pa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j
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 2024_primary_election_mail_ballot_requests table in this repository, by referencing it like:

"pa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j:latest"."2024_primary_election_mail_ballot_requests"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "ballot_status_reason", -- Reason for the status of the ballot. The following are optional values for this field: • CANC – EMAIL BALLOT UND BATCH • CANC – EMAIL BALLOT UNDELIVERABLE • CANC – INCORRECT DATE • CANC – LABEL CANCELLED • CANC – NO DATE • CANC – NO ID • CANC – NO SECRECY ENVELOPE • CANC – NO SIGNATURE • CANC – REPLACED • CANC – RETURNED AFTER DEADLINE • CANC – UNDELIVERABLE • CANC – VOTE CANCELLED • CANC – VOTE CHALLENGED • PEND – NOT YET RETURNED • RECORD – BALLOT RETURNED
    "disposition_reason", -- Reason for the Disposition of the Ballot Application.
    "longitude", -- A generic Longitude point within the county. A point is also provided for outside of the state (on a map it will sit to the southeast of the state). This number represents the total number for the state and this location provides a spot on a map to display the PA number without having it duplicate within a county when using in a mapping visual.
    "latitude", -- A generic Latitude point within the county. A point is also provided for outside of the state (on a map it will sit to the southeast of the state). This number represents the total number for the state and this location provides a spot on a map to display the PA number without having it duplicate within a county when using in a mapping visual.
    "congressional", -- This is the voter's congressional district.
    "senate", -- This is the voter's state senate district.
    "legislative", -- This is the voter's state house district.
    "appreturndate", -- This is the date the application was processed by the county election office.
    "mailapplicationtype", -- This identifies the type of mail ballot requested by the voter. Alt - This is an alternative ballot application where voters who are 65 years of age and the polling place may not be fully accessible. BV - Bedridden Veteran. BVRI - Bedridden Veteran - Remote/Isolated C- This is an absentee ballot application issued during the emergency absentee period. CIV- This is a civilian absentee ballot application that was submitted via paper. CRI- This is an absentee ballot application for an overseas civilian voter in a remote/isolated location. CVO- This is an absentee ballot application for an overseas civilian voter. F- This is an absentee application for an individual who qualifies to vote for federal offices in federal election years. OLMAILV-This is a mail ballot application that was submitted online. M-This is an absentee ballot application for a military voter. MAILIN-This is a mail-in ballot application. MRI-This is an absentee ballot application for a military voter in a remote/isolated location. OLREGV-This is a civilian absentee ballot application that was submitted online. PER-This is an absentee ballot application where a voter has requested permanent status. PMI- This is a mail ballot application where the voter has requested permanent status. REG-This is an absentee ballot application that was submitted via paper. OLMAILNV: Online Mail-In Ballot Application. Not Verified OLREGNV: Online Regular Absentee Ballot Application. V - Veteran. Not Verified BV: Bedridden Veteran (which is a form of Absentee Ballot Application)
    "countyname", -- This identifies the county of the voter when submitting an application to vote by mail ballot in the upcoming election.
    "ballotsentdate", -- This is the date the county confirmed the application to queue a ballot label to mail the ballot materials to the voter.
    "appissuedate", -- This is the date the application was submitted by the voter.
    "party", -- This identifies the voter's party when submitting their application.
    "ballotreturneddate", -- This is the date the county marked the ballot as received after the voter mailed the voted ballot back to the county.
    "ballot_status", -- Status of the ballot • Pending: Not yet returned • Received: Received by county elections office. • Cancelled: the county election authority cancelled the mail label.
    "id_verification_status", -- This field indicates whether voter’s ID has been verified or not.
    "dateofbirth", -- This is the voter's month and year of birth.
    "georeferenced_latitude_longitude", -- A georeferenced latitude and longitude based on the mailing address that can be used to create maps.
    "perm_indicator", -- True/False – indicates whether voter has requested to be on the permanent absentee list or permanent mail-in list. If a voter record has this flag as “True”, the voter is to be mailed an application for ballot at the beginning of the year and if they complete the application and if county board of elections approved the application, they receive ballots for all elections occurring in that year provided they maintain eligibility.
    "ballot_application_disposition", -- Disposition of the ballot application – Approved/Declined
    ":@computed_region_75dh_jrw3", -- This column was automatically created in order to record in what polygon from the dataset 'PA State Senate Districts 2016 Health' (75dh-jrw3) the point in column 'georeferenced_latitude_longitude' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_gbji_5m4q", -- This column was automatically created in order to record in what polygon from the dataset 'US House Districts for PA 2019 Health' (gbji-5m4q) the point in column 'georeferenced_latitude_longitude' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_4fjn_fq7k", -- This column was automatically created in order to record in what polygon from the dataset 'PA County Boundaries Spatial Data Current Transportation' (4fjn-fq7k) the point in column 'georeferenced_latitude_longitude' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_3x3q_vpda", -- This column was automatically created in order to record in what polygon from the dataset 'US House Districts for PA 2019' (3x3q-vpda) the point in column 'georeferenced_latitude_longitude' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
    ":@computed_region_its3_bt6a" -- This column was automatically created in order to record in what polygon from the dataset 'PA State House Districts 2016 Health' (its3-bt6a) the point in column 'georeferenced_latitude_longitude' is located.  This enables the creation of region maps (choropleths) in the visualization canvas and data lens.
FROM
    "pa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j:latest"."2024_primary_election_mail_ballot_requests"
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 pa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.pa.gov. When you querypa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j: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.pa.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 \
  "pa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j" \
  --handler-options '{
    "domain": "data.pa.gov",
    "tables": {
        "2024_primary_election_mail_ballot_requests": "8yp7-qf6j"
    }
}'

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, pa-gov/2024-primary-election-mail-ballot-requests-8yp7-qf6j is just another Postgres schema.