alt Hacker NewsFrom the DuckDB geospatial docs:
SELECT * FROM './path/to/some/shapefile/dataset.shp';
COPY table TO 'some/file/path/filename.geojson' WITH (FORMAT gdal, DRIVER 'GeoJSON', LAYER_CREATION_OPTIONS 'WRITE_BBOX=YES');
This seems extremely helpful to me.
From the DuckDB geospatial docs:
SELECT * FROM './path/to/some/shapefile/dataset.shp';
COPY table TO 'some/file/path/filename.geojson' WITH (FORMAT gdal, DRIVER 'GeoJSON', LAYER_CREATION_OPTIONS 'WRITE_BBOX=YES');
This seems extremely helpful to me.
And ogr2ogr is also very helpful:
ogr2ogr -f "PostgreSQL" -t_srs "EPSG:2274" PG:"host=host user=user dbname=database password=trustno1 schemas=schema" shapefile.shp -nln new_name_for_table
I'll give DuckDB a shot and compare to postgis. Eventually, I think the issue for me would be that I use all the vector outputs via apps connecting to the same database.