GeoDjango at City Scale: Spatial Data for Urban Systems
summary
GeoDjango plus PostGIS stores city entities as Point, LineString, and Polygon fields and uses spatial indexes to cut a sample query from 3410 ms to 6.2 ms. The demo models buildings, transit stops, roads, districts and finds buildings >500 meters from chargers by unioning charger 500 m buffers and subtracting that footprint to count gaps. Recommendations include EXPLAIN ANALYZE to verify indexes, partitioning or time/geography sharding for sensors, paging/map-bounds queries, simplified geometries and serving results as GeoJSON for live dashboards.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 2:07Why spatial data matters
- 3:58GeoDjango and PostGIS overview
- 6:25Spatial indexes and geometry types
- 9:20Modeling EV charger gaps
- 12:20Solving urban infrastructure questions
- 14:30District-level dashboard queries
- 17:26Scaling GeoDjango for cities
- 20:45Handling live spatial data
- 23:42Impact and real-world applications
- 24:46Key takeaways and next steps
