osm2pgsql flex backend
summary
osm2pgsql’s new flex backend lets users define arbitrary tables and uses a per-object flex API to decide for each node way or relation where it goes so you can handle nodes ways relations multipolygons and then run phase-two processing to revisit ways after relations are read. It supports geometry ops (polygons→points merge split), a minutely-updated whole-planet DB workflow, raster-based generalization for merged landuse and an advanced tile expiration system to minimize re-renders.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:19What is osm2pgsql?
- 1:12Middle and memory
- 2:02Different backends
- 4:36Simple node-only example
- 5:09More advanced usage
- 7:06Generalization
related talks
43mLocate all the things
37mProcessing Open Street Map Data with Python and PostgreSQL
40mGIS capability of PostgreSql using POSTGIS & OSM DATA
21mThe Open Source Geospatial Community, PostGIS, & Postgres
21mActual trees, not b-trees: or how I found PostgreSQL through PostGIS
19mGeoPackage and the Related Tables Extension
24mActual trees, not b-trees...
23mLocation Insights for Your Graphs with Neo4j, PostGIS, and Brickgraph