include geojson serialization and geo_inferface #71
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.
This PR includes support for the
__geo_interface__
on the topology object. Since the__geo_interface__
is build upon thegeojson
standard this also means there is now a.to_geojson()
function.The
pretty
andvalidate
parameter will probably change later toFalse
andFalse
instead of the currentTrue
,True
.With the
__geo_interface__
in place, visualization can be done directly using theTopology
object in Altair:Prepare a
Topology
object:And then:
Compare this to the current approach (still and will be completely OK as well):
This PR also means that there will be two approaches to create a
GeoDataFrame
:And now:
Maybe the
to_gdf()
function should get adriver
parameter, that can be set toTopoJSON
orGeoJSON
?I will not close the relevant issues, since tests are not written yet.