cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi
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 affordable_housing_production_by_project table in this repository, by referencing it like:

"cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi:latest"."affordable_housing_production_by_project"

or in a full query, like:

SELECT
    ":id", -- Socrata column ID
    "planned_tax_benefit", -- The Planned Tax Benefit field indicates the type of tax benefit that is anticipated for the project at the time of the project start. Data on actual/final tax benefits received can only be obtained from the NYC Department of Finance. Note: Planned Tax Benefit data for confidential projects are masked.
    "prevailing_wage_status", -- The Prevailing Wage Status field indicates whether the project is subject to prevailing wage requirements, such as Davis Bacon.
    "extended_affordability_status", -- The Extended Affordability Only field indicates whether the project is considered to be Extended Affordability. An extended affordability project involves no construction, but secures an extended or new regulatory agreement. All extended affordability projects have a ‘reporting construction type’ of ‘preservation.’
    "all_counted_units", -- The Counted Units field indicates the total number of affordable units, counted towards the Housing New York plan, that are in the building.
    "other", -- Other Units are units reserved for building superintendents.
    "senior_units", -- Senior Units are units that are created or preserved for senior households. Senior Units are a subset of the Counted Units in a building, and are also included in the appropriate Extremely Low Income, Low Income, Moderate Income, Middle Income, or Other category.
    "project_name", -- The Project Name is the name assigned to the project by HPD.
    "counted_homeownership_units", -- Counted Homeownership Units are the units in the building, counted toward the Housing New York Plan, where assistance has been provided directly to homeowners.
    "counted_rental_units", -- Counted Rental Units are the units in the building, counted toward the Housing New York plan, where assistance has been provided to landlords in exchange for a requirement for affordable units.
    "middle_income", -- Middle Income Units are units with rents that are affordable to households earning 121 to 165% of the area median income (AMI).
    "moderate_income", -- Moderate Income Units are units with rents that are affordable to households earning 81 to 120% of the area median income (AMI).
    "low_income_units", -- Low Income Units are units with rents that are affordable to households earning 51 to 80% of the area median income (AMI).
    "project_start_date", -- The Project Start Date is the date of the project loan or agreement closing.
    "program_group",
    "very_low_income", -- Very Low Income Units are units with rents that are affordable to households earning 31 to 50% of the area median income (AMI).
    "extremely_low_income_units", -- Extremely Low Income Units are units with rents that are affordable to households earning 0 to 30% of the area median income (AMI).
    "project_completion_date", -- The Project Completion Date is the date that the last building in the project was completed. If the project has not yet completed, then the field is blank.
    "project_id", -- The Project ID is a unique numeric identifier assigned to each project by HPD.
    "total_units" -- The Total Units field indicates the total number of units, affordable and market rate, in each building.
FROM
    "cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi:latest"."affordable_housing_production_by_project"
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 cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi 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 cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi: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 cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi

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 cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi:latest

This will download all the objects for the latest tag of cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi 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 cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi: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 cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi: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, cityofnewyork-us/affordable-housing-production-by-project-hq68-rnsi is just another Postgres schema.

Related Documentation:

Loading...