Query the Data Delivery Network

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 data.splitgraph.com:5432 and query any version of over 40,000 datasets that are hosted or proxied by Splitgraph.

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

"cityofnewyork-us/dot-inhouse-street-resurfacing-projects-ffaf-8mrv:latest"."dot_inhouse_street_resurfacing_projects"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "location_to_street", -- The closest intersection to the on street in the opposite direction. 
    "project_speed_bumps", -- The street block contains a speed reducer.
    "location_segment_id", -- Unique identifier for the street block. 
    "location_community_board", -- The three digit borough code and community board where the street resurfacing takes place. 
    "project_status", -- The project status. 
    "project_id", -- The unique identifier assigned to the capital project. 
    "location_status", -- The project paving and milling status at the location. 
    "location_actual_paving_square", -- The amount of square yards paved. 
    "oft_code", -- A unique numerical 18 digit code for the On- From- To location of the street segment. 
    "location_actual_paving_end_date", -- The actual end date for road paving. 
    "location_actual_paving_start_date", -- The actual start date for road paving. 
    "location_from_street", -- The closest intersection to the on street in one direction. 
    "location_actual_lane_miles", -- The number of lane miles paved. 
    "location_actual_protect_until", -- The actual date the street is protected until after street replacement. 
    "project_type", -- Flags whether the street resurfacing project is for the block or intersection
    "location_actual_milling_end_date", -- The actual end date for road milling.
    "borough_code", -- The borough of the street segment in one letter format. 
    "location_actual_milling_start_date", -- The actual start date for road milling. 
    "location_on_street" -- The name of the street where the construction embargo is taking place.
FROM
    "cityofnewyork-us/dot-inhouse-street-resurfacing-projects-ffaf-8mrv:latest"."dot_inhouse_street_resurfacing_projects"
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/dot-inhouse-street-resurfacing-projects-ffaf-8mrv with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.cityofnewyork.us. When you querycityofnewyork-us/dot-inhouse-street-resurfacing-projects-ffaf-8mrv: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

bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"

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 data.cityofnewyork.us, 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/dot-inhouse-street-resurfacing-projects-ffaf-8mrv" \
  --handler-options '{
    "domain": "data.cityofnewyork.us",
    "tables": {
        "dot_inhouse_street_resurfacing_projects": "ffaf-8mrv"
    }
}'

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/dot-inhouse-street-resurfacing-projects-ffaf-8mrv is just another Postgres schema.