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.

Sign up for GitHub

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

Jump to bottom

geospatial_bounds_vertical_crs should not appear when 3D CRS is already present #674

Open
daltonkell opened this issue Sep 24, 2019 · 0 comments
Open

geospatial_bounds_vertical_crs should not appear when 3D CRS is already present #674

daltonkell opened this issue Sep 24, 2019 · 0 comments
Assignees
@daltonkell
Labels
ACDD-Checker

Comments

@daltonkell
Copy link
Contributor

According to the definition of geospatial_bounds_vertical_crs in ACDD:

The vertical coordinate reference system (CRS) for the Z axis of the point coordinates in the geospatial_bounds attribute. This attribute cannot be used if the CRS in geospatial_bounds_crs is 3-dimensional; ...

Even when a 3-D geospatial_bounds_crs is already present, the ACDD checker still seeks the geospatial_bounds_vertical_crs. This should be changed to reflect the accepted definition.
@daltonkell daltonkell self-assigned this Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daltonkell daltonkell

Labels
ACDD-Checker
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@benjwadams @daltonkell