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 city_of_memphis_parks_spatial_data table in this repository, by referencing it like:
"memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq:latest"."city_of_memphis_parks_spatial_data"or in a full query, like:
SELECT
":id", -- Socrata column ID
"inside_y", -- Variable used for mapping in GIS
"zipcode", -- Zip code that park is located in
"park_owner", -- Park owner (City) - from ParkServe
"concession", -- Whether park has concession stand (food/beverage)
"gistrkrid", -- ID used for mapping
"off_street", -- Whether off-street parking is available at the park
"play_groun", -- Whether park has playground
"pools", -- Whether park has swimming pool - If yes, indoor or outdoor
"benches", -- Whether park has bench(es)
"facilities", -- General description of park facilities
"walking_tr", -- Whether park has walking trail
"play_equip", -- Whether park has play equipment
"point", -- Point coordinates, used for mapping parks in GIS
"picnic_tab", -- Whether park has picnic tables
"tennis_cou", -- Whether park has tennis court
"shape_star", -- Geographic variable used for mapping parks in GIS
"park_manag", -- Park manager (City) - from ParkServe
"shape_stle", -- Geographic variable used for mapping parks in GIS
"park_nam_1", -- Park Name
":@computed_region_gxae_hf64",
":@computed_region_xf2b_u4zq",
":@computed_region_me95_vbw4",
"ballfield", -- Whether park has ballfield
"trash", -- Whether park has trash facilities
"basketball", -- Whether park has basketball court
"census_tra", -- 2010 US Census tract that park is located in
"pavilions", -- Whether park has pavilion
"shape_st_2", -- Geographic variable used for mapping parks in GIS
"council_di", -- Council district park is located in
"fountains", -- Whether park has fountain
"shape_st_1", -- Geographic variable used for mapping parks in GIS
"additional", -- Any additional assets at each park
"location", -- Park address
"parkid", -- Unique park ID for ParkServe(R), a national project focused on parks and the 10-minute walk area around them. Learn more at https://www.tpl.org/parkserve
"park_local", -- Park local owner/operator (City of Memphis) - from ParkServe
"acres_park", -- Park area in acres
"grilles", -- Whether park has grills for cooking/grilling
"restrooms", -- Whether park has restrooms
"inside_x" -- Variable used for mapping in GIS
FROM
"memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq:latest"."city_of_memphis_parks_spatial_data"
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 memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq 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 memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq: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 memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkqCheckout 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 memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq:latestThis will download all the objects for the latest tag of memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq 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 memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq: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 memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq: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, memphistn-gov/city-of-memphis-parks-spatial-data-aeu5-vwkq is just another Postgres schema.