Open lucasmbrown-usds opened 2 years ago
@BethMattern - can you confirm that these files should be created as both CSVs and Excels?
And also, where would you like these files to live? Here are some options:
As standalone files that get linked from the https://screeningtool.geoplatform.gov/en/downloads page. Such as,
Combined into one big zip file that can be downloaded
We have a bit of a sticking point here. There's no tool out there to map from 2010 Census Tracts to 2020 Zip Codes by weighted population. GeoCorr does not support it.
Ideally, we would use weighted population to representing the % of people inside of a zip code who live in DACs. This will be more accurate than using simply geographic area, since the zip code may have most of the population concentrated in a certain number of tracts.
So we have only a few options I'm aware of:
We could convert 2010 Census Tracts to 2020 ZCTA by geographic overlap only, not using population at all. This is already implemented.
We could convert from 2010 Census Tracts to 2010 ZCTA by weighted population using Geocorr, and then convert from 2010 ZCTA to 2020 ZCTA using geographic overlap only.
We could convert from 2010 Census Tracts to 2010 Census Blocks by weighted population using Geocorr, then use geographic overlap to convert from 2010 Census Blocks to 2020 Census Blocks using census relationship files, and then convert 2020 Census Blocks to 2020 ZCTA by weighted population using GeoCorr.
Very similar to Option 3: We could convert from 2010 Census Tracts to 2010 Census Blocks by weighted population using Geocorr, then use NHGIS's crosswalk files to convert from 2010 Census Blocks to 2020 Census Blocks by weighted population, and then convert 2020 Census Blocks to 2020 ZCTA by weighted population using GeoCorr.
Finally, after all the above is completed, we need to map 2020 ZCTAs to 2020 zip codes, which are not the same.
ZCTAs can include one or more zip codes. See explanation here.
To convert from 2020 ZCTA to 2020 Zips, we have a couple of options:
and
https://udsmapper.org/zip-code-to-zcta-crosswalk/
The latter seems to be more actively maintained.
Many thanks to @JoeGermuska for his help assembling this information! Joe also recommends posting to https://acsdatacommunity.prb.org/discussion-forum/ with this question.
Do ranges instead of single number.
Another option:
Produce spreadsheet with:
1-2 is already implemented.
An idea we've eliminated: ~Randomly sample dividing 2010 tracts into 2010 blocks and getting ranges of the distribution. Generate a parameter q*x
where the population of a block can be divided into tracts within the range q
and (1-q)
.~
Description Many program officers distribute funding not at the census tract level but using other geographies such as county or zip code. In order for them to use the definition of DACs, they need to translate the census tract data into those other geographic units.
Solution Modify the ETL pipeline to create two separate files:
Make these files available in S3 with a link from Github or another location.