Allow aliases in GeoTIFF CRS#122
Draft
desruisseaux wants to merge 4 commits intoopengeospatial:masterfrom
Draft
Conversation
…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.
Contributor
Author
|
This pull request defines the structure of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
"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.