createCoordinateOperation(): tune computed accuracy of a concatenated op within ETRS89 #4670
+596
−249
Conversation
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
- Database: anticipate upcoming addition of ETRS89-xxx national realizations to the ETRS89 datum ensemble to synthetize null Helmert transformations between ETRS89 and ETRS89-XXX with accuracy of 0.1 m - When doing ETRS89-xxx to ETRS89-yyy, prefer going through ETRF2000 than ETRS89 (when both ways have the same accuracy), as suggested by EPSG Guidance Note 7-7 (ETRS89 in the EPSG Dataset)
… op within ETRS89 When doing ETRS89-XXX -> ETRS89/ETRFzzzz -> ETRS89-YYY and at least one of the 2 operations is a no-op, do not add the two inaccuracies but use their maximum (which should be 0.1 m)
rouault
force-pushed
the
tune_accuracy_etrs89
branch
from
3e6e3fa to
acb7310
Compare
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.
When doing ETRS89-XXX -> ETRS89/ETRFzzzz -> ETRS89-YYY and at least one of the 2 operations is a no-op, do not add the two inaccuracies but use their maximum (which should be 0.1 m)
(on top of PR #4669)