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 taxes_by_county_and_industry_in_colorado table in this repository, by referencing it like:
"colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim:latest"."taxes_by_county_and_industry_in_colorado"or in a full query, like:
SELECT
":id", -- Socrata column ID
"retailtrades", -- The amount of retail traded (?)
"otherservices", -- The amount of retail sold in the Other Services industry
"professionaltechnical", -- The amount of retail sold in the Professional, Scientific, and Technical Services industry
"nonstore", -- The amount of retail sold in the Not Store industry
"genmerchandise", -- The amount of retail sold in the General Merchandise industry
"clothing", -- The amount of retail sold in the Clothing industry
"mvparts", -- The amount of retail sold in the ? industry
"wholesale", -- The amount of retail sold in the Wholesale Trade industry
"construction", -- The amount of retail sold in the Construction industry
"mining", -- The amount of retail sold in the Mining, Quarrying, and Oil and Gas Extraction industry
"fips", -- The county fips code, added after export from database using county name and lookup table
"transwrhse", -- The amount of retail sold in the Transportation and Warehousing industry
"education", -- The amount of retail sold in the Education industry
"gasstations", -- The amount of retail sold in the Gas Station industry
"foodbeverage", -- The amount of retail sold in the Food and Beverage industry
"miscstores", -- The amount of retail sold in the Miscellaneous Stores industry
"sportshobbies", -- The amount of retail sold in the Sports and Hobbies industry
"financialinsurance", -- The amount of retail sold in the Finance and Insurance industry
"healthcare", -- The amount of retail sold in the Health Care industry
"realestate", -- The amount of retail sold in the Real Estate, Rental, and Leasing industry
"information", -- The amount of retail sold in the Information industry
"health", -- The amount of retail sold in the Health Care and Social Assistance industry
"adsuppwstmngmremserv", -- The amount of retail sold in the Administrative and Support and Waste Management and Remediation Services industry
"foodservices", -- The amount of retail sold in the Food Services industry
"lodging", -- The amount of retail sold in the Accommodation industry
"artsentertainment", -- The amount of retail sold in the Arts, Entertainment, and Recreation industry
"allindustries", -- The amount of retail sold in all industries
"government", -- The amount of retail sold in the Public Administration industry
"year", -- The year that the data was gathered
"month", -- The month code that the data was gathered (eg 01 is January)
"agriculture", -- The amount of retail sold in the agriculture industry
"county", -- The name of the county (eg Jefferson)
"manufacturing", -- The amount of retail sold in the Manufacturing industry
"utilities", -- The amount of retail sold in the Utilities industry
"bldgnursery", -- The amount of retail sold in the Building and Nursery industry
"electappl", -- The amount of retail sold in the Electricity industry
"furniture" -- The amount of retail sold in the Furniture industry
FROM
"colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim:latest"."taxes_by_county_and_industry_in_colorado"
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 colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim 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 colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim: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 colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdimCheckout 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 colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim:latestThis will download all the objects for the latest tag of colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim 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 colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim: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 colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim: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, colorado-gov/taxes-by-county-and-industry-in-colorado-ax6t-kdim is just another Postgres schema.