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

"cityofnewyork-us/jobs-nyc-postings-kpav-sd4t:latest"."jobs_nyc_postings"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "salary_range_from", -- Proposed salary from: range. (Can be 0)
    "posting_type", -- Internal or External job posting.
    "process_date", -- Dataset created date.
    "preferred_skills", -- Preferred skills for this position.
    "residency_requirement", -- Residency requirements for this position.
    "career_level", -- This denotes the career level of the job. The possible career levels. 
    "division_work_unit", -- Department/Division within the hiring agency.
    "posting_updated", -- Last Modification Date.
    "recruitment_contact", -- Recruitment contact information.
    "business_title", -- Business title
    "level", -- Civil Service title level
    "posting_date", -- Date that the position was posted.
    "civil_service_title", -- Civil Service title
    "salary_range_to", -- Proposed salary to: range. (Can be 0)
    "salary_frequency", -- Proposed salary frequency
    "job_id", -- Job Opening ID.
    "work_location", -- Agency location.
    "work_location_1", -- Specific work location for this opening.
    "number_of_positions", -- Number of vacancies to be filled.
    "job_description", -- Description of the job responsibilities for this position.
    "title_classification", -- The civil service title jurisdiction classification that corresponds to the civil service title posted. The civil service title classification. 
    "post_until", -- Date Posting will be removed.  (Blank means post until filled)
    "title_code_no", -- Civil Service title Code
    "full_time_part_time_indicator", -- "This denotes whether the job is a full time or part time employment. "
    "hours_shift", -- Working hours and shift information.
    "minimum_qual_requirements", -- Minimum qualifications required for position.
    "agency", -- Name of the City agency where the vacancy exists.
    "job_category", -- The occupational group in which the posted job belongs. 
    "to_apply", -- Instructions on how to apply for this postion. 
    "additional_information" -- Additional information provided by the hiring agency.
FROM
    "cityofnewyork-us/jobs-nyc-postings-kpav-sd4t:latest"."jobs_nyc_postings"
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 cityofnewyork-us/jobs-nyc-postings-kpav-sd4t with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.cityofnewyork.us. When you querycityofnewyork-us/jobs-nyc-postings-kpav-sd4t: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.cityofnewyork.us, 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 \
  "cityofnewyork-us/jobs-nyc-postings-kpav-sd4t" \
  --handler-options '{
    "domain": "data.cityofnewyork.us",
    "tables": {
        "jobs_nyc_postings": "kpav-sd4t"
    }
}'

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, cityofnewyork-us/jobs-nyc-postings-kpav-sd4t is just another Postgres schema.