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

Allow aliases in GeoTIFF CRS #122

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

desruisseaux
Copy link
Contributor

In the planetary working group, there is a need for aliases because names or identifiers of some asteroids (for example) can change. The ISO 19111 specification already supports aliases, but not GeoTIFF. A possible approach would be as below:

  • Adopt the GDAL/ESRI convention described in GitHub issue 59.
  • Add the following amendment: keys can be repeated. If a key is repeated (not necessarily consecutively), all occurrences after the first one are aliases. For example in "GCS Name = my CRS|Datum = My datum|Ellipsoid = my ellipsoid|Datum = My Datum alias|", "My datum" would be the primary datum name and "My datum alias" would be an alias for that datum.

…pochGeoKey`

key name from the "GeoTIFF v1.0 key name" column to the "This document key name".
In my understanding, that key didn't existed in GeoTIFF 1.0.
… and requirement 16.5.

This is a source code formatting, with no change in text and no change in the PDF or HTML formatting.
This is a complement of pull request opengeospatial#114, which was done by an automatic tool on main paragraphs only.
The formatting in this commit was done manually in preparation for future change requests with content changes.
…peated.

All occurrences after the first one should be interpreted as aliases.
@desruisseaux
Copy link
Contributor Author

This pull request defines the structure of GeodeticCitationGeoKey. Some requirements in GeoTIFF specification seem to implicitly require a similar structure for VerticalCitationGeoKey and ProjectedCitationGeoKey as well — see #59 (comment). Current pull request does not cover those two latter cases.

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

Successfully merging this pull request may close these issues.

None yet

1 participant