austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud

  • actual
  • austin
  • austin finance online
  • budget
  • budget documents
  • + 11

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

"austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud:latest"."program_budget_operating_budget_vs_expense_raw"

or in a full query, like:

SELECT 
    ":id", -- Socrata column ID
    "unit_code",
    "activity_code", -- An activity is a sub-group under programs that further segregates the organization to track the City of Austin's functions and expenses.
    "fund_code", -- A fund is a high level chart of accounts structure. Funds help organize the City's finances. Some examples include the General Fund, Drainage Fund, and the Airport Operating Fund.
    "unit_name",
    "expense_code", -- The identification code associated with an object of expenditure.  Object is a fund accounting Chart of Accounts element.  It is used to describe types of expenses. An expense category describes the types of expenses. For example, Computer Software, Salaries, and Architectural Services. 
    "program_code", -- A program is the secondary organizational unit used by the City of Austin. Each department has one or more programs within it. For example, Parks and Recreation have Acquatics, Cultural Arts Services, Facilities Services, etc. A program can be an organizational entity within a department, or an administrative entity in which expenses can be captured and tracked.
    "department_name", -- A department is a primary organizational unit used by the City of Austin. Examples of various departments are Parks and Recreation and Austin Police Department.
    "thru_quarter", -- The Budget versus expense data set is populated with data thru the quarter defined in this column.  Fiscal Months 1 to 3 is Q1, 4-6 is Q2, 7-9 is Q3, and 10-12 is Q4.
    "dept_rollup", -- A department is a primary organizational unit used by the City of Austin. Examples of various departments are Parks and Recreation and Austin Police Department. 
    "dept_rollup_name", -- A department is a primary organizational unit used by the City of Austin. Examples of various departments are Parks and Recreation and Austin Police Department. 
    "department_code", -- A department is a primary organizational unit used by the City of Austin. Examples of various departments are Parks and Recreation and Austin Police Department. 
    "budget_fiscal_year",
    "program_name", -- A program is the secondary organizational unit used by the City of Austin. Each department has one or more programs within it. For example, Parks and Recreation have Acquatics, Cultural Arts Services, Facilities Services, etc. A program can be an organizational entity within a department, or an administrative entity in which expenses can be captured and tracked.
    "budget",
    "fund_name", -- A fund is a high level chart of accounts structure. Funds help organize the City's finances. Some examples include the General Fund, Drainage Fund, and the Airport Operating Fund.
    "expense_name", -- The identification name associated with an object of expenditure.  Object is a fund accounting Chart of Accounts element.  It is used to describe types of expenses. An expense category describes the types of expenses. For example, Computer Software, Salaries, and Architectural Services. 
    "activity_name", -- An activity is a sub-group under programs that further segregates the organization to track the City of Austin's functions and expenses.
    "key", -- Row Key Identifier
    "expenditures"
FROM
    "austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud:latest"."program_budget_operating_budget_vs_expense_raw"
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/program-budget-operating-budget-vs-expense-raw-g5k8-8sud 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/program-budget-operating-budget-vs-expense-raw-g5k8-8sud: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/program-budget-operating-budget-vs-expense-raw-g5k8-8sud" \
  --handler-options '{
    "domain": "data.austintexas.gov",
    "tables": {
        "program_budget_operating_budget_vs_expense_raw": "g5k8-8sud"
    }
}'

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/program-budget-operating-budget-vs-expense-raw-g5k8-8sud is just another Postgres schema.

Related Documentation: