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 closed_discrimination_complaint_cases_in_iowa table in this repository, by referencing it like:
"mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br:latest"."closed_discrimination_complaint_cases_in_iowa"or in a full query, like:
SELECT
":id", -- Socrata column ID
"public_accom", -- "Yes" indicates that the complaint was associated with public accommodations (public services and buildings)
"date_closed", -- Date the discrimination case was closed.
"date_opened", -- Date the discrimination case was opened.
"color", -- "Yes" indicates that the basis of the complaint is associated with the complainant's color.
"nat_org", -- "Yes" indicates that the basis of the complaint is associated with the complainant's national origin.
"disability", -- "Yes" indicates that the basis of the complaint is associated with the complainant's disability.
"religion_type", -- Lists the complainant's religion when the basis of the complain was associated with the complainant's religion. Otherwise field is null.
"housing", -- "Yes" indicates that the complaint was associated with housing.
"processor", -- Indicates whether the discrimination complaint was processed by ICRC, EEOC or a local agency
"creed", -- "Yes" indicates that the basis of the complaint is associated with the complainant's creed.
"sex_type", -- Lists the complainant's sex when the basis of the complain was associated with the complainant's sex. Otherwise field is null.
"employment", -- "Yes" indicates that the complaint was associated with employment.
"education", -- "Yes" indicates that the complaint was associated with education.
"marital_status", -- "Yes" indicates that the basis of the complaint is associated with the complainant's marital status.
"not_jurisdictional", -- "Yes" indicates that the case did NOT meet established jurisdictional requirements.
"sex_orientation", -- "Yes" indicates that the basis of the complaint is associated with the complainant's sexual orientation.
"sex", -- "Yes" indicates that the basis of the complaint is associated with the complainant's sex.
"not_timely", -- "Yes" indicates that the complaint was NOT received within 300 days of the alleged incident.
"processing_days", -- Calculates the number of the days between the date the case was open to the date the case was closed.
"nat_org_type", -- Lists the complainant's national origin when the basis of the complain was associated with the complainant's national origin. Otherwise field is null.
"race", -- "Yes" indicates that the basis of the complaint is associated with the complainant's race.
"credit", -- "Yes" indicates that the complaint was associated with credit.
"closure_desc", -- Closure description highlights the reason for closing the discrimination case.
"fy", -- Fiscal Year (July 1 - June 30, labeled for the year that it ends) the discrimination case was closed.
"gender_identity", -- "Yes" indicates that the basis of the complaint is associated with the complainant's gender identity.
"religion", -- "Yes" indicates that the basis of the complaint is associated with the complainant's religion.
"race_type", -- Lists the complainant's race when the basis of the complain was associated with the complainant's race. Otherwise field is null.
"age", -- "Yes" indicates that the basis of the complaint is associated with the complainant's age.
"retaliation", -- "Yes" indicates that the basis of the complaint is associated with retaliation.
"pregnancy", -- "Yes" indicates that the basis of the complaint is associated with the complainant's pregnancy.
"family_status" -- "Yes" indicates that the basis of the complaint is associated with the complainant's familial status.
FROM
"mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br:latest"."closed_discrimination_complaint_cases_in_iowa"
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/closed-discrimination-complaint-cases-in-iowa-ha33-u9br 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 mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br: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 mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9brCheckout 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 mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br:latestThis will download all the objects for the latest tag of mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br 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 mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br: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 mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br: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, mydata-iowa-gov/closed-discrimination-complaint-cases-in-iowa-ha33-u9br is just another Postgres schema.