Replies: 2 comments 1 reply
-
|
@C-Loftus Pretty sure you just want to create a |
Beta Was this translation helpful? Give feedback.
-
|
From discussing with a coworker it seems like a way to solve this might be to partition the parquet dataset into 50 separate parquet files by their geometry, i.e. a separate parquet file for each state and have another table with the geometry of each state. Then a user could
This would likely work although I was hoping to find a way to do this without needing to have an extra states table which adds a bit of overhead. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Thank you for the excellent work everyone does on duckdb; I have an optimization question. I am struggling with and wondering if folks had opinions. Thank you
Context
ogr2ogr -f "Parquet" reference_flowline.parquet reference_flowline.gpkg -t_srs EPSG:4326 -lco COMPRESSION=ZSTD -lco ROW_GROUP_SIZE=122880Geoparquet Metadata
What works
I am finding that I can use the following, but this seems to just download all the data directly and put it in memory. So at this point it seems like it makes more sense to just download the parquet file on disk.
This is the output of the macos system monitor after running that then building the rtree spatial index.

Beta Was this translation helpful? Give feedback.
All reactions