Pluto 25v4

[sf-dcp]

Main tasks

• source data extracted
• draft build succeeded
• draft build passed QA
• data packaged and distributed (including DOF sftp)
• shared QA reports with AD

Data loading

Manual Updates

Updated 2x a year typically in June and December

• dcp_colp (check here)

Automated Updates

Open data automated pull

Check here to see the latest run

• dsny_frequencies
• dpr_greenthumb
• lpc_historic_districts
• lpc_landmarks

DOF Automated Pull and Number of Buildings

• pluto_pts (Check here)
• pluto_input_geocodes (Check here)
• pluto_input_cama_dof (Check here)
• pluto_input_numbldgs (Check here)

Updated with Quarterly updates (check here)

• dcp_cdboundaries_wi
• dcp_ct2010
• dcp_cb2010
• dcp_ct2020
• dcp_cb2020
• dcp_school_districts
• dcp_councildistricts_wi
• dcp_firecompanies
• dcp_policeprecincts
• dcp_healthareas
• dcp_healthcenters

Updated with Zoning Taxlots

(check here for latest run).

These are all produced by GIS, who typically update them sometime in the first week of each month.
Check in with them before archiving with data library

• dof_dtm
• dof_shoreline
• dof_condo
• dcp_commercialoverlay
• dcp_limitedheight
• dcp_zoningdistricts
• dcp_specialpurpose
• dcp_specialpurposesubdistricts
• dcp_zoningmapamendments
• dcp_edesignation

Never Updated (Safe to ignore)

• doitt_zipcodeboundaries (almost never updated, check here)
• fema_firms2007_100yr
• fema_pfirms2015_100yr
• dcp_zoningmapindex

QA Checklist

1. Data Extraction

TODO: This should become a data check

• Ensure zoning data matches the build month
• Confirm Geosupport version aligns with PLUTO version (e.g., 25a for 24Q1)

2. Data Quality Review

We resolve all data quality issues before promoting PLUTO to drafts. These may come from:

• Sub-issues (GitHub or email)
• Failed dbt tests during build
• PLUTO QAQC page

Actions:

• Investigate stakeholder issues

  • Check if the field in question has ever been corrected (via pluto_input_research.csv)
  • If no past corrections for this field: notify the data provider (e.g., DOF) and inform the requester that DCP doesn't correct this field
  • If yes, add a manual correction

• Investigate failed dbt checks

  • Refer to data check descriptions in the repo
  • Manually correct records or add to an ignore seed file to pass check

• Investigate QAQC page (e.g., unreasonably small apartments)

  • Use provided guidance on the QAQC page to review and correct records as needed.

3. After publishing PLUTO

Send the following to AD:

• pts_condo_units_{{version}}.csv: all BBLs with active resunits corrections in PLUTO
• devdb_condo_units_{{version}}.csv: same BBLs joined to devdb for unit count comparison
• Zip and send via email with a PTS data version noted
• AD will forward these reports to DOF for them to review and address

[damonmcc]

Geosupport 25D scheduled for Nov 16th

[alexrichey]

WIP!

BBL Unit Count Research

There 12 cases that we haven't seen before.

BBL	What's Up
1000697502
1003157501
1010507501
1021887501
1022037501	existing in prev corrections
3006737502
3008857503
3011297503
3015357503
3041547501
3053927501	existing in prev corrections
3064717502

[alexrichey]

Research (In Progress)

90 JOHN STREET (1000697502)

DevDB indicates there should be ~330 units. DOF sources say 225, but it doesn't seem like construction has completed.

222 EAST BROADWAY (1003157501)

It seems like PTS is wrong here (and thus so is pluto_rpad_geo)

The first unit BBL in this condo shouldn't have 60 coop_apts (which appears to be just a general unit count, not coops, fyi)

Seems like the ballpark we're looking for here is between 60-70, per NY Yimby

billingbbl: 1003157501
basebbl: 1003150045
two towers, with a single entry in the DTM for 1003150045

DTM has questionable numfloors: should probably be 28, per this

"Soaring 28 stories, the airy tower residences feature signature floor-to-ceiling"

(There are two towers, and the value we have is for the shorter building)