• capital projects
  • construction
  • highway
  • roadbed
  • sidewalk
  • + 1

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


or in a full query, like:

    ":id", -- Socrata column ID
    "projtitle", -- The full title of the capital project.
    "projectsta", -- The current status of the capital project.
    "projecttyp", -- The three letter code that identifies the type of work being performed.
    "projectt_1", -- The full description on the type of work that is being performed for the capital project.
    "designstar", -- The date the design phase of the capital project starts.
    "construc_1", -- The date the project will be completed.
    "otherscope", -- Brief description for any other capital projects.
    "projectcos", -- Estimated cost of the capital project.
    "fromstreet", -- The nearest cross street from where the capital project is taking place.
    "overallsco", -- Overall brief description of the capital projects.
    "projectid", -- A unique number assigned to identify a capital project.
    "projectdes", -- The description of the capital project.
    "fmsid", -- The unique budget code assigned to the capital project in the citywide Financial Management System (FMS).
    "onstreetna", -- The street where the capital project is taking place.
    "oftcode", -- A 18 digit code consisting of three 6-digit street codes representing On-From-To streets as returned by GeoSupport functions.
    "projectjus", -- The reason for the initiation of the project.
    "managingag", -- The agency that manages the project in three letter acronym.
    "fmsagencyi", -- The three number citywide Financial Management System (FMS) agency code.
    "constructi", -- The fiscal year of the capital project.
    "boroughnam", -- The New York City borough where the project would take place.
    "leadagency", -- The primary agency leading the capital project in three letter acronym.
    "designfy", -- The fiscal year in which the design was initiated.
    "safetyscop", -- Brief description for a safety related capital projects.
    "currentfun", -- Estimated current funding allocated for this capital project.
    "tostreetna" -- The nearest cross street to where the capital project is taking place.
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 cityofnewyork-us/street-and-highway-capital-reconstruction-projects-97nd-ff3i with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at When you querycityofnewyork-us/street-and-highway-capital-reconstruction-projects-97nd-ff3i: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 \
  "cityofnewyork-us/street-and-highway-capital-reconstruction-projects-97nd-ff3i" \
  --handler-options '{
    "domain": "",
    "tables": {
        "street_and_highway_capital_reconstruction_projects": "97nd-ff3i"

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, cityofnewyork-us/street-and-highway-capital-reconstruction-projects-97nd-ff3i is just another Postgres schema.

Related Documentation: