/1.0/data/show/latest does an incomplete job of assessing releases for data availability
JoeGermuska opened this issue · 0 comments
JoeGermuska commented
Profile pages make a single call for data from both B08006 and B08013. Isabella County, MI doesn't have B08006 data in the ACS 2019-1yr release, so the return from the API call returns data for the 2019-1, but Isabella has no representation at all of B08006
A separate call for just B08006 for the same geographies correctly falls back to the 5-year release.
The API should be sure to check through all tables to choose the most complete release.