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


or in a full query, like:

    ":id", -- Socrata column ID
    "council_strategic_outcome", -- Associated Council strategic outcome as assigned by the Office of the City Auditor.
    "date_report_issued", -- The month and year the audit report was issued.
    "dept", -- The department to whom the recommendation is addressed. In some cases, the department has been renamed or combined with other departments since the original report was issued.
    "report_title", -- The title of the audit report that included the recommendation.
    "follow_up_priority", -- Follow-up priority is determined by the Office of the City Auditor according to the following definitions: High (H) priority: Critical Citywide issue, priority, or initiative; recommendation poses immediate safety risk. Medium (M) priority: Issue, priority, or initiative is important but affects only one or few departments; recommendation does not pose immediate safety risk.  Low (L) priority: Issue, priority, or initiative is moderately important but only affects one or few departments; recommendation does not pose a safety risk.
    "status", -- Status as reported upon follow-up by Office of the City Auditor staff. A follow-up audit is an audit designed to test the efforts departments have made to address previously issued audit recommendations. During a follow-up audit, we may interview personnel, review documentation, and conduct inspections to determine if risks noted in prior audits have been effectively addressed. Follow-up audits are usually shorter and more focused than other performance audits, and the results of these audits are summarized and typically presented to the Audit and Finance Committee twice per year.
    "link_to_report", -- URL link to published report
    "note", -- Explains why recommendation is no longer applicable if status is listed as no longer applicable.
    "fy" -- The City of Austin's fiscal year runs from October 1 through September 30.
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 austintexas-gov/audit-recommendations-y4qq-mqk9 with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at When you queryaustintexas-gov/audit-recommendations-y4qq-mqk9: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 \
  "austintexas-gov/audit-recommendations-y4qq-mqk9" \
  --handler-options '{
    "domain": "",
    "tables": {
        "audit_recommendations": "y4qq-mqk9"

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, austintexas-gov/audit-recommendations-y4qq-mqk9 is just another Postgres schema.

Related Documentation: