Code Neighborhood Rezonings Phasing Assumptions

[levysamu]

Currently the phasing assumptions for units associated with a rezoning are manually edited. For a build year of 10 years, you might assume that 50% of the units will happen in the next 5 years and 50% will happen between 5 and 10 years out. But the next time the KPDB is assembled, 2 years will have passed and new values need to be assigned. In that case it might make sense to change these values from 50/50 to 62.5/37.5 for within 5 and 5 to 10 respectively.

This could be coded as long as the information for the year of the rezoning, the build year, and the current year were included in the file.

[td928]

one possible solution:

since very few records have phasing assumption in multiple phasings. We could potentially separate those records as their categories which then needs to be deduplicated.

for example explodes the Neighborhood Study Rezoning Commitments into three categories

    hierarchy = {
        "DOB": 1,
"Neighborhood Study Rezoning Commitments <5 years" : 1.1,
        "HPD Projected Closings": 2,
        "HPD RFPs": 3,
        "EDC Projected Projects": 4,
        "DCP Application": 5,
"Neighborhood Study Rezoning Commitments 5 to 10 ": 5.5
        "Empire State Development Projected Projects": 6,
        "Neighborhood Study Projected Development Sites": 8,
        "DCP Planner-Added Projects": 9,
"Neighborhood Study Rezoning Commitments 10+": 9.5
    }

issue with this approach though the records will likely be deduplciated against itself i.e. the units from within 5 years for rezoning commitments will get deducted from the 5to10 years units.

[github-actions[bot]]

Stale issue message