cambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt
Icon for Socrata external plugin

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

"cambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt:latest"."epa_air_quality_data_pollutants"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "observation_percent", -- The percent representing the number of observations taken with respect to the number scheduled to be taken during the day.
    "arithmetic_mean", -- The average (arithmetic mean) value for the day.
    "first_max_hour", -- The hour (on a 24-hour clock) when the highest value for the day was taken.
    "aqi", -- The Air Quality Index for the day for the pollutant, if applicable.
    "method", -- A short description of the processes, equipment, and protocols used in gathering and measuring the sample.
    "pollutant_standard", -- A description of the ambient air quality standard rules used to aggregate statistics.
    "units_of_measure", -- The unit of measure for the parameter.
    "sample_duration", -- The length of time that air passes through the monitoring device before it is measured.
    "local_site_name", -- The name of the site (if any) given by the State, local, or tribal air pollution control agency that operates it.
    "event_type", -- Indicates whether data measured during exceptional events (such as a wildfire) are included in the summary.
    "observation_count", -- The number of observations (samples) taken during the day.
    "first_max_value", -- The highest value for the day.
    "parameter_code", -- The AQS (Air Quality System) code corresponding to the parameter (pollutant) measured by the monitor.
    "parameter", -- The name or description assigned in AQS to the parameter measured by the monitor.
    "date_local" -- The calendar date for the summary.
FROM
    "cambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt:latest"."epa_air_quality_data_pollutants"
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 cambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.cambridgema.gov. When you querycambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt:latest on the DDN, we "mount" the repository using the socrata mount handler. The mount handler proxies your SQL query to the upstream data source, translating it from SQL to the relevant language (in this case SoQL).

We also cache query responses on the DDN, but we run the DDN on multiple nodes so a CACHE_HIT is only guaranteed for subsequent queries that land on the same node.

Query Your Local Engine

Install Splitgraph Locally
bash -c "$(curl -sL https://github.com/splitgraph/splitgraph/releases/latest/download/install.sh)"
 

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 (like this repository), 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, where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.

Mounting Data

This repository is an external repository. It's not hosted by Splitgraph. It is hosted by data.cambridgema.gov, and Splitgraph indexes it. This means it is not an actual Splitgraph image, so you cannot use sgr clone to get the data. Instead, you can use the socrata adapter with the sgr mount command. Then, if you want, you can import the data and turn it into a Splitgraph image that others can clone.

First, install Splitgraph if you haven't already.

Mount the table with sgr mount

sgr mount socrata \
  "cambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt" \
  --handler-options '{
    "domain": "data.cambridgema.gov",
    "tables": {
        "epa_air_quality_data_pollutants": "43k6-pjtt"
    }
}'

That's it! Now you can query the data in the mounted table like any other Postgres table.

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, cambridgema-gov/epa-air-quality-data-pollutants-43k6-pjtt is just another Postgres schema.

Related Documentation: