This repository was archived by the owner on Jul 4, 2022. It is now read-only.
move to GeometryBasics #2
Closed
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
GeoJSON counterpart to JuliaGeo/Shapefile.jl#39.
Still very much a work in progress. Currently provides a method to convert individual geometries to GeometryBasics. Right now the properties are still ignored, but they will be stored in the GeometryBasics meta types as a NamedTuple. Performance is obviously worse than the lazy JSON3 representation, but at half a second for a 10MB file it doesn't seem too bad either. (
gpd.read_file("ne_10m_land.geojson")takes 4 seconds).Still worth exploring if we can do better by using the JSON3 Struct API directly, instead of using the default mapping and then converting.