Skip to main content
Wherobots now connects to Databricks Unity Catalog, allowing you to build spatial solutions with data directly from your lakehouse without replication or migration. This integration empowers data teams working on Databricks to use Wherobots’s best in-class geospatial capabilities while continuing to benefit from data governance capabilities of Unity Catalog.
Databricks foreign catalogs use direct authentication, not a Wherobots Cloud connection
When you add a Databricks Unity Catalog foreign catalog in Wherobots, you connect directly to your Databricks workspace URL. Unity Catalog Delta uses a Personal Access Token (PAT). Unity Catalog Iceberg uses OAuth client credentials (client_id and client_secret).

Benefits

  • Zero-Copy architecture: Read tables managed by Databricks Unity Catalog without moving or duplicating data.
  • Maintained governance: Databricks Workspace Admins can retain catalog- and table-level access control when reading their Databricks catalogs.
  • Secure federation: Connect securely using Databricks authentication credentials.
  • Accelerated innovation on the lakehouse: Take spatial ideas to market faster using Wherobots’ 300+ spatial functions, raster inference, and compute for physical world data on your Unity Catalog data.

Supported workflows

Wherobots’ integration with Databricks Unity Catalog supports the following workflows:

Setup and configuration

The following sections provide step-by-step instructions for connecting Wherobots to your Databricks Unity Catalog.

Before you start

Before you can use this feature, make sure you have the following:
  • A Wherobots Account within a Professional, Innovation, or Enterprise Edition Organization. Your Account needs to be assigned an Admin role to add the foreign catalog in Data Hub.
  • A pre-existing Managed Delta or Managed Iceberg table within the Databricks platform.
  • A pre-existing Unity Catalog in Databricks.
  • The necessary permissions in Databricks, as described below.

Databricks authentication

Databricks Unity Catalog foreign catalogs do not use a Wherobots Cloud connection intermediary. Wherobots authenticates directly to your Databricks workspace using the credentials for your table format:
  • Unity Delta: Personal Access Token (PAT)
  • Unity Iceberg: OAuth client credentials (client_id and client_secret)
Make sure you have the necessary permissions in Databricks, as described below.

Databricks permissions

The permissions you need depend on your read/write workflow.
  • If you’re reading from a Managed Delta Table and writing to a Wherobots-managed Catalog:
    • Create a Personal Access Token (PAT).
    Best practice: Use a Databricks Service PrincipalTo mitigate security concerns, you should adhere to the principle of least privilege by attaching the PAT to a Databricks service principal instead of an individual user and granting it only the minimum permissions required.
    • The following permissions are required:
    • If you’re reading from a Managed Iceberg Table and writing to a Wherobots-managed Catalog:
    • The following permissions are required:

Add the catalog in Wherobots

To create a catalog based on your Databricks Unity Catalog, follow these steps:
  1. In Wherobots Cloud, open the Data Hub.
  2. Start adding a catalog using either the Add Catalog button or the Data Hub explorer:
    Select the Unity Catalog card.The Data Hub empty state showing the Unity Catalog, Amazon Glue, and Storage Integration cards
    Either method opens the Connect to Databricks Unity Catalog dialog.
  3. Enter a Name that exactly matches the catalog name in your Databricks Workspace, then enter your Workspace URL (https://<workspace ID>.cloud.databricks.com). Wherobots connects directly to this Databricks URL; no Wherobots Cloud connection is required.
  4. Select Delta or Iceberg to match the format of your source table, then enter the credentials for that type:
    • Enter your Personal Access Token (PAT). Delta Table
    • Click Add.
    Runtime Restart Required After Data IntegrationTo use new storage integrations or catalogs in your notebooks, you must start a new runtime. Notebooks can only access storage integrations or catalogs that were created before the runtime started.
Once your catalog is connected, see Reading and Writing Unity Catalog Tables to query and write your Unity Catalog data from a Wherobots Notebook.

Next steps

After connecting your Databricks Unity Catalog, you can read and write tables from a Wherobots Notebook. Read more for instructions:

Read and write Unity Catalog tables

Query Databricks Unity Catalog tables from a Wherobots Notebook and write results to supported destinations.

Try it in a notebook

Walk through a hands-on tutorial reading Unity Catalog Delta tables in Wherobots.

Usage and limitations

  • Catalog Naming: You cannot use a local alias for a catalog. If you have a pre-existing catalog in your Wherobots Organization named wherobots, trying to connect a Databricks catalog with the name wherobots will cause a permanent naming conflict and must be avoided.
  • Catalog Limit: The integration supports a limit of 10 foreign catalogs per Organization.
  • UniForm: If you use Databricks’ Universal Format (UniForm) to enable Iceberg reads on a Delta table, that table will be read-only.

Workflows explained

The following table provides a detailed summary of each workflow and its intended use case.