Why Database GEO Indexes Need Hilbert Curves Not Z-Order cover art

Why Database GEO Indexes Need Hilbert Curves Not Z-Order

Why Database GEO Indexes Need Hilbert Curves Not Z-Order

Listen for free

View show details
Geospatial queries are everywhere—ride-hailing, food delivery, logistics—but the database indexes powering them often fail under real-world coordinate distributions. Lucas and Luna dig into why Z-order curves, the default for many spatial indexes, produce inefficient query rectangles that scan too many tiles, while Hilbert curves preserve locality better for most geospatial workloads. They walk through a concrete example: a logistics company whose geofence lookups were scanning 40% more tiles than necessary, and how switching to a Hilbert curve index cut query latency by half. They also discuss trade-offs: Hilbert indexes are slower to build, and for point-radius queries the advantage narrows. If you're designing a location-aware feature, knowing which space-filling curve your database uses—and when to override it—can save you from buying more hardware to fix a software problem. #Database #GeospatialIndexing #HilbertCurve #ZOrderCurve #SpatialIndex #PostGIS #SQL #NoSQL #LocationBasedServices #QueryPerformance #DatabaseOptimization #TechPodcast #FexingoBusiness #BusinessPodcast #DataEngineering #IndexingStrategy #Geofence #LatencyOptimization Keep every episode free: buymeacoffee.com/fexingo
adbl_web_anon_alc_button_suppression_t1
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.