Rasterflow, Earth Intelligence & inference engine now in public preview Learn More

Wherobots Now Federates with the AWS Glue Data Catalog

AWS glue catalog blog image
AWS customers can now bring Wherobots’ best-in-class spatial intelligence capabilities to any dataset managed by AWS Glue Data Catalog.

AWS Glue Data Catalog (GDC) customers use it to manage structured data, like user activity and revenue reports, and complex geospatial data, like parcels, buildings, and mobility datasets. AWS services like EMR, Redshift, and Athena excel at processing the former, while Wherobots is purpose-built for the latter. AWS customers have standardized tooling, governance, and processes around the GDC, which they do not want to replicate on another catalog. Having to manage two catalogs introduces friction and slows down innovation.

How Wherobots Connects to the AWS Glue Data Catalog

Today, Wherobots addresses this friction by making it easier for customers to use the best spatial data tool for the job while maintaining their governance layer in the AWS GDC. Using IAM policies, customers can now federate access between the AWS Glue Data Catalog and Wherobots. Wherobots will handle reading geospatial data from that catalog, processing it and writing it back to it, while Glue continues to act as the central catalog.

For instance, consider a national e-commerce retailer coordinating just-in-time restocking across regional distribution centers. The workflow:

  • Wherobots can ingest Sentinel-1 SAR imagery, which sees through cloud cover
  • And ingest NOAA’s High-Resolution Rapid Refresh (HRRR) precipitation forecast raster
  • Join both to the Overture Roads network connecting each center to its delivery routes
  • Buffering the affected road segments and running zonal statistics against the flood and precipitation layers, the retail team can use Wherobots to calculate a route disruption score for each corridor and writes it to a federated Glue table.
  • Supply chain teams at the retailer can then pull that score into their EMR restocking pipelines to trigger early shipments or reroute orders before a corridor goes down.
Risk scores along road segments in Europe.

Spatial Compute Built for Physical-World Data

Trino, Postgres, and Spark are battle-tested engines, but they were not designed for what spatial data demands, such as coordinate reference systems (CRS), mixed raster and vector formats, and joins across billions of geometries.

Built by the original creators of Apache Sedona and 100% code compatible across all spatial functions, WherobotsDB handles the spatial workloads that stall on general-purpose engines. With RasterFlow, this power extends to Earth Observation, enabling planetary-scale mosaicking and AI inference pipelines alongside high-performance vector analytics. Customers can also take advantage of Wherobots’ Spatial AI tools to get insights from spatial data in minutes using natural language, with little to no prior geospatial expertise. Open table formats and catalog services like AWS Glue Data Catalog remove the tradeoff: your governance, tooling, and data stay in Glue, while the engine built for spatial data does the spatial work.

Regrid, uses Wherobots to provide comprehensive parcel data with boundaries, buildings, addresses, and geographic enrichments for all your location decisions.

"We made a deliberate decision to standardize on AWS. The expertise and experience Wherobots bring to helping us navigate and architect the transition of 4,000+ geospatial pipelines to a highly scalable and efficient cloud native processing workflow has been invaluable to the success of our project. Wherobots is creating the future of cloud geospatial processing."
Blake Girardot

Senior Data Engineer at Regrid

Get started with Wherobots and the AWS Glue Data Catalog

Integrate Wherobots with your AWS Glue Data Catalog securely using AWS IAM in a few minutes, and run your first workloads on the Professional free trial: 14 days or $95 in credits, whichever comes first.

We also offer hands-on spatial expertise to help you move your ideas and initiatives into production faster. We deliver this through the Wherobots Innovation Edition, which you can subscribe to by reaching out to us.

Key takeaways

  • AWS Glue Data Catalog customers can now federate access to Wherobots using IAM policies. Wherobots reads geospatial data from the catalog, processes it, and writes it back, while Glue remains the central catalog. Customers keep existing GDC governance, tooling, and processes instead of running a second catalog.
  • WherobotsDB is built by the original creators of Apache Sedona and is 100% code compatible across spatial functions. It handles CRS, mixed raster and vector formats, and joins across billions of geometries that stall on general-purpose engines such as Trino, Postgres, and Spark.
  • A national e-commerce restocking example joins Sentinel-1 SAR imagery, NOAA HRRR precipitation forecast rasters, and the Overture Roads network, then buffers affected segments, runs zonal statistics, and writes a route disruption score to a federated Glue table that EMR restocking pipelines can pull.
  • Regrid standardized on AWS and used Wherobots to help architect the transition of 4,000+ geospatial pipelines to cloud-native processing. Integration uses AWS IAM and can be stood up in a few minutes on the Professional free trial: 14 days or $95 in credits, whichever comes first.

Frequently Asked Questions

How does Wherobots connect to the AWS Glue Data Catalog?

Customers federate access between Glue Data Catalog and Wherobots using IAM policies. Wherobots handles reading geospatial data from that catalog, processing it, and writing it back. Glue continues to act as the central catalog, so AWS-standard tooling, governance, and processes stay in place.

Why use Wherobots instead of EMR, Redshift, or Athena for geospatial data?

EMR, Redshift, and Athena excel at structured data such as user activity and revenue reports. Wherobots is purpose-built for geospatial data such as parcels, buildings, and mobility datasets. Trino, Postgres, and Spark were not designed for CRS, mixed raster and vector formats, and joins across billions of geometries.

Can Wherobots write spatial results back to Glue tables?

Yes. In the retail restocking example, Wherobots calculates a route disruption score for each corridor and writes it to a federated Glue table. Supply-chain teams then pull that score into EMR restocking pipelines to trigger early shipments or reroute orders.

How do I get started with Wherobots and Glue?

Integrate Wherobots with your AWS Glue Data Catalog using AWS IAM in a few minutes, and run first workloads on the Professional free trial: 14 days or $95 in credits, whichever comes first. Hands-on spatial expertise is also available through the Wherobots Innovation Edition.

RELATED POSTS
VIEW MORE

RasterFlow is now available in Public Preview

RasterFlow makes planetary-scale earth intelligence workflows easy and costs predictable. We are excited to announce that RasterFlow is now in Public Preview, opening up the power of planetary scale Earth Intelligence to all Wherobots Professional Edition customers! RasterFlow let’s you solve complex monitoring challenges with vision-language models or tailored models for specific use cases, without […]

Wherobots for QGIS: Cloud-Scale Spatial Data, from Wherobots Labs

Wherobots for QGIS is a new plugin that connects QGIS to Wherobots Cloud. From a panel inside QGIS, an analyst can run spatial SQL against WherobotsDB, load the results as a map layer, push a local layer up to a Wherobots Iceberg table, and pull raster data into the canvas.  Why Wherobots for QGIS: Eliminating […]

How Wherobots builds with NVIDIA to let AI see the physical world

The world and what happens in it is digitized by petabytes of raw and derivative spatial datasets of various data types and scales, and the potential for applying AI to it is immense. But the AI models and agents we use every day need connectivity to tools that turn this data into usable insights and relationships. Wherobots gives AI the ability operate on and understand raw physical-world data, and NVIDIA GPUs are core to it. Architecturally here’s how this works at a high level.

El Niño 2026, atmospheric rivers, and California’s burn scars: one SQL engine, two data models

7,713 mapped building footprints sit inside or within 500 m (1,640 ft) of the 42 Eaton basins USGS rates high hazard for debris flows, and 388 km (241 mi) of mapped road and path cross the low ground below the scar. WherobotsDB finds both in SQL: a join to the USGS basins for the buildings, and a raster vector join over elevation for the roads.