Database: update to EPSG v9.6.1, IGNF v3.0.3, ESRI 10.7.0 and add operation_version column #1368
Conversation
This file contains 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
…pper node This is the standard logic, that is now possible since ID is allowed in BASEGEOGCRS and similar node
… upper node This is a particular logic allowed by paragraph 7.3.3 Identifier of OGC 18-010r6
even if there is one on upper node This is a particular logic allowed by paragraph 7.3.3 Identifier of OGC 18-010r6
Maybe a topic for discussion on the mailing list? My immediate thoughts are that it is probably safe to do a backport right now but it may cause problems for people in the future. In the future we may very well see people that are interfacing with the database directly. |
rouault
changed the title
|
Discussion started in https://lists.osgeo.org/pipermail/proj/2019-March/008376.html |
|
👍 to this being done at this time. It is still quite early in the 6.0 cycle and people are just getting acclimated. |
rouault
added a commit
that referenced
this pull request
Mar 26, 2019
Backport #1368 on 6.0: Database: update to EPSG v9.6.1, IGNF v3.0.3, ESRI 10.7.0 and add operation_version column
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Only the 4 last commits are specific to this PR, the other ones come from #1366
I'm not sure what our policy regarding backport is for that case. There's no API change, but we change database content and structure.