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

"cityofnewyork-us/synthetic-turf-fields-weh8-3ujf:latest"."synthetic_turf_fields"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "parentid", -- The ID of the park property where the synthetic turf system is located
    "borough", -- The borough where the synthetic turf system is located.
    "construction_entity_spec", -- The specific entity responsible for the construction or reconstruction of the synthetic turf system.
    "contract_type", -- The type of funding contract utilized for the construction or replacement of the synthetic turf system.
    "maint_by", -- The party responsible for the general maintenance of the synthetic turf system.
    "infill_material", -- The type of fill used for systems of Turf_Type Infill.
    "description", -- Description of the synthetic turf system 
    "contract_number", -- The contract number under which the sythetic turf system was installed.
    "system", -- Unique ID for the synthetic turf system
    "department", -- The Parks maintenance district where the synthetic turf system is located
    "synturf_location", -- Closest cross streets to the synthetic turf system.
    "objectid", -- OBJECTID
    "system_type", -- The type of synthetic turf system.
    "jop", -- Indicates if the synthetic turf system is within a Jointly Operated Playground.
    "turf_type", -- The type of synthetic turf construction.
    "shape", -- Geometry of the synthetic turf system
    "retired", -- Indicates if the synthetic turf system is active or inactive
    "maint_by_spec", -- The specific party responsible for general maintenance of the synthetic turf system.
    "construction_entity", -- The entity responsible for the construction or replacement of the synthetic turf system.
    "commission_date" -- Approximate date synthetic turf system was opened to the public.
FROM
    "cityofnewyork-us/synthetic-turf-fields-weh8-3ujf:latest"."synthetic_turf_fields"
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/synthetic-turf-fields-weh8-3ujf 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/synthetic-turf-fields-weh8-3ujf: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/synthetic-turf-fields-weh8-3ujf" \
  --handler-options '{
    "domain": "data.cityofnewyork.us",
    "tables": {
        "synthetic_turf_fields": "weh8-3ujf"
    }
}'

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/synthetic-turf-fields-weh8-3ujf is just another Postgres schema.