Skip to content
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

Closed
magau opened this issue Aug 23, 2019 · 3 comments
Closed

X/Y axis units (radian) #1799

magau opened this issue Aug 23, 2019 · 3 comments

Comments

@magau
Copy link
Contributor

magau commented Aug 23, 2019

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:

else if( EQUAL( szUnits, "rad" ) )

else if( EQUAL( szUnits, "rad" ) )

Hope this small change can improve the GDAL library in order to keep the NetCDF standard to be used correctly.

Cheers!

@rouault
Copy link
Member

rouault commented Aug 23, 2019

Are there datasets that use "radian" and you hit that issue ? Your proposed change is reasonable. You could issue a pull request with it.

@magau
Copy link
Contributor Author

magau commented Aug 26, 2019

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".

https://en.wikipedia.org/wiki/Rad_(unit)

@rouault
Copy link
Member

rouault commented Aug 26, 2019

Fixed per #1803

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants