wa-gov/candidate-surplus-funds-latest-report-3cbn-54c3
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 candidate_surplus_funds_latest_report table in this repository, by referencing it like:

"wa-gov/candidate-surplus-funds-latest-report-3cbn-54c3:latest"."candidate_surplus_funds_latest_report"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "balance", -- This column shows the balance of surplus funds that a candidate reported on the last C4. This balance remains in the account until disposed of per RCW 42.17.
    "spent", -- This column is the cumulative total that has been spent out of the account from inception.
    "filer_name", -- The registered name of the surplus funds account.
    "person_id", -- The unique ID assigned to a public office holder or candidate. This id is consistent across years and, offices or candidacies and is the preferred id for identifying a natural person.
    "report_number", -- The unique number assigned to a report when it is filed. A 10 character number represents a paper filed report whose data was manually entered into the database. A 9 character number represents an electronically filed report.
    "id", -- PDC internal identifier that corresponds to a candidate's surplus funds account. A candidate has only one surplus account which is valid until terminated. There is not an election year associated with a surplus funds account, money is transferred in and spent out of the account until closed.
    "raised", -- This column is the cumulative total that has been transferred into the account from inception.
    "year", -- This column is provided to clarify in what year a report is filed. Since a surplus funds account can be active for multiple years, this column is created using the thru_date.
    "thru_date", -- A C4 report covers a specific period of time. This column is the end date of the report.
    "filer_id", -- The unique id assigned to a candidate's surplus account. The filer id remains the same throughout years.
    "from_date", -- A C4 report covers a specific period of time. This column is the start date of the report.
    "url", -- A link to a PDF version of the C4 summary report as it was filed with the PDC.
    "origin" -- This column designates what type of report the data was retrieved from.
FROM
    "wa-gov/candidate-surplus-funds-latest-report-3cbn-54c3:latest"."candidate_surplus_funds_latest_report"
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/candidate-surplus-funds-latest-report-3cbn-54c3 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/candidate-surplus-funds-latest-report-3cbn-54c3: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/candidate-surplus-funds-latest-report-3cbn-54c3" \
  --handler-options '{
    "domain": "data.wa.gov",
    "tables": {
        "candidate_surplus_funds_latest_report": "3cbn-54c3"
    }
}'

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/candidate-surplus-funds-latest-report-3cbn-54c3 is just another Postgres schema.