-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lat/lon gridded data does not have monotonically increasing latitudes #60
Comments
@jbusecke this is standard for reanalysis data (such as ERA5), although I agree it is counterintuitive. For example, try loading sample NCEP reanalysis data with xarray:
The latitude values are also in decreasing order. |
Oh interesting, I did not know that. Thanks @tom-andersson. I personally would make the argument that this is something that 'should' be changed to make the data more analysis ready, but I guess this is somewhat personal preference and it would be good if there is more general guidance on this that ARCO-producers could refer to. |
I agree that this is not ideal but there are very many datasets like this ;) particularly in the raster imaging space. See pydata/xarray#1613 for a discussion on a nicer API that ignores order of the coordinate variable. |
First of all THANK YOU so much for this effort! Having ERA5 data available in an ARCO format is truly a game changer!
I noticed a small issue: The latitudes of the lat/lon gridded data 1959-2022-full_37-1h-0p25deg-chunk-1.zarr-v2/ seems to have decreasing latitude values
which makes selecting a region in xarray slightly counterintuitive:
returns no latitude indicies
![image](https://private-user-images.githubusercontent.com/14314623/275976369-280f8ff9-e3c4-4dd7-90ae-cce5e7487e89.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM5ODk1NTMsIm5iZiI6MTcyMzk4OTI1MywicGF0aCI6Ii8xNDMxNDYyMy8yNzU5NzYzNjktMjgwZjhmZjktZTNjNC00ZGQ3LTkwYWUtY2NlNWU3NDg3ZTg5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDEzNTQxM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg2NGI4OTkxNDhmYjhhZjYzNWY3ODQ1YjhjYWE2NjYxY2RhOTlmNmIzNzRmZGU3MDIwYTMzYTM1MTJmMzI4NmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.P3jdFKqsava1CiCRZViW0xnJZstFae-COt-BLbRhHrY)
while
gives (the desired)
If you end up reprocessing the data at some point, I wonder if something like xarrays
ds.sortby('latitude')
or equivalent could be added to the pipeline.The text was updated successfully, but these errors were encountered: