readingpa-gov/demolition-permits-bkbf-njzm
Loading...
  •  
    Overview
  •  
    Tables
  • Loading...
  •  
    REST API
  • Loading...
  •  
    SQL Query

Query the Data Delivery Network

Query the DDN

The 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 demolition_permits table in this repository, by referencing it like:

"readingpa-gov/demolition-permits-bkbf-njzm:latest"."demolition_permits"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "zip", -- Contractor zip. 
    "statby", -- ID of the employee that changed the status. 
    "laststgdesc", -- The description of the last stage. 
    "comments", -- Description of work. 
    "laststg", -- The last stage the permit has completed for processing. 
    "addr1", -- Contractor address 1. 
    "deptcm", -- Department of Commerce code. 
    "apby", -- ID of the employee that added the permit. 
    "addr2", -- Contractor address 2. 
    "issby", -- ID of the employee that issued the permit. 
    "pri", -- Priority code. 
    "city", -- Contractor city. 
    "statdttm", -- Date/time of the status change. 
    "stat", -- The status of the permit. 
    "planrev", -- Y/N if plan reviews should be automatically added on stage progression. 
    "lstactdttm", -- The date/time of the last action that was done to the permit. 
    "state", -- Contractor state. 
    "worktypedesc", -- Description of the work type code. 
    "pridesc", -- Description of the priority code. 
    "nextstgdesc", -- The next stage of the permit's process. 
    "expdttm", -- Permit expiration date/time. 
    "declvltn", -- Declared value of the proposed demolition. 
    "apdttm", -- Permit date/time. 
    "apname", -- Name on the permit. 
    "worktype", -- Code for the type of work for the permit. 
    "contractor", -- Name of the contractor performing the work. 
    "permit", -- Permit number. 
    "commercedesc", -- Description of the commerce code. 
    "issdttm", -- Permit issued date/time. 
    "primaplid", -- ID of the primary applicant for the permit. 
    "address" -- Address where the work is to be performed. 
FROM
    "readingpa-gov/demolition-permits-bkbf-njzm:latest"."demolition_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 readingpa-gov/demolition-permits-bkbf-njzm with SQL in under 60 seconds.

Query Your Local Engine

Install Splitgraph Locally
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 readingpa-gov/demolition-permits-bkbf-njzm: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 readingpa-gov/demolition-permits-bkbf-njzm

Checkout 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 readingpa-gov/demolition-permits-bkbf-njzm:latest

This will download all the objects for the latest tag of readingpa-gov/demolition-permits-bkbf-njzm 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 readingpa-gov/demolition-permits-bkbf-njzm: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 readingpa-gov/demolition-permits-bkbf-njzm:latest

This 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, readingpa-gov/demolition-permits-bkbf-njzm is just another Postgres schema.

Related Documentation:

Loading...