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 us_state_and_territorial_orders_closing_and table in this repository, by referencing it like:
"cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x:latest"."us_state_and_territorial_orders_closing_and"or in a full query, like:
SELECT
":id", -- Socrata column ID
"numeric_capacity_indoor", -- The maximum number of people permitted for on premise, indoor consumption number
"percent_capacity_outdoor", -- The maximum percent occupancy for on premise, outdoor consumption number
"citation", -- Citation for the order
"url", -- URL of order language used to complete dataset
"order_code", -- Numeric order status grouped by display categories used on the Environmental Public Health Tracking Network; corresponds to restrictiveness of the action
"business_type", -- Describes the type of businesses being impacted. Bars (including cigar bars/hookah lounge, taverns, brew pubs, breweries, microbreweries, distillery, pubs, wineries, tasting rooms, clubs, and other places of public accommodation offering alcoholic beverages for on-premises consumption). Note: when a state differentiates between bars that serve food and bars that do not, and treats bars that serve food in the same manner as restaurants, only bars that do not serve food are coded as bars and bars that do serve food will be captured as Restaurants; Restaurants: any establishment that traditionally provides for on-premises consumption of food and beverages, distinguished from bars (beverage only) and businesses that sell food for off-premises consumption (grocery stores, convenience stores, etc.).
"date", -- Daily date in dataset
"fips_county", -- U.S. county FIPS codes
"fips_state", -- U.S. state FIPS codes
"county_name", -- U.S. county names
"state_tribe_territory", -- U.S. state, tribe, and territory names
"limited_open_outdoor_only",
"source_of_action", -- Source where order was found
"action", -- Describes the closure action applied to the business described in Business_Type. NA: the jurisdiction has not closed businesses of this type; Closed: the jurisdiction has closed businesses of this type; Curbside/carryout/delivery only: businesses may only conduct curbside or delivery operations; Open with limitations – outdoor: the jurisdiction allows on-premise consumption but only outdoors; Open with limitations – indoor: The jurisdiction allows on-premise consumption indoors, but must follow safety limitations such as reduced capacity and social distancing; Authorized to fully reopen: businesses of this type may open fully with no new limitations for COVID-19.
"numeric_capacity_outdoor", -- The maximum number of people permitted for on premise, outdoor consumption number
"percent_capacity_indoor", -- The maximum percent occupancy for on premise, indoor consumption number
"limited_open_general_indoor"
FROM
"cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x:latest"."us_state_and_territorial_orders_closing_and"
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 cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x 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 cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x: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 cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939xCheckout 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 cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x:latestThis will download all the objects for the latest tag of cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x 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 cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x: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 cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x: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, cdc-gov/us-state-and-territorial-orders-closing-and-azmd-939x is just another Postgres schema.