Add Swagger API documentation and add data ingestion from NASA API #143
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-Swagger API:
We have developed the Swagger API documentation for the Surface URLs.
The development work primarily involved adding the extend_schema decorator from the drf_spectacular library to each of the involved views. This allowed us to include a brief description of the API's purpose, the various parameters used, and, in some cases, the allowed responses for each endpoint.
-Data Ingestion from NASA API:
We have developed a new decoder for JSON files provided by NASA's Power Data APIs, similar in functionality to the existing ones. This required adding a new line in both the Format and Decoder tables with the name “JSON_NASA.” Additionally, we have enabled SURFACE to make API requests to external sources like NASA Power Data, allowing periodic data retrieval and storage without an FTP server. These features use existing models, a new “cron_scheduler” field in the Station table was added to schedule data retrieval tasks