[DO NOT MERGE] Add Proj as a dependency and constrain its version to <1.9 #436
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
A theoretical Proj v1.9 release will have type piracy on GeoFormatTypes
asinghvi17
changed the title
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.
A theoretical Proj v1.9 release will be the new blessed pirate for GeoFormatTypes, see JuliaGeo/GeoFormatTypes.jl#21
This comes with some benefits for users but it's a bit breaking. Maybe ArchGDAL should also load Proj, to minimize breakage, since loading Proj means GFT converts work as usual.
Something to think about.