www.femafhz.com/map/48.62379...
www.femafhz.com/map/48.62379...
Python spatial and all its package baggage are built on top of GDAL. Cut out the middleman and use 'gdal ....' to create/edit ALL your raster/vector data directly.
(Looking at you, too, ESRI)
Python spatial and all its package baggage are built on top of GDAL. Cut out the middleman and use 'gdal ....' to create/edit ALL your raster/vector data directly.
(Looking at you, too, ESRI)
Riverine Flooding shown:
www.femafhz.com/map/36.98500...
Riverine Flooding shown:
www.femafhz.com/map/36.98500...
www.femafhz.com/map/19.43551...
www.femafhz.com/map/19.43551...
Simplify:
gdal vector simplify --input=states.gpkg --tolerance=.5 --output=simple.gpkg
Clean coverage:
gdal vector clean-coverage --input=simple.gpkg --snapping-distance=.7 --output=clleaned.gpkg
Simplify:
gdal vector simplify --input=states.gpkg --tolerance=.5 --output=simple.gpkg
Clean coverage:
gdal vector clean-coverage --input=simple.gpkg --snapping-distance=.7 --output=clleaned.gpkg
www.femafhz.com/map/17.66233...
www.femafhz.com/map/17.66233...
On demand printing, no limit on # of copies. Print or eBook. Guidelines exist that can make it daunting. Not a small task. I've been using KDP for 10+ years:
www.postholer.com/maps/Pacific...
On demand printing, no limit on # of copies. Print or eBook. Guidelines exist that can make it daunting. Not a small task. I've been using KDP for 10+ years:
www.postholer.com/maps/Pacific...
The network and the client's ability to process is the limitation, NOT the FGB/COG format. How is shoving 50MB of vector data into an app/browser over the internet useful?
Parquet tooling is a problem, not a solution.
The network and the client's ability to process is the limitation, NOT the FGB/COG format. How is shoving 50MB of vector data into an app/browser over the internet useful?
Parquet tooling is a problem, not a solution.
People need to understand, for bbox spatial queries, web server range requests and the proper file format, FGB/COG, are ideal.
Need a non-spatial attribute query? Great! Use the overhead you're suggesting.
People need to understand, for bbox spatial queries, web server range requests and the proper file format, FGB/COG, are ideal.
Need a non-spatial attribute query? Great! Use the overhead you're suggesting.
Examples DuckDB, GeoPandas, GDAL all use bbox. With FGB you don't need any of that. Overture 145M buildings, single 35GB FGB remote web server:
www.femafhz.com/map/26.90634...
Examples DuckDB, GeoPandas, GDAL all use bbox. With FGB you don't need any of that. Overture 145M buildings, single 35GB FGB remote web server:
www.femafhz.com/map/26.90634...
...or dynamically put the IP in iptables.
...or dynamically put the IP in iptables.
Mead has 7% chance for 2029, 3% for 2030, otherwise 0%.
www.usbr.gov/lc/region/g4...
Mead has 7% chance for 2029, 3% for 2030, otherwise 0%.
www.usbr.gov/lc/region/g4...