-
Notifications
You must be signed in to change notification settings - Fork 806
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
Add projsync utility #1903
Add projsync utility #1903
Conversation
Why do we have |
I wonder if this should be called some variant of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. This is a nice utility to add the package.
I wonder about the tests of the application, how resilient are they to changes in PROJ-data/the CDN? Do we need to update the tests everytime a change is made on the CDN or will this still work unchanged?
@hobu I was indeed midly satisfied with the name. projdownload seemed a bit stodgy to me, but projsync would be good. I'll go for it, if you and @kbevers is happy with that Regarding synchronizing proj.db, this is a hard topic as I discussed a number of times. PROJ is highly sensitive to the content of proj.db. So if we were to do it, we would likely to have proj_7.0.0.db files compatible of PROJ 7.0.0 binary. |
They should be pretty resilient, unless we remove some files / source agencies. |
My thought was to update if a new version of EPSG came out. Maybe it isn't worth the trouble. |
Sounds good to me.
It seems that EPSG doesn't really follow semantic versioning, so an increase in the patch-number can add a new operation or some other thing that requires new code. #1869 is a good example of that. It would be great if we in the future could decouple the EPSG-registry from specific PROJ releases and update the database when new updates appear in the EPSG registry but we're not there yet. |
024a18f
to
bf0555d
Compare
bf0555d
to
8731828
Compare
Fixes #1750