You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the bug fix for the census tables. Because the correct 2010 tabes for age and sex by race are only available at the tract level and up (the tables' prefix is PCT), requests for all 2010 block-level data yield tables with NAs (and a warning from each API call) after this fix -- even when age and sex args are FALSE. The package should probably (?) throw an error if block-level data is requested and either age OR sex is TRUE.
See, for example, the output of:
get_census_data(states = 'WY', age = F, sex = F, year = '2010', census.geo = 'block', county.list = list('WY' = '017'))
While it's not possible, therefore, to impute race with age and sex conditioning at the block level in the 2010 census, one could still do so at the block level if age and sex args are FALSE. The package would instead have to pull race/ethnicity totals from Table P5 in the 2010 SF1.
The text was updated successfully, but these errors were encountered:
Thanks for the bug fix for the census tables. Because the correct 2010 tabes for age and sex by race are only available at the tract level and up (the tables' prefix is
PCT
), requests for all 2010 block-level data yield tables with NAs (and a warning from each API call) after this fix -- even whenage
andsex
args areFALSE
. The package should probably (?) throw an error if block-level data is requested and eitherage
ORsex
isTRUE
.See, for example, the output of:
While it's not possible, therefore, to impute race with age and sex conditioning at the block level in the 2010 census, one could still do so at the block level if
age
andsex
args areFALSE
. The package would instead have to pull race/ethnicity totals from Table P5 in the 2010 SF1.The text was updated successfully, but these errors were encountered: