Today, spatial work can happen on one platform. Spatial SQL is now Generally Available. Databricks is a geospatial lakehouse. The era of bolting a spatial database onto a warehouse onto a mapping tool is over. Store data as Geometry in Iceberg or Delta, run spatial queries at scale, call 90+ spatial functions, share through Delta Sharing, and explore in Genie, while Unity Catalog handles the governance.

Within the time-crunch caused by an approaching hurricane, every second counts. This is why we have continuously improved out-of-the-box performance of spatial joins and ST_ functions since Public Preview. To measure the latest improvements, we ran a comprehensive benchmark using SpatialBench. Across SpatialBench, 8 of the 12 queries improved since Public Preview, with gains ranging from 20% to 15X.

For boolean set operations (ST_Intersection, ST_Difference, ST_Union) we’ve introduced improved algorithms. These functions can help answer questions like, “Which parts of my land parcels lie inside the projected hurricane path?” and “What's the combined coverage of all our cell towers in this area?” Databricks is now 2X faster on average working with areal datasets using these operators compared to the prior versions. No code changes required, your existing queries just got faster.

These are the spatial operations that drive efficiency for Databricks customers like Top Chrono, who specialize in Premium Courier and Last-Mile Delivery services.