mydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd
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 iowa_township_fund_balances_by_fiscal_year table in this repository, by referencing it like:

"mydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd:latest"."iowa_township_fund_balances_by_fiscal_year"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "location", -- Location of the township in latitude and longitude.
    "end_bal_total", -- Estimated cash balance of all funds as of June 30 of the fiscal year.
    "beg_bal_total", -- Estimated cash balance of all funds as of July 1 of the fiscal year.
    "end_bal_other", -- Estimated cash balance of other/miscellaeous fund as of June 30 of the fiscal year.
    "beg_bal_other", -- Estimated cash balance of other/miscellaneous fund as of July 1 of the fiscal year.
    "beg_bal_fire_ems", -- Estimated cash balance of fire/EMS fund as of July 1 of the fiscal year.
    "end_bal_tort", -- Estimated cash balance of tort liability fund as of June 30 of the fiscal year.
    "end_bal_litigation", -- Estimated cash balance of litigation fund as of June 30 of the fiscal year.
    "beg_bal_litigation", -- Estimated cash balance of litigation fund as of July 1 of the fiscal year.
    "end_bal_twp_hall_repairs", -- Estimated cash balance of township hall repair fund as of June 30 of the fiscal year.
    "end_bal_twp_hall", -- Estimated cash balance of township hall fund as of June 30 of the fiscal year.
    "beg_bal_owned_cem", -- Estimated cash balance of owned cemetery fund as of July 1 of the fiscal year.
    "record_key", -- Tracking code of township data
    "end_bal_fire_ems", -- Estimated cash balance of fire/EMS fund as of June 30 of the fiscal year.
    "end_bal_non_owned_cem", -- Estimated cash balance of non-owned cemetery fund as of June 30 of the fiscal year.
    "fiscal_year", -- Fiscal year ending June 30
    "beg_bal_tort", -- Estimated cash balance of tort liability fund as of July 1 of the fiscal year.
    "end_bal_library", -- Estimated cash balance of library fund as of June 30 of the fiscal year.
    "beg_bal_library", -- Estimated cash balance of library fund as of July 1 of the fiscal year.
    "beg_bal_twp_hall", -- Estimated cash balance of township hall fund as of July 1 of the fiscal year.
    "beg_bal_non_owned_cem", -- Estimated cash balance of non-owned cemetery fund as of July 1 of the fiscal year.
    "end_bal_owned_cem", -- Estimated cash balance of owned cemetery fund as of June 30 of the fiscal year.
    "township_tax_district_name", -- Name of the township
    "unique_line_id", -- Identification code for the line of data.
    "beg_bal_twp_hall_repairs", -- Estimated cash balance of township hall repair fund as of July 1 of the fiscal year.
    "county_name" -- County in which the township is located
FROM
    "mydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd:latest"."iowa_township_fund_balances_by_fiscal_year"
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 mydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at mydata.iowa.gov. When you querymydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd: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 mydata.iowa.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 \
  "mydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd" \
  --handler-options '{
    "domain": "mydata.iowa.gov",
    "tables": {
        "iowa_township_fund_balances_by_fiscal_year": "etmy-ihfd"
    }
}'

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, mydata-iowa-gov/iowa-township-fund-balances-by-fiscal-year-etmy-ihfd is just another Postgres schema.