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

Database: update to EPSG v9.6.1, IGNF v3.0.3, ESRI 10.7.0 and add operation_version column #1368

Merged
merged 10 commits into from Mar 26, 2019

Conversation

Projects
None yet
3 participants
@rouault
Copy link
Member

commented Mar 25, 2019

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.

rouault added some commits Mar 25, 2019

WKT2_2018: export ID in base crs node, when there is none on top of u…
…pper node

This is the standard logic, that is now possible since ID is
allowed in BASEGEOGCRS and similar node
WKT2_2018: always export ID in base crs node, even if there is one on…
… upper node

This is a particular logic allowed by paragraph 7.3.3 Identifier
of OGC 18-010r6
WKT2_2018: always export ID of SOURCECRS/TARGETCRS and STEPs
even if there is one on upper node

This is a particular logic allowed by paragraph 7.3.3 Identifier
of OGC 18-010r6
@kbevers

This comment has been minimized.

Copy link
Member

commented Mar 25, 2019

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.

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 rouault changed the title Database: update to EPSG v9.6.1, IGNF v3.0.3 and add operation_version column Database: update to EPSG v9.6.1, IGNF v3.0.3, ESRI 10.7.0 and add operation_version column Mar 25, 2019

@rouault

This comment has been minimized.

Copy link
Member Author

commented Mar 25, 2019

@hobu

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2019

👍 to this being done at this time. It is still quite early in the 6.0 cycle and people are just getting acclimated.

@rouault rouault merged commit 1e575f4 into OSGeo:master Mar 26, 2019

3 checks passed

Travis CI - Pull Request Build Passed
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
coverage/coveralls Coverage increased (+0.01%) to 85.313%
Details

@rouault rouault deleted the rouault:epsg_961_and_operationversion branch Mar 26, 2019

rouault added a commit that referenced this pull request Mar 26, 2019

Merge pull request #1372 from OSGeo/backport-1368-on-6.0
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

@kbevers kbevers added this to the 6.0.1 milestone Mar 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.