2020 Census update

[AmandaDoyle]

• [ ] Add the following fields
• CenBlock2020
• BCTCB2020
• BCT2020
• NTA2020
• NTAName2020
• CDTA 2020
• [ ] Remove the following fields
• PUMA2010 TD: keep the puma as now since a lot demographics data is only available on PUM
• [ ] Create new aggregation tables
• Block
• Tract
• NTA

[SPTKL]

@td928

Data Source

• dcp_cb2010
• dcp_ct2010
• dcp_cb2020
• dcp_ct2020
• dcp_cdta2020
• dcp_nta2020
• dcp_nta2010

Edit scripts:

• bash/01_dataloading.sh
• sql/_functions.sql
• sql/_spatial.sql
• python/geocode.py
• python/geocode_hny.py

and any down stream script

[AmandaDoyle]

Need crosswalk from 2020 census track to council district and community district (? about if CDTA vs CD and ? about if we can use CD to CDTA crosswalk to do Censta tract to CD)

[AmandaDoyle]

@td928 Can you confirm that the new aggregation tables should be the following for 2020 geographies: _by_CensusBlock _by_CensusTract _by_NTA _by_CDTA _by_CommunityDistrict _by_CityCouncilDistrict

We're no longer producing _by_PUMA. Should we product both _by_CDTA and _by_CommunityDistrict or is one enough, and if so, which one should we create?

[td928]

Hi @AmandaDoyle! Yes we are comfortable with leaving out the PUMA table. Also, community district only should be okay.

[SPTKL]

do you still need CityCouncilDistrict

[AmandaDoyle]

@SPTKL flagging that in dcp_housing.latest cenblock2020 is NULL for all values