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

value in corner vs. value in center #12

Open
KathiSchleidt opened this issue Jan 5, 2022 · 0 comments
Open

value in corner vs. value in center #12

KathiSchleidt opened this issue Jan 5, 2022 · 0 comments

Comments

@KathiSchleidt
Copy link
Collaborator

The way I've come to understand coverage good practice, value in corner should be used (this is the point for which we provide the exact information), but the Elevation Data Spec goes the way of Bitmaps, mandating value in center:

IR Requirement Annex II Section 6.2.1.2 Constraints of the spatial object type RectifiedGridCoverage

Grid points of a RectifiedGridCoverage shall coincide with the centres of cells of the geographical grids defined in Section 2.2 of Annex II of the Commission Regulation on Interoperability of Spatial Data Sets and Services at the same resolution level.

I discussed this with Emmanuel Devys from IGN France, he confirmed my confusion:

IMHO, the elevation posts are supposed to be at the grid points and not in the middle of the cell. Elevation posts are NOT surfaces. If the encoding is GeoTIFF (quite common), the PixelIsPoint is the option that should be used. Therefore other spec. elements working for pixels (with square area cells) should be avoided for clarity – IMHO). I am curious to get the justification for such a choice in the EL spec.

Which option should be implemented?

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

1 participant