wa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3
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 2015_greenhouse_gas_report_data table in this repository, by referencing it like:

"wa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3:latest"."2015_greenhouse_gas_report_data"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "total_emissions_mt_co2e", -- Total reported emissions in metric tons of carbon dioxide equivalents. Sum of all other emissions numbers.
    "source", -- Name of reporters reporting emissions.
    "point_size_based_on_total_emissions", -- Used to determine the size of the dot on the map. Based on total emissions. Not available for unmapped reporters.
    "nitrous_oxide_mt_co2e", -- Total reported nitrous oxide emissions in metric tons of carbon dioxide equivalents.
    "county", -- County of reporter, if applicable. Reporters without a specific location may not have this field.
    "location_latitude_longitude_city",
    "location_latitude_longitude_state",
    "location_latitude_longitude_address",
    "energy_intensive_trade_exposed", -- Status as an Energy-Intensive, Trade-Exposed industry in Washington.
    "sub_sector", -- Secondary activity classification of the reporter.
    "sector", -- Main activity classification of the reporter.
    "location_latitude_longitude", -- GPS coordinates of reporter, if applicable. Reporters without a specific location may not have this field.
    "sulfur_hexafluoride_mt_co2e", -- Total reported sulfur hexafluoride emissions converted to metric tons of carbon dioxide equivalents.
    "perfluorocarbons_mt_co2e", -- Total reported perfluorocarbons emissions converted to metric tons of carbon dioxide equivalents. This includes several GHGs: https://en.wikipedia.org/wiki/Fluorocarbon
    "hydrofluorocarbons_mt_co2e", -- Total reported hydrofluorocarbon emissions converted to metric tons of carbon dioxide equivalents. This includes several GHGs: https://en.wikipedia.org/wiki/Hydrofluorocarbon
    "biogenic_co2_mt_co2", -- Total reported biogenic carbon dioxide emissions in metric tons of carbon dioxide equivalents. Examples: wood, biodiesel, or biogas combustion.
    "address", -- Address of reporter, if applicable. Reporters without a specific location may not have this field.
    ":@computed_region_fny7_vc3j", -- This column was automatically created in order to record in what polygon from the dataset 'WAOFM - GIS - Congressional District Boundary' (fny7-vc3j) the point in column 'location_latitude_longitude' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_x4ys_rtnd", -- This column was automatically created in order to record in what polygon from the dataset 'Counties' (x4ys-rtnd) the point in column 'location_latitude_longitude' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_8ddd_yn5v", -- This column was automatically created in order to record in what polygon from the dataset 'WAOFM - GIS - Legislative District Boundary' (8ddd-yn5v) the point in column 'location_latitude_longitude' is located. This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    "location_latitude_longitude_zip",
    "methane_mt_co2e", -- Total reported methane emissions converted to  metric tons of carbon dioxide equivalents.
    "fossil_co2_mt_co2", -- Total reported carbon dioxide emissions in metric tons of carbon dioxide equivalents due to fossil fuel combustion.
    "clean_air_rule", -- Projected participation under Washington’s Clean Air Rule.
    "other_mt_co2e" -- Total reported emissions of GHGs not included in another category, converted to metric tons of carbon dioxide equivalents.
FROM
    "wa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3:latest"."2015_greenhouse_gas_report_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 wa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3 with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.wa.gov. When you querywa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3: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)"
 

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 (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.wa.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 \
  "wa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3" \
  --handler-options '{
    "domain": "data.wa.gov",
    "tables": {
        "2015_greenhouse_gas_report_data": "jvx2-m4u3"
    }
}'

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, wa-gov/2015-greenhouse-gas-report-data-jvx2-m4u3 is just another Postgres schema.