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

"edmonton-ca/311-requests-2019-rb8e-6i3k:latest"."311_requests_2019"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "nbhd_latitude", -- The latitude value for the centroid of the Neighbourhood
    "svc_area_svc_descr", -- A combination of Service Area and Service Description so visualizations can be created
    "svc_area_svc_cat", -- A combination of Service Area and Service Category so visualizations can be created
    "svc_cat_svc_area", -- A combination of Service Category and Service Area so visualizations can be created
    "neighbourhood", -- The name given to a Neighbourhood
    "neighbourhood_id", -- Unique number identifier given to Neighbourhoods throughout Edmonton
    "service_area", -- The business area that is responsible for the service. 
    "service_description", -- Provides a general description of the service request. 
    "service_category", -- The type of action or service request.
    "status_detail", -- Certain request types may include additional details describing the progress or action associated with the request. The state of progress the request is at. 
    "request_status", -- The stage at which your request is at, Open or Closed. 
    "month_number", -- The numeric Month in which the 311 ticket was created.
    "date_created", -- The date the service request ticket was created 
    "date_closed", -- The date the appropriate City department has investigated the concern and identified steps to resolve your request. Action for resolving the issue may be dependent on priority and weather conditions or your issue has been closed due to lack of information including contact details.
    "row_id", -- System generated value for each 311 request created in the system
    "nbhd_longitude", -- The longitude value for the centroid of the Neighbourhood
    "interaction_channel", -- The channel or method in which the request was initiated
    "month", -- The Month in which the 311 ticket was created.
    "ward", -- A unique number give to a geographical area representing a electoral area
    "year", -- The Year in which the 311 ticket was created.
    "nbhd_point_location", -- The point location of the centroid of the Neighbourhood used for mapping purposes.
    "referral_type" -- The action associated with  how the request was handled either information provided or transferred to a business area. 
FROM
    "edmonton-ca/311-requests-2019-rb8e-6i3k:latest"."311_requests_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 edmonton-ca/311-requests-2019-rb8e-6i3k with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.edmonton.ca. When you queryedmonton-ca/311-requests-2019-rb8e-6i3k: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.edmonton.ca, 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 \
  "edmonton-ca/311-requests-2019-rb8e-6i3k" \
  --handler-options '{
    "domain": "data.edmonton.ca",
    "tables": {
        "311_requests_2019": "rb8e-6i3k"
    }
}'

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, edmonton-ca/311-requests-2019-rb8e-6i3k is just another Postgres schema.