H3 Indexing
summary
Adds the H3 geospatial index to PostgreSQL/PostGIS, shows loading OpenStreetMap data using osm2pgsql inside Docker, and explains H3 internals: 64-bit indexes, 16 resolutions (0–15) with 12 pentagons per level, and cells represented as multipolygons. Demonstrates performance gains—example: a PostGIS distance_within query drops from 14 ms to 3 ms when using an H3 join at resolution 7 (~1500 m)—and shows density maps at level 10 (~120 m, 0.08 s), while warning H3 is WGS84-only, approximate, and unsuitable for exact area or coverage calculations.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:09What is a spatial index
- 4:21H3 explained
- 9:00H3 Core features
- 11:24Installation and setup
- 13:10OSM data example
- 15:46H3 vs PostGIS
- 16:50Data visualization
- 19:02H3 limits and use cases
- 20:41Conclusion and Q&A
related talks
14m10 Things I've Learnt About PostGIS
50m–Mom, can we have G**gle Maps? –We have G**gle Maps at home
45mBreakout Session
40mGIS capability of PostgreSql using POSTGIS & OSM DATA
21mThe Open Source Geospatial Community, PostGIS, & Postgres
53mOn Beyond Data Types
53mThis Is PostGIS
30mBuilding geospatial apps on Postgres, PostGIS, & Citus at large scale