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 highway_curves_in_colorado table in this repository, by referencing it like:
"colorado-gov/highway-curves-in-colorado-an2q-gwrx:latest"."highway_curves_in_colorado"or in a full query, like:
SELECT
":id", -- Socrata column ID
"seccurveclass", -- The curve class is calculated from the seccurve values using the following class breaks: A: >= 1660 (the value of -1 is also considered class A), B: >= 1053 AND < 1660, C: >= 676 AND < 1053, D: >= 413 AND < 676, E: >= 200 AND < 413, F: < 200
"pricurveclass", -- The curve class is calculated from the pricurve values using the following class breaks: A: >= 1660 (the value of -1 is also considered class A), B: >= 1053 AND < 1660, C: >= 676 AND < 1053, D: >= 413 AND < 676, E: >= 200 AND < 413, F: < 200
"pricurve", -- This value is the actual distance along the route, similarly known as the arc length of the curve. Each GPS point distance, between the start and end point, is added together to get the total distance in feet. Values that are negative represent left-hand turns. Values that are -1 are considered to be straight lines between two curves, otherwise known as the tangent. In the primary direction.
"curve_updateyr", -- date of curve data collection
"seg_length", -- segment length in miles
"endrefpt", -- end reference point (related to mileposts)
"objectid", -- Esri auto generated unique identifier
"runlength_to", -- end measure
"runlength_from", -- begin measure
"refpt", -- begin reference point (related to mileposts)
"route", -- CDOT route identifier
"seccurve" -- This value is the actual distance along the route, similarly known as the arc length of the curve. Each GPS point distance, between the start and end point, is added together to get the total distance in feet. Values that are negative represent left-hand turns. Values that are -1 are considered to be straight lines between two curves, otherwise known as the tangent. In the secondary direction.
FROM
"colorado-gov/highway-curves-in-colorado-an2q-gwrx:latest"."highway_curves_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/highway-curves-in-colorado-an2q-gwrx 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/highway-curves-in-colorado-an2q-gwrx: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/highway-curves-in-colorado-an2q-gwrxCheckout 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/highway-curves-in-colorado-an2q-gwrx:latestThis will download all the objects for the latest tag of colorado-gov/highway-curves-in-colorado-an2q-gwrx 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/highway-curves-in-colorado-an2q-gwrx: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/highway-curves-in-colorado-an2q-gwrx: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/highway-curves-in-colorado-an2q-gwrx is just another Postgres schema.