Parse GeoFormatTypes EPSG with 2 codes #374
Merged
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
evetion
changed the title
evetion
force-pushed
the
feat/parse-epsg2
branch
from
ed57ef1
to
9330962
Compare
yeesian
approved these changes
Oct 20, 2023
|
Not currently no. It would be a compound CRS, and you can lookup the individual codes. Like the test examples, it would be a combination of a 2D CRS and a vertical one, making it 3d. Some of those combinations are common, and have their own code: 4326+3855 == 9518. Maybe the Proj.identify function could help with this, but it doesn't yet know about the EPSG{2} convention. |
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.
To be merged after #372 and JuliaGeo/GeoFormatTypes.jl#22