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 2020_ncfo_operators_file table in this repository, by referencing it like:
"bts-gov/2020-ncfo-operators-file-wgzf-9czk:latest"."2020_ncfo_operators_file"or in a full query, like:
SELECT
":id", -- Socrata column ID
"trip_purpose_pleasure", -- Indicates whether the operator services pleasure transit trips
"pub_fund_prog_1", -- Name of public funding program 1
"other_funding_revenue", -- Percentage of annual revenue from all other revenue sources
"local_funding_revenue", -- Percentage of annual revenue from direct public funding (local)
"pub_fund_prog_7", -- Name of public funding program 7
"pub_fund_source_1", -- Name of public funding agency 1
"pub_fund_source_3", -- Name of public funding agency 3
"pub_fund_source_4", -- Name of public funding agency 4
"pub_fund_source_5", -- Name of public funding agency 5
"pub_fund_source_6", -- Name of public funding agency 6
"pub_fund_source_7", -- Name of public funding agency 7
"pub_fund_source_8", -- Name of public funding agency 8
"pub_fund_type_1", -- Public funding type 1
"pub_fund_type_2", -- Public funding type 2
"pub_fund_type_3", -- Public funding type 3
"pub_fund_type_4", -- Public funding type 4
"pub_fund_type_6", -- Public funding type 6
"pub_fund_type_7", -- Public funding type 7
"pub_fund_type_8", -- Public funding type 8
"state_funding_revenue", -- Percentage of annual revenue from direct public funding (state)
"trip_purpose_lifeline", -- Indicates whether the operator services lifeline trips to mainland
"trip_purpose_nps", -- Indicates whether the operator services trips to National Park Service locations
"trip_purpose_other_desc", -- Indicates the other purposes
"pub_fund_source_2", -- Name of public funding agency 2
"trip_purpose_roadway_conn", -- Indicates whether the operator services roadway connector trips
"url", -- Company Web Site
"op_strzip", -- Zip code of the ferry operator mailing address
"op_country", -- Country of the ferry operator street address
"census_year", -- Year of the census
"private_contract_revenue", -- Percentage of annual revenues from private contract payments
"trip_purpose_other", -- Indicates whether the operator services trips for other purposes
"pub_fund_prog_3", -- Name of public funding program 3
"pub_fund_prog_8", -- Name of public funding program 8
"operator_id", -- A unique numeric identifier assigned to each ferry operator
"op_strcity", -- City of the ferry operator mailing address
"ticket_revenue", -- Percentage of annual revenue from individual purchased tickets or fares (including fare cards)
"public_contract_revenue", -- Percentage of annual revenue from contracts with public agencies
"data_year", -- Year of the collected data
"pub_fund_prog_5", -- Name of public funding program 5
"trip_purpose_commuter_transit", -- Indicates whether the operator services commuter transit trips
"trip_purpose_emergency", -- Indicates whether the operator services emergency transit trips
"pub_fund_type_5", -- Public funding type 5
"accepts_public_funding", -- Indicates whether the operator accepts public funding
"advertising_revenue", -- Percentage of annual revenue from advertising contract payments
"federal_funding_revenue", -- Percentage of annual revenue from direct public funding (federal)
"federal_state_local", -- Completing the census on behalf of a federal, state or local government agency
"op_state", -- State of the ferry operator mailing address
"operator_name", -- The complete company name of the ferry operator
"pub_fund_prog_4", -- Name of public funding program 4
"pub_fund_prog_2", -- Name of public funding program 2
"pub_fund_prog_6" -- Name of public funding program 6
FROM
"bts-gov/2020-ncfo-operators-file-wgzf-9czk:latest"."2020_ncfo_operators_file"
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 bts-gov/2020-ncfo-operators-file-wgzf-9czk 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 bts-gov/2020-ncfo-operators-file-wgzf-9czk: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 bts-gov/2020-ncfo-operators-file-wgzf-9czkCheckout 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 bts-gov/2020-ncfo-operators-file-wgzf-9czk:latestThis will download all the objects for the latest tag of bts-gov/2020-ncfo-operators-file-wgzf-9czk 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 bts-gov/2020-ncfo-operators-file-wgzf-9czk: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 bts-gov/2020-ncfo-operators-file-wgzf-9czk: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, bts-gov/2020-ncfo-operators-file-wgzf-9czk is just another Postgres schema.