Fixed an issue with data format provided by new cds api, added test #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The test pipeline is outdated. (Our fault.) Would you please merge dev? That should allow to run them, again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The API of the copernicus Climate Data Store (CDS) was revised at the end of September.
The data format provided by the API for ERA5 data has also changed.
The column containing the time stamps is now no longer called “time” but “valid_time”.
This leads to errors when reformatting the data provided into the dataframe format.
As a solution, I suggest simply renaming the column to “time” when reformatting.
I have also added a test that checks the reformatting into the Pandas dataframe format.
Sample data is used for this.