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


or in a full query, like:

    ":id", -- Socrata column ID
    "battery_cell_manufacturer", -- The manufacturer of the battery cells. For thermal or other forms of energy storage, the manufacturer of the hardware. Blank cells represent data that were not required or are not currently available
    "energy_storage_power_capacity", -- Rating of the electric power that can be delivered from an energy storage project in alternating current (AC) power 
    "installed_energy_storage", -- Usable installed energy storage capacity measured in alternating current (AC) power. It is equal to the total capacity measured during a complete discharge from a 100% usable state of charge, performed in accordance with the storage manufacturer’s specifications, on the commercial operation date
    "date_completed", -- Date NYSERDA recognized the project as interconnected and operational, and closed out the project application. Blank cells represent pipeline data for projects not yet completed
    "zip_code", -- ZIP code for project location. Blank cells represent data that were not required or are not currently available
    "county", -- Name of county for project location
    "city", -- Name of city for project location
    "address", -- Name of street for project location. Blank cells represent data that were not required or are not currently available
    "project_name", -- Description of project
    "metering_method", -- How the energy storage system was interconnected; either Community DG, Remote net metering, Bulk, or On-site metering. On-site metering is with customer load, and Community DG, Remote net metering, and Bulk are not. Bulk projects provide wholesale market services
    "nyserda_funding_amount", -- Amount of project incentives approved or paid by NYSERDA in USD
    "contractor", -- Name of entity responsible for installation of the project
    "project_status", -- Either Completed or Approved. Complete indicates projects that are interconnected and operational, and closed out the project application.  Approved indicates projects in the pipeline with an active application that are not yet completed. Pipeline projects are subject to change
    "date_project_approved", -- Date project application was approved by the program. Dates before April 2019 reflect the original approval date for already approved NY-Sun projects that subsequently added energy storage during or after April 2019
    "nyiso_zone", -- Name of New York Independent System Operator load zone for project location
    "electric_utility", -- Name of electric utility service provider for project location
    "application_number", -- Unique identifier for project
    "paired_with_solar", -- Indicates whether the energy storage system is interconnected with and charged by a paired solar electric PV system; either Yes or No
    "program_type", -- Name of program type; either Retail or Bulk
    "state", -- New York State 
    "reporting_period", -- The time period covered by the data set
    "storage_technology_type" -- Defines the type of energy storage system. For battery storage projects, the battery chemistry type is shown
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 ny-gov/retail-and-bulk-energy-storage-incentive-programs-ugya-enpy with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.ny.gov. When you queryny-gov/retail-and-bulk-energy-storage-incentive-programs-ugya-enpy: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.ny.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 \
  "ny-gov/retail-and-bulk-energy-storage-incentive-programs-ugya-enpy" \
  --handler-options '{
    "domain": "data.ny.gov",
    "tables": {
        "retail_and_bulk_energy_storage_incentive_programs": "ugya-enpy"

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, ny-gov/retail-and-bulk-energy-storage-incentive-programs-ugya-enpy is just another Postgres schema.

Related Documentation: