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

"mydata-iowa-gov/city-budget-expenditures-by-fund-by-fiscal-year-k7cp-hq8y:latest"."city_budget_expenditures_by_fund_by_fiscal_year"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "value", -- Amount of budgeted expenditure from the fund listed, for the line item listed.
    "fund", -- City fund the expenditure is budgeted under.  Cities can expend money under seven individual fund types:  General Revenue, Special Revenue, TIF Special Revenue, Debt Service, Capital Projects, Permanent, Proprietary.
    "expense_line_item", -- Expenditure line item listing from the city budget.
    "fiscal_year", -- Fiscal year the data was extracted from - Fiscal year runs from July 1 to June 30.  Labeled for the calendar year the fiscal year ends.
    "city_name", -- Full city name
    "gnis_feature_id", -- The official federal identifier given to physical and cultural geographic features in the United States and associated areas based on ANSI INCITS 446-2008, Identifying Attributes for Named Physical and Cultural Geographic Features (Except Roads and Highways) of the United States, Its Territories, Outlying Areas, and Freely Associated Areas, and the Waters of the Same to the Limit of the Twelve-Mile Statutory Zone.
    "code", -- DOM city code
    "primary_point_coordinates", -- The official feature location is a single point (in decimal degrees) to which the city is associated in order to ensure positive and unique identification and association, also referred to as the primary point. The placing of the location point is generally at or near the geographic center of the city.
    "unique_line_id", -- Unique identification code for each data point.
    "expenditure_program" -- City expenditure program that the line item lies with in.
FROM
    "mydata-iowa-gov/city-budget-expenditures-by-fund-by-fiscal-year-k7cp-hq8y:latest"."city_budget_expenditures_by_fund_by_fiscal_year"
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 mydata-iowa-gov/city-budget-expenditures-by-fund-by-fiscal-year-k7cp-hq8y with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at mydata.iowa.gov. When you querymydata-iowa-gov/city-budget-expenditures-by-fund-by-fiscal-year-k7cp-hq8y: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 mydata.iowa.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 \
  "mydata-iowa-gov/city-budget-expenditures-by-fund-by-fiscal-year-k7cp-hq8y" \
  --handler-options '{
    "domain": "mydata.iowa.gov",
    "tables": {
        "city_budget_expenditures_by_fund_by_fiscal_year": "k7cp-hq8y"
    }
}'

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, mydata-iowa-gov/city-budget-expenditures-by-fund-by-fiscal-year-k7cp-hq8y is just another Postgres schema.