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 public_right_of_way_permits table in this repository, by referencing it like:
"montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk:latest"."public_right_of_way_permits"or in a full query, like:
SELECT
":id", -- Socrata column ID
"wssc", -- Project/plan number provided by the utility/agency on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"wgl", -- Project/plan number provided by the utility/agency on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"bus_shelter", -- Project/plan number provided by the utility/agency that constructed bus shelters within the County on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"allegheny", -- Project/plan number provided by the utility/agency on the DPS Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"city", -- City of work location.
"stno", -- Street number of work location
"finaleddate", -- The final date indicates the date that construction has been completed and approved by DPS. The final inspection was conducted that date/time by the DPS inspector and was acceptable.
"addeddate", -- The date that the applicant applied for the permit and the information entered into the database.
"usecode", -- Type of structure work will be performed on.
"worktype", -- Type of work to be performed.
"pepco", -- Project/plan number provided by the utility/agency on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"comcast", -- Project/plan number provided by the utility/agency on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"bge", -- Project/plan number provided by the utility/agency on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"zip", -- Zip Code of work location.
"permitno", -- Number assigned to uniquely identify permit.
"location_address",
"verizon", -- Project/plan number provided by the utility/agency on the Public Right-of-Way application for use in correlating the DPS permit to their project/plan.
"status", -- Status of permit.
"stname", -- Street name of work location.
"issueddate", -- The date that the permit is issued. When the permit is issued, construction is allowed to commence. DPS has reviewed the construction plans according to the applicable building and life safety codes and approved the plans.
"location_zip",
"location_city",
"descoflocation", -- Description of the location of work being performed. Typically used when the activity is not at a discrete property address.
"location_state",
"description", -- Description of planned work
"location",
"applicationtype", -- Type of permit application
"predir", -- Pre-direction, if the street name has a direction as a prefix. For example, E Jefferson Street.
"suffix", -- Street suffix, such as ST (Street), PL (Place), RD (Road).
"state", -- State of work location.
"postdir", -- Post-direction, if the street name has a direction after the name. For example, University Blvd W.
":@computed_region_6vgr_duib", -- This column was automatically created in order to record in what polygon from the dataset 'Council Districts 7' (6vgr-duib) the point in column 'location' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
":@computed_region_a9cs_3ed7",
":@computed_region_vu5j_pcmz",
":@computed_region_d7bw_bq6x",
":@computed_region_rbt8_3x7n",
":@computed_region_tx5f_5em3",
":@computed_region_kbsp_ykn9"
FROM
"montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk:latest"."public_right_of_way_permits"
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 montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk 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 montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk: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 montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxkCheckout 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 montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk:latestThis will download all the objects for the latest tag of montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk 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 montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk: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 montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk: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, montgomerycountymd-gov/public-right-of-way-permits-2b9e-mbxk is just another Postgres schema.