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 9.7.0 #1558

Merged
merged 1 commit into from Jul 27, 2019
Merged

Database: update to EPSG 9.7.0 #1558

merged 1 commit into from Jul 27, 2019

Conversation

rouault
Copy link
Member

@rouault rouault commented Jul 25, 2019

No description provided.

@nyalldawson
Copy link
Contributor

@nyalldawson nyalldawson commented Jul 25, 2019

Very quick turnaround, lovely stuff!

Do these upgrades get backported to stable releases?

@rouault
Copy link
Member Author

@rouault rouault commented Jul 26, 2019

@kbevers This would go to master, which will be released as PROJ 6.2 right ? Anyway this update itself could probably be candidate for a backport to a maintenance branch if there was an active one currently.

@snowman2
Copy link
Contributor

@snowman2 snowman2 commented Jul 26, 2019

Maybe this could be something where the PROJ database and the PROJ source code could be separate? Similar to proj-datumgrids, you could also distribute proj-database?

@hobu
Copy link
Contributor

@hobu hobu commented Jul 26, 2019

Maybe this could be something where the PROJ database and the PROJ source code could be separate?

I lean toward no on that because the db potentially changes the behavior and results of the software. I think we want releases pinned to known versions rather than letting users manage it. Also, releasing the db as its own entity brings up a number of challenging packaging issues (licensing and such) that we'd rather not have to revisit now that we have seem to have overcome them.

@rouault
Copy link
Member Author

@rouault rouault commented Jul 26, 2019

I lean toward no on that because the db potentially changes the behavior

The model of the DB might also change, and will certainly change in the coming months because EPSG is revising their data model to align more closeling with ISO19111:2019 and this will certainly require non trivial changes to the structure of the PROJ db and the code as well.

@snowman2
Copy link
Contributor

@snowman2 snowman2 commented Jul 26, 2019

Okay, sounds like it definitely should remain as is then.

@kbevers
Copy link
Member

@kbevers kbevers commented Jul 27, 2019

@kbevers This would go to master, which will be released as PROJ 6.2 right ? Anyway this update itself could probably be candidate for a backport to a maintenance branch if there was an active one currently.

Yes and yes. 6.1.1 included an update to the EPSG database as well so that practice has already been established.

@kbevers kbevers added this to the 6.2.0 milestone Jul 27, 2019
@kbevers kbevers merged commit f567ee4 into OSGeo:master Jul 27, 2019
4 checks passed
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

5 participants