I just downloaded the current census response rates file for Illinois. My focus in Chicago. When I matched the response rate file to the latest ACS I did not get a match.
For example, ACS 2018 for Chicago has a tract 3201.00. The incoming response rate file has tracts 3201.01 and 3201.02.
The incoming response rate file has tracts 3301.01, 3301.02 and 3301.03; the 2018 ACS file includes 3301.00.
There are 8-9 similar mismatches, always with the response rate file having more new variants of the 2018 ACS tract structure.
Ouch! Did they do retracting of fairly settled cities for 2020? Looking around, I can find no info.
Huge implications.
To go back to the original question and the follow up from Bernie, new tracts were developed under the PSAP program earlier this year using housing unit counts derived from 2010 figures plus new construction…
Unfortunately, the Bureau released the 2020 response rates in 2020 Census tracts, not 2010 Census tracts. (Really frustrating).
A similar question was posted on the Census API developer's forum at the beginning of the response perdio. I shared some code with Stuart Lynn, out of NYC, that I use to proportionally reallocate the 2020 tracts and their response back into 2010 census tracts. He has been making those 2020 responses in 2010 geographies publicly available in his Git repository. You can access that information here: https://github.com/stuartlynn/census_2020_response_rates/tree/master/data/counts_adjusted_for_2010
How can they draw new tracts before the census count is complete? Aren't tracts supposed to be based on population?