You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I learned about the pyogrio package, created by the geopandas developers. It enables much faster reading (5-10x faster) & writing (5-20x faster) of vector formats than with geopandas alone. Using pyogrio.read_dataframe and pyogrio.write_dataframe would be super advantageous in all three of our packages: viz-staging, viz-raster, and viz-3dtiles. The docs also outline additional features that would be useful in speeding up our workflow:
Filter records by spatial extent: In viz-staging, we could select and read only polygons that intersect with the tile bounding box, rather than reading in the entire file at once.
Read basic information about a data layer - get CRS, features, num polygons, etc. without reading in the entire file. This would allow us to convert the CRS of the tile bounding box to the CRS of the data to enable the above
Quick note that as of geopandas 0.11, you can set the reading & writing "engine" to pyogrio instead of the default/slower fiona. This is an easy step we could implement to make the workflow a little faster, but it would need some testing.
Today I learned about the
pyogrio
package, created by the geopandas developers. It enables much faster reading (5-10x faster) & writing (5-20x faster) of vector formats than with geopandas alone. Usingpyogrio.read_dataframe
andpyogrio.write_dataframe
would be super advantageous in all three of our packages:viz-staging
,viz-raster
, andviz-3dtiles
. The docs also outline additional features that would be useful in speeding up our workflow:centroid_within_tile
is true.However, note the warning:
The text was updated successfully, but these errors were encountered: