Icon for Socrata external plugin

Query the Data Delivery Network

Query the DDN

The easiest way to query any data on Splitgraph is via the "Data Delivery Network" (DDN). The DDN is a single endpoint that speaks the PostgreSQL wire protocol. Any Splitgraph user can connect to it at and query any version of over 40,000 datasets that are hosted or proxied by Splitgraph.

For example, you can query the iowa_unemployment_insurance_benefit_payments_and table in this repository, by referencing it like:


or in a full query, like:

    ":id", -- Socrata column ID
    "final_payments", -- Final Payment:  Number of claimants drawing the final payment of their original entitlement of regular Unemployment Insurance (exhaustees). ETA-5159 (303-26)
    "ui_recipients", -- Benefit Recipients:  The number of claimants receiving at least one regular UI benefit payment during the month. State report: [NX.UI.P001.NVSAM.CNTY.BENEFITS (Recipients - UI)]
    "weeks_compensated", -- Weeks Compensated:  The number of weeks claimed for which UI benefits are paid. Weeks compensated for partial unemployment are included. ETA-5159 (301-14)
    "benefits_paid", -- Benefits Paid:  Unemployment benefits paid to individuals under the regular state UI program.  ETA-5159 (302-14)
    "initial_claims", -- Initial Claim:  Initial claims include new claims and additional claims.  A new claim is any notice of unemployment filed to request a determination of entitlement to and eligibility for compensation.  An additional claim is a notice of unemployment filed to begin a subsequent period of eligibility within a benefit year or period of eligibility.  ETA-5159 (101-1)
    "first_payments", -- First Payment:  The number of claimants receiving their UI benefit first payment in a benefit year for a week of unemployment claimed under the state UI program. ETA-5159 (303-21)
    "average_weekly_benefit", -- Average Weekly Benefit:  UI benefits paid divided by the number of weeks compensated.  Benefits paid for partial unemployment are included. 
    "continued_weeks_claimed", -- Continued Weeks Claimed:  Number of weeks of UI benefits claimed. ETA-5159 [(201-10) plus (201-11)]
    "month" -- Stored as month ending date.  Displayed as month.
LIMIT 100;

Connecting to the DDN is easy. All you need is an existing SQL client that can connect to Postgres. As long as you have a SQL client ready, you'll be able to query mydata-iowa-gov/iowa-unemployment-insurance-benefit-payments-and-jpje-kkb9 with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at When you querymydata-iowa-gov/iowa-unemployment-insurance-benefit-payments-and-jpje-kkb9:latest on the DDN, we "mount" the repository using the socrata mount handler. The mount handler proxies your SQL query to the upstream data source, translating it from SQL to the relevant language (in this case SoQL).

We also cache query responses on the DDN, but we run the DDN on multiple nodes so a CACHE_HIT is only guaranteed for subsequent queries that land on the same node.

Query Your Local Engine

Install Splitgraph Locally
bash -c "$(curl -sL"

Read the installation docs.

Splitgraph Cloud is built around Splitgraph Core (GitHub), which includes a local Splitgraph Engine packaged as a Docker image. Splitgraph Cloud is basically a scaled-up version of that local Engine. When you query the Data Delivery Network or the REST API, we mount the relevant datasets in an Engine on our servers and execute your query on it.

It's possible to run this engine locally. You'll need a Mac, Windows or Linux system to install sgr, and a Docker installation to run the engine. You don't need to know how to actually use Docker; sgrcan manage the image, container and volume for you.

There are a few ways to ingest data into the local engine.

For external repositories (like this repository), the Splitgraph Engine can "mount" upstream data sources by using sgr mount. This feature is built around Postgres Foreign Data Wrappers (FDW). You can write custom "mount handlers" for any upstream data source. For an example, we blogged about making a custom mount handler for HackerNews stories.

For hosted datasets, where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.

Mounting Data

This repository is an external repository. It's not hosted by Splitgraph. It is hosted by, and Splitgraph indexes it. This means it is not an actual Splitgraph image, so you cannot use sgr clone to get the data. Instead, you can use the socrata adapter with the sgr mount command. Then, if you want, you can import the data and turn it into a Splitgraph image that others can clone.

First, install Splitgraph if you haven't already.

Mount the table with sgr mount

sgr mount socrata \
  "mydata-iowa-gov/iowa-unemployment-insurance-benefit-payments-and-jpje-kkb9" \
  --handler-options '{
    "domain": "",
    "tables": {
        "iowa_unemployment_insurance_benefit_payments_and": "jpje-kkb9"

That's it! Now you can query the data in the mounted table like any other Postgres table.

Query the data with your existing tools

Once you've loaded the data into your local Splitgraph engine, you can query it with any of your existing tools. As far as they're concerned, mydata-iowa-gov/iowa-unemployment-insurance-benefit-payments-and-jpje-kkb9 is just another Postgres schema.