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

"datahub-austintexas-gov/open-data-portal-datasets-austin-transportation-28ys-ieqv:latest"."open_data_portal_datasets_austin_transportation"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "attribution", -- The attribution of the asset, if one has been provided
    "page_views_total", -- Number of views of this asset since creation.
    "automation_method_other", -- Free text field that allows for descriptions of automation if the dropdown in automation_method is not correct.
    "type", -- The type of the asset (eg. dataset, story, filter, href, file).
    "description", -- The description for the asset, if one has been provided.
    "is_public", -- Single true or false column on whether the dataset is publicly available to use and view.
    "update_frequency", -- Timeframe this dataset is expected to be updated at.
    "program_name", -- Free text field that describes the program name of the dataset (if applicable).
    "dataset_url", -- Link to the asset's webpage
    "page_views_last_week", -- Number of views of this asset last week.
    "name", -- The title of the asset.
    "cover_image_url", -- The URL link of the cover image if applicable.
    "id", -- The unique identifier for the asset.
    "page_views_last_month", -- Number of views of this asset last month.
    "owner_display_name", -- The display name of the dataset owner's account.
    "publication_date", -- Date this asset was published.
    "tags", -- Multi-select field of the tags of this dataset (if applicable)
    "data_updated_at", -- The timestamp at which the asset data was last updated.
    "updatedat", -- The timestamp at which the asset was last updated.
    "strategic_area", -- Single choice field that is optional to pick what strategic outcome this dataset can represent.
    "department_name", -- Name of the dataset's owning department.
    "metadata_updated_at", -- The timestamp at which the asset metadata was last updated.
    "automation_method", -- Dropdown selection describing how the dataset is automated (if applicable)
    "createdat", -- The timestamp at which the asset was created.
    "row_count", -- Number of rows this dataset has (only for dataset type).
    "download_count", -- The number of times this asset has been downloaded.
    "spatial_information" -- Free text field that describes if there is geospatial information with this dataset.
FROM
    "datahub-austintexas-gov/open-data-portal-datasets-austin-transportation-28ys-ieqv:latest"."open_data_portal_datasets_austin_transportation"
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 datahub-austintexas-gov/open-data-portal-datasets-austin-transportation-28ys-ieqv with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at datahub.austintexas.gov. When you querydatahub-austintexas-gov/open-data-portal-datasets-austin-transportation-28ys-ieqv: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 datahub.austintexas.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 \
  "datahub-austintexas-gov/open-data-portal-datasets-austin-transportation-28ys-ieqv" \
  --handler-options '{
    "domain": "datahub.austintexas.gov",
    "tables": {
        "open_data_portal_datasets_austin_transportation": "28ys-ieqv"
    }
}'

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, datahub-austintexas-gov/open-data-portal-datasets-austin-transportation-28ys-ieqv is just another Postgres schema.