• cares act
  • covid-19
  • pandemic
  • recovery
  • sub recipient awards

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 procotol. 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_pandemic_recovery_reporting_sub_recipient table in this repository, by referencing it like:


or in a full query, like:

    ":id", -- Socrata column ID
    "award_amount", -- The total amount of the award.
    "performance_start", -- The date on which effort begins or the award is otherwise effective.
    "award_description", -- A brief description of the purpose of the award.
    "award_number", -- A unique identifier assigned by the state agency to facilitate the tracking of the award.
    "city", -- City where the vendor is physically located.
    "secondary_address", -- Name of building, and unit designator (i.e. FL - floor, STE - suite, RM - room, etc.) where the vendor is physically located.
    "primary_address", -- Street address where the vendor is physically located.
    "doing_business_as", -- Name the vendor receiving the award is doing business as if applicable.
    "legal_name", -- Legal name of the vendor receiving the sub award.
    "vendor_number", -- Unique eleven character identifier used in the State Accounting System for payments to the vendor receiving the award.
    "federal_program_title", -- Name of the Federal program the sub recipient award was funded by.
    "federal_award_number", -- This shall be the federal award number for the federal award that is funding the sub recipient award.
    "record_id", -- Unique identifier for the record; concatenation of state_dept_no, and award_number with a dash (“-”) in between.
    "location", -- Geolocation of the vendor’s physical  address.
    "local_gov", -- Local government consists of cities, counties, townships, school districts and special-purpose districts.  A yes or true response indicates the sub recipient is a board, commission, agency or office of a local government.
    "performance_end", -- The date on which effort related to the award ends or is completed.
    "state_department", -- Name of the State Department making the award.
    "award_date", -- The date a binding agreement was executed.
    "zip", -- United States ZIP code (five digits) concatenated with the additional +4 digits where the vendor is physically located.
    "state_dept_no", -- The three digit code used in the State Accounting System of the department making the award.
    "vendor_duns", -- The unique 9-digit number assigned to the vendor by Dun and Bradstreet (D&B) referred to as the DUNS®
    "state", -- United States Postal Service (USPS) two-letter abbreviation for the state where the vendor is physically located.
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-pandemic-recovery-reporting-sub-recipient-p385-znwp 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-pandemic-recovery-reporting-sub-recipient-p385-znwp: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"

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-pandemic-recovery-reporting-sub-recipient-p385-znwp" \
  --handler-options '{
    "domain": "",
    "tables": {
        "iowa_pandemic_recovery_reporting_sub_recipient": "p385-znwp"

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-pandemic-recovery-reporting-sub-recipient-p385-znwp is just another Postgres schema.

Related Documentation: