Query the Data Delivery Network
Query the DDNThe 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 program_budget_operating_budget_vs_expense_raw table in this repository, by referencing it like:
"datahub-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_name",
"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.
"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.
"budget",
"expenditures",
"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.
"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.
"budget_fiscal_year",
"key", -- Row Key Identifier
"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_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.
"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.
"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.
"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.
"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.
"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.
"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.
"unit_code",
"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.
FROM
"datahub-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 datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud with SQL in under 60 seconds.
Query Your Local Engine
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, 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 (like this repository), where the author has pushed Splitgraph Images to the repository, you can "clone" and/or "checkout" the data using sgr cloneand sgr checkout.
Cloning Data
Because datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud:latest is a Splitgraph Image, you can clone the data from Spltgraph Cloud to your local engine, where you can query it like any other Postgres database, using any of your existing tools.
First, install Splitgraph if you haven't already.
Clone the metadata with sgr clone
This will be quick, and does not download the actual data.
sgr clone datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sudCheckout the data
Once you've cloned the data, you need to "checkout" the tag that you want. For example, to checkout the latest tag:
sgr checkout datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud:latestThis will download all the objects for the latest tag of datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud and load them into the Splitgraph Engine. Depending on your connection speed and the size of the data, you will need to wait for the checkout to complete. Once it's complete, you will be able to query the data like you would any other Postgres database.
Alternatively, use "layered checkout" to avoid downloading all the data
The data in datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud:latest is 0 bytes. If this is too big to download all at once, or perhaps you only need to query a subset of it, you can use a layered checkout.:
sgr checkout --layered datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud:latestThis will not download all the data, but it will create a schema comprised of foreign tables, that you can query as you would any other data. Splitgraph will lazily download the required objects as you query the data. In some cases, this might be faster or more efficient than a regular checkout.
Read the layered querying documentation to learn about when and why you might want to use layered queries.
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, datahub-austintexas-gov/program-budget-operating-budget-vs-expense-raw-g5k8-8sud is just another Postgres schema.