NYCPlanning / NYCPlanning/data-engineering

create LIFT data product

Open
#2,549 2 comments 0 reactions 1 assignee View on GitHub

@alexrichey is already working on this.

Since Aug 7, 2026.

db-lift
Dominant language
Python
Stars
43
Forks
3
Avg merge
23h 3m
Merged PRs (30d)
44

Description

We're adding columns to DCAS's LIFT table:

  • DRI Tier
  • Capital Projects Total Project count
  • Capital Projects Total Spent
  • 2020 Census Tract
  • NTA

This data is related to the Land Inventory Fast Track (LIFT) task force (storymap). it's a list of the "invetory" of city-controlled land that is suitable for housingm development

DCAS's LIFT table has 106 columns and ~15K rows. each row seems to be a lot

we'd love to build the pipeline to produce the entire LIFT table, but for now we're just adding fields to the latest manually created table

data model

inputs

  • DCAS LIFT
  • MapPLUTO
  • EDDE DRI
  • 2020 Census Tracts to 2020 NTAs and CDTAs Equivalency
  • CPDB

outputs

  • DCP LIFT

notes

LIFT_DCAS_Data Fields_20260807 is the last excel file we got from DCAS and is called the "updated DCAS LIFT table". it has 106 columns

LIFT Master Fields Other Data Sources 20260622 is a list of fields suggested by LIFT agencies earlier this year

since CPDB is a snapshot of the budget, should be clear that any capital project data is related to projects in the latest budget not all-time data

EDDE DRI data is NTA-level and PLUTO doesn't have an NTA column. we need to relate DRIs to tracts to lots

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.