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 estimated_lost_wages_due_to_hospitalizations_for table in this repository, by referencing it like:
"pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw:latest"."estimated_lost_wages_due_to_hospitalizations_for"or in a full query, like:
SELECT
":id", -- Socrata column ID
"longitude", -- Longitude coordinates in degrees for a centroid point for geographic area.
"latitude", -- Latitude coordinates in degrees for a centroid point for geographic area.
"latitude_longitude", -- Latitude and longitude coordinates in degrees for a centroid point for geographic area.
"county_fips_code", -- Last 3 digits of the 5-digit Federal Information Processing Standard (FIPS) code that designate the county association. Each state has its own 2-digit number and each county within the state has its own 3-digit number which are combined into a 5-digit number to uniquely identify every US county.
"county_code_text", -- Pennsylvania county code provided as text (1-67 for counties sorted alphabetically, 0 for Commonwealth).
"estimated_lost_wages", -- Estimated wages lost due to hospitalization for opioid use. This value is the product of the number of days hospitalized and the average weekly wages for county of residence—as reported by the Bureau of Labor Statistics—divided by seven.
"time_period_dates", -- Start and end dates of time period.
"geographic_name", -- Name of geographic area.
"geocoded_column", -- Georeferenced column as a point used for creating visuals such as maps. A generic point for each county is supplied so a map can be created.
"state_fips_code", -- First 2 digits of the 5-digit Federal Information Processing Standard (FIPS) code that designate the state association. Each state has its own 2-digit number and each county within the state has its own 3-digit number which are combined into a 5-digit number to uniquely identify every US county.
"estimated_lost_state_income_tax_desc", -- Description of estimated lost state income tax revenue.
"number_of_days_hospitalized", -- Total number of days for which an individual was hospitalized for opioid use. These hospitalizations were identified as hospital stays that included a diagnosis code for opioid use disorder and a classification code for drug abuse and/or dependence or poisoning from drug use. Any hospitalization duration of at least four hours but less than one day counted as one day.
"year", -- Calendar year of measurement (January 1–December 31).
"county_code_number", -- Pennsylvania county code provided as a number (1-67 for counties, 0 for Commonwealth).
"estimated_lost_state_income_tax", -- Estimated state income tax revenue associated with lost wages while hospitalized; 3.07% of lost wages.
"estimated_lost_wages_desc", -- Description of estimated lost wages.
"number_of_days_hospitalized_notes", -- Describes suppression criteria for protecting confidentiality. Counts less than 11 are not provided.
"number_of_days_hospitalized_1", -- Description of number of days hospitalized.
"time_period", -- Period of measurement (annual, federal fiscal year, or quarterly if available).
"age", -- Ages of individuals hospitalized (21 to 64 years).
"gender", -- Gender of individuals hospitalized.
"geographic_area", -- Region measured, either total for Commonwealth or county.
":@computed_region_d3gw_znnf",
":@computed_region_rayf_jjgk",
":@computed_region_r6rf_p9et",
":@computed_region_amqz_jbr4",
":@computed_region_nmsq_hqvv"
FROM
"pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw:latest"."estimated_lost_wages_due_to_hospitalizations_for"
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 pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw 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 pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw: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 pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkwCheckout 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 pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw:latestThis will download all the objects for the latest tag of pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw 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 pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw: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 pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw: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, pa-gov/estimated-lost-wages-due-to-hospitalizations-for-w7cq-ufkw is just another Postgres schema.