datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95
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 communitytreeprioritymap table in this repository, by referencing it like:

"datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95:latest"."communitytreeprioritymap"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "shape_area", -- Feature area.
    "health_score", -- Cumulative score for the health category.
    "investment_score", -- Cumulative score for the investment category.
    "environment_score", -- Cumulative score for the environment category.
    "percent_canopy_2014", -- % of land area covered in tree canopy (2014).
    "ae_service_area", -- Determines if the priority area is in the Austin Energy service area (i.e. NeighborWoods service area).
    "zipcodes", -- Zip codes covering the priority area (i.e. Census tract).
    "tract_full_name", -- Census tract full name.
    "geoid10", -- Census tract unique ID.
    "priority_level_detailed", -- Priority level determined by the priority score. Detailed view provides 5 class breaks.
    "priority_score", -- Cumulative score of all 4 categories.
    "social_score", -- Cumulative score for the social category.
    "shape_length", -- Feature length.
    "tract_sqmi", -- Census tract land area in square miles.
    "the_geometry", -- Feature geometry.
    "austin_city_limits", -- Determines if the priority area is in the City of Austin's jurisdiction.
    "percent_canopy_2018", -- % of land area covered in tree canopy (2018).
    "priority_level_simple" -- Priority level determined by the priority score. Simple view provides 2 class breaks for reporting.
FROM
    "datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95:latest"."communitytreeprioritymap"
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 datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95 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 datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95: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 datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95

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 datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95:latest

This will download all the objects for the latest tag of datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95 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 datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95: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 datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95: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, datahub-austintexas-gov/communitytreeprioritymap-ugty-5b95 is just another Postgres schema.

Related Documentation:

Loading...