cityofchicago/budget-survey-2020-drbg-ny73
Loading...

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

"cityofchicago/budget-survey-2020-drbg-ny73:latest"."budget_survey_2020"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "revenue_change_shopping_bag_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "revenue_change_property_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "expense_interest_libraries", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_sales_tax", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_permit_fees", -- Whether the respondent reported interest in information on this topic.
    "spending_change_infrastructure", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "spending_change_regulatory", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "zip_code", -- The respondent's reported home ZIP Code.
    "revenue_interest_ridesharing_tax", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_tax_on_sports_theater_other_entertainment", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_cigarette_tax", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_hotel_tax", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_shopping_bag_tax", -- Whether the respondent reported interest in information on this topic.
    "expense_interest_police", -- Whether the respondent reported interest in information on this topic.
    "spending_change_other_public_safety", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "spending_change_community", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "spending_change_city_development", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "spending_change_libraries", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "revenue_change_garage_parking_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "revenue_change_sales_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "revenue_change_permit_fees", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "_1000_assignment_total", -- Total of the previous columns, after accounting for the adjustments.
    "counter_column", -- This is an additional column, set to 1 for all records, to allow for certain types of charts and aggregations.
    "spending_change_streets_and_sanitation", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "revenue_change_ridesharing_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "revenue_change_tax_on_sports_theater_other_entertainment", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "revenue_interest_license_fees", -- Whether the respondent reported interest in information on this topic.
    "revenue_change_hotel_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "expense_interest_infrastructure", -- Whether the respondent reported interest in information on this topic.
    "expense_interest_regulatory", -- Whether the respondent reported interest in information on this topic.
    "spending_change_cultural_affairs_and_special_events", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "expense_interest_cultural_affairs_and_special_events", -- Whether the respondent reported interest in information on this topic.
    "_1000_assignment_community", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "expense_interest_city_development", -- Whether the respondent reported interest in information on this topic.
    "date", -- The date on which the respondent completed the survey.
    "expense_interest_community", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_other", -- Whether the respondent reported interest in information on this topic.
    "revenue_change_alcohol_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "_1000_assignment_libraries", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_city_development", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_police", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_other_public_safety", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_infrastructure_services", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_streets_and_sanitation", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_regulatory", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "_1000_assignment_cultural_affairs_and_special_events", -- Amount of a hypothetical $1000 allocated to this area. Negative values have been converted to blanks. Totals above $1000 have been adjusted proportionally to reduce the total to $1000.
    "revenue_interest_alcohol_tax", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_garage_parking_tax", -- Whether the respondent reported interest in information on this topic.
    "revenue_interest_property_tax", -- Whether the respondent reported interest in information on this topic.
    "expense_interest_streets_and_sanitation", -- Whether the respondent reported interest in information on this topic.
    "expense_interest_other", -- Whether the respondent reported interest in information on this topic.
    "spending_change_police", -- Answer for this area to the question: "Which areas of spending would you consider reducing, increasing or remaining the same in order to balance the City’s budget? "
    "revenue_change_cigarette_tax", -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
    "expense_interest_other_public_safety", -- Whether the respondent reported interest in information on this topic.
    "revenue_change_license_fees" -- Answer for this potential revenue source to the question: "Which revenues would you consider increasing or keeping the same in order to balance the City’s budget? "
FROM
    "cityofchicago/budget-survey-2020-drbg-ny73:latest"."budget_survey_2020"
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 cityofchicago/budget-survey-2020-drbg-ny73 with SQL in under 60 seconds.

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, 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 cityofchicago/budget-survey-2020-drbg-ny73: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 cityofchicago/budget-survey-2020-drbg-ny73

Checkout 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 cityofchicago/budget-survey-2020-drbg-ny73:latest

This will download all the objects for the latest tag of cityofchicago/budget-survey-2020-drbg-ny73 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 cityofchicago/budget-survey-2020-drbg-ny73: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 cityofchicago/budget-survey-2020-drbg-ny73:latest

This 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, cityofchicago/budget-survey-2020-drbg-ny73 is just another Postgres schema.

Related Documentation:

Loading...