NYCPlanning / db-pluto

🔭 PLUTO and MapPLUTO
https://nycplanning.github.io/db-pluto
39 stars 13 forks source link

2020 Census changes #246

Open AmandaDoyle opened 3 years ago

AmandaDoyle commented 3 years ago

Changes that will need to happen to PLUTO as a result of the 2020 Census release

github-actions[bot] commented 3 years ago

Stale issue message

lseirup commented 3 years ago

I don't think we can delete Tract2010 or change the format for CT2010 and CB2010. Agencies may have processes in place that expect that data.

AmandaDoyle commented 3 years ago

Add 2 new 2020 fields with proposed formatting Keep 2010 fields as is and phase out 2010 fields eventually

AmandaDoyle commented 3 years ago

Edited to add BCT2010 and BCTCB2010 fields per BC's comment

@SPTKL more detail on census fields Leave the following fields unchanged:

Add the following fields after the CD field (between CD and CT2010). The formatting of these fields will be the same as the formatting of the fields in DevDB, and they'll be created the same way.

@lseirup Can you sign off on the above? ^ Final and confirmed by @lseirup. Only add in the two new 2020 CT and CB fields.

Given that we're not changing the 2010 fields and not formatting the 2020 fields to match the 2010 fields in PLUTO the addition of the 2020 fields does not have to follow the 2010 workflow. I think that we can do the following:

Yes, this is overly complicated.

SPTKL commented 3 years ago

we should also add BCT2010 and BCTCB2010 so that agencies can have something to switch to if they no longer want CT2010, CB2010, Tract2010, and we should warn them about deprecation

SPTKL commented 3 years ago

@AmandaDoyle what about NTA and CDTA

SPTKL commented 3 years ago

@AmandaDoyle what about NTA and CDTA

Confirmed with Lynn that NTA and CDTA will not be part of pluto