austintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj

  • campaign finance
  • city clerk
  • credits
  • election
  • financial

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

"austintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj:latest"."campaign_finance_credits_dataset"

or in a full query, like:

SELECT 
    ":id", -- Socrata column ID
    "credit_year", -- The date on which the credit/gain/refund was received or the interest was earned.
    "payer", -- The full name of the person of business from whom the credit/gain/refund/returned contribution or interest was received.
    "payer_address", -- Address of individual or entity from whom the credit/gain/refund/returned contribution or interest was received.  
    "report_filed", -- The type of report on which the filer reported the credit/gain/refund/returned contribution, or interested.
    "out_of_state_pac", -- If the column is checked X, the incoming credit/gain was received by an out of state PAC.
    "transaction_type", -- The type of transaction that occurred.  This column will always be populated by ‘Interest, Credits, Gains, Refunds, and Contributions Returned to Filer.’
    "correction", -- If the column has New or Modify, the credit/gain/refund/returned contribution, or interested was filed as a correction to another report. 
    "date_reported", -- Date the structured data file was received by the Office of the City Clerk.
    "recipient", -- Name of the candidate or office holder that is filing the report. This name is a standardized format used by the Office of the City Clerk to ensure all of a filer's reports are accessible under a single name.
    "credit_date", -- The date on which the credit/gain/refund was received or the interest was earned.
    "credit_amount", -- The exact dollar amount of the credit/gain/refund/returned contribution, or interest.
    "payer_city_state_zip", -- City, state, and zip code of individual or entity from whom the credit/gain/refund/returned contribution or interest was received.
    "transaction_id", -- Unique ID based upon the concatenation of the Report_ID and Transaction_ID field - acts as a unique key for each individual transaction.
    "in_kind_description", -- A description of the credit/gain/refund/returned contribution, or interested.
    "payer_type", -- Identifies the payer as either an entity (such as a company, political committee, organization, or other group) or an individual person.
    "view_report", -- A link to the PDF report on which the filer reported the credit/gain/refund/returned contribution, or interested.
    "political_contribution_return" -- If the column is checked X, the incoming credit/gain was originally made by the filer in the form of a political contribution. 
FROM
    "austintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj:latest"."campaign_finance_credits_dataset"
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 austintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj with SQL in under 60 seconds.

This repository is an "external" repository. That means it's hosted elsewhere, in this case at data.austintexas.gov. When you queryaustintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj: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.austintexas.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 \
  "austintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj" \
  --handler-options '{
    "domain": "data.austintexas.gov",
    "tables": {
        "campaign_finance_credits_dataset": "xhtw-mkpj"
    }
}'

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, austintexas-gov/campaign-finance-credits-dataset-xhtw-mkpj is just another Postgres schema.

Related Documentation: