• alaska
  • bering sea
  • biota
  • bottom trawl
  • disease
  • + 2

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


or in a full query, like:

    ":id", -- Socrata column ID
    "latitude", -- The latitude (decimal degrees) at the start of the haul
    "longitude", -- The longitude (decimal degrees) at the start of the haul
    "cruise", -- Six-digit number identifying the cruise number
    "shell_cond", -- Carapace shell condition (0 = premolt, 2 = new hardshell, 3 = oldshell, 4 = oldshell, 5 = very oldshell)
    "year", -- Year specimen was collected
    "vessel", -- Vessel Codes;
    "size", -- Carapace width measurement (mm)
    "host_tissue", -- Description of body part collected from organism
    "species_name", -- The scientific name of the organism
    "chela", -- Measurement of height of right chela (mm). Null = information not reported
    "egg_color", -- female reproductive condition based on the color of the eggs (0 = no eggs, 4 = orange, null = no egg color information reported or does not apply),
    "egg_cond", -- Female reproductive condition on the condition of the eggs (0 = no eggs, 1 = uneyed, null = no egg condition information reported or does not apply)
    "sex", -- Sex of crab (1 = male, 2 = female)
    "haul", -- Haul within a cruise. It is a sequential number, in chronological order of occurrence
    "spno", -- Specimen number
    "pcr_result", -- PCR Result (0 = negative for Hematodinium DNA, 1 = positive for Hematodinium DNA, 3 = undetermined, at the limit of detection).
    "bottom_temp", -- Weighted average temperature (in tenths of a degree Celsius)
    "bottom_depth", -- Weighted average depth (m)
    "station_id", -- Alphanumeric station ID that identifies a Bering Sea crab-groundfish slope survey trawl location
    "clutch", -- Female reproductive condition based on the size of the egg clutch (0 = immature, 1 = mature female no eggs, 2 = trace to 1/8, 3 = 1/4, 4 = 1/2, 5 = 3/4, 6 = full, null = no egg clutch information reported or does not apply).
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 noaa-fisheries-afsc-data-socrata/afscracesappathobiology-2016-bitter-crab-disease-s82g-ghj7 with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at When you querynoaa-fisheries-afsc-data-socrata/afscracesappathobiology-2016-bitter-crab-disease-s82g-ghj7: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 \
  "noaa-fisheries-afsc-data-socrata/afscracesappathobiology-2016-bitter-crab-disease-s82g-ghj7" \
  --handler-options '{
    "domain": "",
    "tables": {
        "afscracesappathobiology_2016_bitter_crab_disease": "s82g-ghj7"

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, noaa-fisheries-afsc-data-socrata/afscracesappathobiology-2016-bitter-crab-disease-s82g-ghj7 is just another Postgres schema.

Related Documentation: