-
Notifications
You must be signed in to change notification settings - Fork 36
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
Can't correctly recognize netCDF file #737
Comments
Where did you see that syntax? It's not documented like that, it's just an accident that it doesn't error ;) The syntax is:
I will fix so your syntax throws an error |
Thank you for pointing out my error! The syntax does work if using ArchGDAL:
But it outputs wrong coordinates:) |
I mean did you get the right coordinates with the right syntax? The problem with your syntax is it only "works" by mistake, it's not doing what you think it is so the values are not what you want. I need to make it throw an error (I think it's just using GDAL to load the file, and it's not good at loading netcdf) |
Yes, it provides the correct coordinates with the proper syntax. However, with incorrect syntax using ArchGDAL, the coordinates only shift by half a grid width, making it difficult to detect the error. It would be beneficial if throwing an error in such cases. |
Yes I will stop that syntax from working at all, its just the fallback function somehow ignoring the second argument. |
Thanks. I have updated the title of this issue to avoid misleading other users. |
Additionally, there is a minor issue where the variable in the sample NetCDF file is not recognized by Rasters.jl without explicitly specifying the variable name. Here is the code I attempted:
It prompts:
|
Right, it's ignoring the dimension variables lat/lon but not the |
For the following sample netCDF file described by CDL:
It can not be opened:
It prompts:
If specifying data source:
It prompts:
If using ArchGDAL, it does open the file, but it gives wrong coordinates:
The text was updated successfully, but these errors were encountered: