Pull EPSG codes from legacy pyproj epsg code dump #2
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
Add 1527 new EPSG codes compared to what our legacy/crs-defs.deprecated.json represented. This hopefully should not have the issues with X/Y inversion and other problems that came from the dump I did using the newer PROJ6+ definitions.
Prior commit was formatted wrong. The lines didn't begin with "EPSG:XXXX", but instead "XXXX"
This had 30 more EPSG codes defined than I was able to pull from legacy pyproj!
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.
Add 1527 new EPSG codes compared to what our legacy/crs-defs.deprecated.json represented. This hopefully should not have the issues with X/Y inversion and other problems that came from the dump I did using the newer PROJ6+ definitions.