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


or in a full query, like:

    ":id", -- Socrata column ID
    "pctkm_persurvey", -- Percentage of streams in the survey network that the site represents. For each survey, this is the site's adjusted spatial weight, divided by the sum of all adjusted spatial weights in the survey x 100.
    "ecoreg3_nm", -- Level III ecorgion name as described in the Washington Master Sample: https://fortress.wa.gov/ecy/gispublic/DataDownload/EAP_ENV_MasterSample.htm
    "asweight_km", -- Adjusted Spatial Weights (kilometers) is the length of sample frame stream represented by the ranom site
    "x_deniobank_category", -- Condition class of AVG X DensioBank (%) when compared to reference conditions during 2009-2017. "Fair" for West is > 83.4 to 93.2% ; for East Moutains is > 72.4 to 87.8% ; for East Plateau is > 70.2 to 82.8%
    "site_id", -- Unique site identifier as provided by the Washington Master Sample: https://fortress.wa.gov/ecy/gispublic/DataDownload/EAP_ENV_MasterSample.htm
    "salmon_rr", -- Salmon Recevery Region, as described in the Washington Master Sample: https://fortress.wa.gov/ecy/gispublic/DataDownload/EAP_ENV_MasterSample.htm
    "stream", -- Description of the stream in which the site resides, based on nearest geographic identifier on the map in the Watershed Health Monitoirng Database: https://fortress.wa.gov/ecy/eimreporting/WHM/WHMSearch.aspx
    "status_and_trends_region", -- Watershed Health Monitoring region, based on SALMON_RR and modified as described in Publication No1 8-03-226 section 3.23.https://fortress.wa.gov/ecy/publications/documents/1803226.pdf
    "scoring_region", -- Region in which random sites are compared to reference sites, to evaluate riparian cover condition. West includes 3 Status and Trends Regions west of Cascade Ridge; East Plateau is Columbia Plateau Ecoregion; East Mountain is remainder
    "year", -- Year of observatiion
    "avg_x_densiobank", -- This is the average per year (1 or 2 observations) of X DensioBank values. Calculation of X DensionBank is described in the Metric Dictionary: https://fortress.wa.gov/ecy/publications/SummaryPages/1303033.html
    "region_round" -- Status and Trends Region and survey round (round 1 = 2009-2012; round 2 = 2013-2019)
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 wa-gov/watershed-health-monitoring-riparian-cover-using-x-asqd-efxe with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.wa.gov. When you querywa-gov/watershed-health-monitoring-riparian-cover-using-x-asqd-efxe: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 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.wa.gov, 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 \
  "wa-gov/watershed-health-monitoring-riparian-cover-using-x-asqd-efxe" \
  --handler-options '{
    "domain": "data.wa.gov",
    "tables": {
        "watershed_health_monitoring_riparian_cover_using_x": "asqd-efxe"

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, wa-gov/watershed-health-monitoring-riparian-cover-using-x-asqd-efxe is just another Postgres schema.

Related Documentation: