-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
X/Y axis units (radian) #1799
Comments
Are there datasets that use "radian" and you hit that issue ? Your proposed change is reasonable. You could issue a pull request with it. |
Yes. The geostationary projection requires X/Y axis values in radians or km. My objective here is to encourage the data providers to use de "radians" value for the "units" attribute if they choose to represent the coordinates in radians and stop using "rad" which is the units for "absorbed dose". |
Fixed per #1803 |
According with the NUWG NetCDF Conventions for naming units, the value "rad" for radian unit shouldn't be used. Instead, the correct value should be "radian".
As one can see in the end of the following document:
https://www.unidata.ucar.edu/software/netcdf/netcdf/Units.html
My proposal to resolve this issue is to add both values ("rad" and "radian") as possible value for the X/Y axis/coordinates unit, in order to keep retro-compatibility.
So, instead of:
else if( EQUAL( szUnits, "rad" ) )
I sugest:
else if( EQUAL( szUnits, "rad" ) || EQUAL( szUnits, "radian" ))
As far as I know the following two lines should be changed:
gdal/gdal/frmts/netcdf/netcdfdataset.cpp
Line 3642 in 9e00045
gdal/gdal/frmts/netcdf/netcdfdataset.cpp
Line 3660 in 9e00045
Hope this small change can improve the GDAL library in order to keep the NetCDF standard to be used correctly.
Cheers!
The text was updated successfully, but these errors were encountered: