Query the Data Delivery Network
Query the DDNThe 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 copa_cases_by_complainant_or_subject table in this repository, by referencing it like:
"cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie:latest"."copa_cases_by_complainant_or_subject"or in a full query, like:
SELECT
":id", -- Socrata column ID
"log_no", -- A unique identifier for the case record. The log number can be used to link records in other datasets that contain a log number column.
"complaint_day", -- The day of the week component of COMPLAINT_DATE. Sunday=1
"complaint_month", -- The month component of COMPLAINT_DATE.
"sex_of_complainant", -- The sex of the complainant or subject.
"complaint_date", -- The date that the complaint or notification was made to IPRA/COPA and the record was created.
"current_category", -- The category of the primary allegation against the involved CPD member.
"finding_code", -- The overall current case finding, ranked by the following hierarchy: Sustained, Not Sustained, Unfounded, Exonerated, No Affidavit, and No Finding. “Current_Finding” means that even after COPA has completed an investigation and made a recommended finding, the finding can change given post-COPA processes, including Police Department review, Police Board adjudication, and grievance and arbitration processes.
"age_of_complainant", -- The age of the complainant or subject.
"police_shooting", -- Whether or not the case is a police shooting.
"assignment", -- The jurisdictional assignment for the complaint case.
"case_type", -- Whether a case is a complaint, a notification, or miscellaneous.
"current_status", -- The current status of the case investigation, as of the date the data were last published.
"beat", -- The CPD beat in which the incident occurred. If more than one beat was involved, the values are separated by the pipe (|) character.
"race_of_complainant", -- The race or ethnicity of the complainant or subject.
"complaint_hour" -- The hour of the day component of COMPLAINT_DATE.
FROM
"cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie:latest"."copa_cases_by_complainant_or_subject"
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 cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie with SQL in under 60 seconds.
Query Your Local Engine
bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"Read the installation docs.
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, 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 (like this repository), where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.
Cloning Data
Because cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie:latest is a Splitgraph Image, you can clone the data from Spltgraph Cloud to your local engine, where you can query it like any other Postgres database, using any of your existing tools.
First, install Splitgraph if you haven't already.
Clone the metadata with sgr clone
This will be quick, and does not download the actual data.
sgr clone cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmieCheckout the data
Once you've cloned the data, you need to "checkout" the tag that you want. For example, to checkout the latest tag:
sgr checkout cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie:latestThis will download all the objects for the latest tag of cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie and load them into the Splitgraph Engine. Depending on your connection speed and the size of the data, you will need to wait for the checkout to complete. Once it's complete, you will be able to query the data like you would any other Postgres database.
Alternatively, use "layered checkout" to avoid downloading all the data
The data in cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie:latest is 0 bytes. If this is too big to download all at once, or perhaps you only need to query a subset of it, you can use a layered checkout.:
sgr checkout --layered cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie:latestThis will not download all the data, but it will create a schema comprised of foreign tables, that you can query as you would any other data. Splitgraph will lazily download the required objects as you query the data. In some cases, this might be faster or more efficient than a regular checkout.
Read the layered querying documentation to learn about when and why you might want to use layered queries.
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, cityofchicago/copa-cases-by-complainant-or-subject-vnz2-rmie is just another Postgres schema.