-
Notifications
You must be signed in to change notification settings - Fork 6
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
How to specify a PROJ string in a CF-netCDF file? #43
Comments
I do not recall that this question has been discussed before and it's a good point. I would support the definition of such an attribute of the grid_mapping variable, provided that (like the WKT) it was regarded as subordinate to the attributes specifying the projection. |
We systematically add a :proj_string attribute to our crs variable. Having a standardized name for such an attribute could help and avoid the zoo of :projstr, :proj4string, :proj4_string, etc... etc... |
How about |
Hei Jim, I think "proj string" is very much accepted in that sense. For example this is how the "quick start" of the PROJ software begins:
So it would makes sense (at least to me!) to stay close to the existing PROJ terminology. But of course, there are many options, including "crs_proj" (that would relate to the existing "crs_wkt"). |
One might want add a
PROJ
string to a grid mapping description as additional (redundant) information. Currently, no attribute name (e.g.proj_string
) is specified for this purpose in the CF Conventions.There exists a specific
crs_wkt
attribute in Table F.1 of the CF Conventions. However, no similar attribute for aPROJ
string is provided although the Notes of most grid mapping descriptions in Appendix F point to thePROJ
software package.Does there exist a best practice where/how to specify a
PROJ
string?By the way:
PROJ4
is calledPROJ
, now, and recently advanced to versions 5, 6 and 7 after two decades of version 4. Therefore, several URLs in Appendix F don't work anymore. I will create a issue and a pull request next week for this (issue cf-convention/cf-conventions#253; pr cf-convention/cf-conventions#254).The text was updated successfully, but these errors were encountered: