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

"nj-gov/sandy-cdl-master-data-4va7-qk4z:latest"."sandy_cdl_master_data"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "disbursed_amount", -- Amount of the loan that has been drawn down
    "obligated_amount", -- Funds committed to this project but not yet spent
    "applicant_name", -- Applicant/recipient of the funds.  Example: Stafford Township, Ocean County, etc.
    "municipality", -- This is the Municipality name or names that pertain to a particular project detail. This column may contain either one Municipality Name, multiple Municipality Names separated by commas, 'statewide', etc.
    "as_of_date", -- Agency data is up to date as of this date
    "status", -- Current status of project. Valid value: Completed
    "program_description", -- FEMA Provides funds to any eligible jurisdiction in a designated disaster area that has suffered a substantial loss of tax and other revenue
    "applicant_type", -- The type of applicant that the funds are being used for (Municipality, Schools, Services, etc.)
    "county", -- This is the name of a county where a Superstorm Sandy related project was worked on. This column may have a single name of a county, a value of 'Statewide' for projects being worked on at a State level, or it will contain the value 'Multi County' for those projects that cross more than on County. A comma separated list of multiple counties relating to one project detail is in the column.
    "project_description", -- FEMA Provides funds to any eligible jurisdiction in a designated disaster area that has suffered a substantial loss of tax and other revenue
    "funding_source", -- Federal Agency that is the funding source for FEMA CDL. Valid value: Community Disaster Loan
    "federal_agency", -- Federal Agency corresponding to the State Agency. Valid value: FEMA CDL
    "project_name" -- The type of applicant that the funds are being used for (Municipality, Schools, Services, etc.)
FROM
    "nj-gov/sandy-cdl-master-data-4va7-qk4z:latest"."sandy_cdl_master_data"
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 nj-gov/sandy-cdl-master-data-4va7-qk4z with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.nj.gov. When you querynj-gov/sandy-cdl-master-data-4va7-qk4z: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.nj.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 \
  "nj-gov/sandy-cdl-master-data-4va7-qk4z" \
  --handler-options '{
    "domain": "data.nj.gov",
    "tables": {
        "sandy_cdl_master_data": "4va7-qk4z"
    }
}'

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, nj-gov/sandy-cdl-master-data-4va7-qk4z is just another Postgres schema.