Values of Zero for Median Year Structure Built

For the latest 5-year ACS estimates, I noticed a discrepancy in the values for MEDIAN YEAR STRUCTURE BUILT BY TENURE (B25037_001) between the 5-year state summary file records and the matching data on data.census.gov.

 For example, Lincoln County, Kansas (FIPS: 105) shows a median year of “0” in the summary file (All_Geographies_Not_Tracts_Block_Groups\Kansas_All_Geographies_Not_Tracts_Block_Groups\e20195ks0113000.txt) but a median year of "1939-" online (https://data.census.gov/cedsci/table?q=median%20year%20house%20built&g=0500000US20105,36047&tid=ACSDT5Y2019.B25037&hidePreview=true).

 This pattern appears to be consistent for 2014-2018 and 2015-2019 ACS data, with values of "0" in the summary files being matched by "1939-" entries on the website. Since there are also no values of '1939' in either of those summary files I am guessing that the zero entries represent median years that are 1939 or older. However, I’ve reached out to the Census to confirm this.

 Is anyone else finding similar issues with the summary file and website values not matching?

Top Replies

Parents
  • Yes, "jam values" such as the top end and bottom end of these types of year categories are different in the summary file data / API data, vs. data.census.gov.  Data.census.gov has the true value  - 1939 and older, in this case - whereas the other formats need to keep it as numeric rather than string. Here's the logic of how I handled the jam values in the summary file and API formats:  (If I've missed something, I'd love to know!)

    define new string variable = B25037_calc_txt001E

    if B25037_001E == 0, then return "Before 1939"

    else if B25037 == 19, then return "2014 or later"

    else, return B25037_001E

Reply
  • Yes, "jam values" such as the top end and bottom end of these types of year categories are different in the summary file data / API data, vs. data.census.gov.  Data.census.gov has the true value  - 1939 and older, in this case - whereas the other formats need to keep it as numeric rather than string. Here's the logic of how I handled the jam values in the summary file and API formats:  (If I've missed something, I'd love to know!)

    define new string variable = B25037_calc_txt001E

    if B25037_001E == 0, then return "Before 1939"

    else if B25037 == 19, then return "2014 or later"

    else, return B25037_001E

Children