City of Phoenix Human Services Department 2016 Community Assessment Page | A-1 Appendix A: Census and Caseload Data Allocation Methodology Appendix Title Page Appendix A-I Community Assessment Demographic Data Overview A-2 Appendix A-II Zip Code Allocations by Village A-7 Appendix A-III Zip Code Allocations by Early Head Start/Head Start Delegate A-9 Agency Service Areas Appendix A-IV Census Tract Allocations by Village A-11 Appendix A-V Census Tract Allocations by Early Head Start/Head Start Delegate A-21 Agency Service Areas April 18, 2016 City of Phoenix Human Services Department 2016 Community Assessment Page | A-2 Appendix A-I: Community Assessment Demographic Data Overview Demographic data included in the City of Phoenix Human Services Department’s 2016 Community Assessment has been adapted from the Census Bureau’s American Community Survey (ACS) five-year estimates for 2010 through 2014. This Appendix provides a brief overview of the ACS, lists the specific tables used in the Community Assessment, and outlines the methodologies used to map the data and combine race and ethnicity data. Background The American Community Survey differs from the decennial Census in several important ways: • The ACS is an ongoing survey that provides data every year, compared to the Census, which is conducted once per decade • The ACS collects much more detailed demographic data than the Census, which only gathers data regarding gender, age, race/ethnicity, and home ownership • The ACS is an estimate based on a sample – about one percent of households are surveyed every year – compared to the Census, which aims to collect data from every household The first two bullets highlight the primary benefits of the ACS and the reasons it was used in the Community Assessment: its timeliness and the depth of information it provides. The ACS makes available three different estimate timeframes: one-year, three-year, and five- year. The one-year estimates are the most timely because they are based entirely on data collected over the past year compared to the five-year figures for which 20 percent of the estimate is based on data from five years ago, 20 percent is derived from four year-old data, etc. The five-year estimates are derived from larger samples (that is, five years of surveys) so they will generally have a lower potential sampling error. Most importantly, data for individual census tracts are included only in the five-year estimates. In order to provide analyses at a sub- city level (i.e., across urban villages and Head Start service areas), the Community Assessment therefore uses the five-year estimates. ACS Tables Used ACS data is made available online at factfinder.census.gov/. The Census Bureau has constructed a number of tables to summarize the data collected in the ACS. Figure A-1 lists the ACS data included in the Community Assessment and the table from which each was adapted. April 18, 2016 City of Phoenix Human Services Department 2016 Community Assessment Page | A-3 Figure A-1: Source of Demographic Data Included in Community Assessment Demographic Data American Community Survey (ACS) Table Used Total Residents (Total and B17001: Poverty Status in Past 12 Months by Sex by Age Individuals Living in Poverty) Household Composition B17017: Poverty Status in Past 12 Months by Household (Total and Households Living Type by Age of Householder in Poverty) S1101: Households and Families Households in Poverty with a B17010: Poverty Status in the Past 12 Months of Families by Child Under Five Years of Family Type by Presence of Related Children Under 18 Age Years of Age by Age of Related Children Age Ranges (Total and B01001: Sex by Age Individuals Living in Poverty) B17001: Poverty Status in Past 12 Months by Sex by Age Median Age B01002: Median Age by Sex Race/Ethnicity (Total and B01001: Sex by Age Individuals Living in Poverty) B03002: Hispanic or Latino Origin by Race B17001: Poverty Status in Past 12 Months by Sex by Age B17020: Poverty Status in the Past 12 Months by Age Citizenship (Total and B17025: Poverty Status in the Past 12 Months by Nativity Individuals Living in Poverty) B05003: Sex by Age by Nativity and Citizenship Status Language Spoken at Home/ B16002: Household Language by Household Limited Linguistic Isolation English Speaking Status Educational Attainment (Age B17003: Poverty Status in the Past 12 Months of Individuals 25+) (Total and Individuals by Sex by Educational Attainment Living in Poverty) DP02: Selected Social Characteristics in the United States Employment Status (Age 16+) DP03: Selected Economic Characteristics B17005: Poverty Status in the Past 12 Months of Individuals by Sex by Employment Status Household Income DP03: Selected Economic Characteristics Median Income S1903: Median Income in the Past 12 Months (in 2010 Inflation-Adjusted Dollars) Income as a Percent of B17024: Age by Ratio of Income to Poverty Level in the Poverty (Age 55+) Past 12 Months Households with One or More B11007: Households by Presence of People 65 Years and People 65 Years and Over Over by Household Size and Household Type Grandparents Living with B10051: Grandparents Living with Own Grandchildren Grandchildren Under 18 Years by Responsibility for Own Grandchildren by Presence of Parent of Grandchildren and Age of Grandparent Home Ownership Rates B25008: Total Population in Occupied Housing Units by Tenure April 18, 2016 City of Phoenix Human Services Department 2016 Community Assessment Page | A-4 Figure A-1: Source of Demographic Data Included in Community Assessment Demographic Data American Community Survey (ACS) Table Used Percent of Three and Four S1401: School Enrollment Year-Olds Enrolled in School Residents by Disability Type S1810: Disability Characteristics Health Insurance Coverage S2701: Health Insurance Coverage Status Health Insurance by Age B27010: Types of Health Insurance by Age Summarizing Data by Village/Head Start Service Area Given the geographic size and diversity of the City, the Community Assessment summarizes demographic and caseload data at sub-City levels. Specifically, this data was reported for the City’s urban villages and Head Start service areas. Allocation methodologies were developed in order to provide estimates for these smaller geographic areas. Dividing the City into smaller areas allows service planning to take into consideration the unique characteristics of the City’s neighborhoods. To facilitate this planning and taking advantage of already-defined regions, the Community Assessment details demographic and caseload data within each of the City’s 15 urban villages. The villages – and the Planning Committee within each – exist to assist the City in updating the General Plan; defining the future function, density, and character of subareas within the village; and commenting on proposals for new zoning or land use districts. A map outlining the boundaries of these villages is included as Figure 1 in the Community Assessment. Data was similarly detailed for Early Head Start and Head Start service areas. In most cases, these services areas correspond to the boundaries of a school district or group of school districts1. Allocating information provided for census tracts and zip codes required the development of ‘keys’ to apportion the data. In brief, this process involved: • Collecting ‘shape files’ that outline the location boundaries of the geographic areas for 2 analysis (that is, the urban villages and Head Start service areas) 3 • Overlaying these shape files with City boundary , census tract, and zip code shape files 4 • Further overlaying these files with census block and city boundary shape files 1 Two different Head Start delegate agencies – Booker T. Washington and Greater Phoenix Urban League – serve portions of the Phoenix Elementary School District. 2 The ‘shape files’ for the urban villages and Early Head Start service area were provided by the City. The school district ‘shapes’ were gathered from the Census Bureau. Phoenix Elementary School had to be split at Central Avenue to apportion its area to the two agencies that serve it. 3 If a school district extended outside of the Phoenix, the analysis included only the portion within the City. 4 The smallest Census geographic area is the census block. A collection of these blocks roll-up to form a census block group. And a collection of census blocks groups form a census tract. April 18, 2016 City of Phoenix Human Services Department 2016 Community Assessment Page | A-5 • Calculating the total population of each zip code or census tract by adding the populations of the census blocks within each zip code or census tract • Calculating the percentage of the total population of each census tract or zip code that is within the City limits by comparing the populations of the census blocks within the City to the total determined in the previous step • Calculating the percentage of the City population that is within each urban village or Head Start service area by comparing the populations of the census blocks within the zip code or census tract to the City total determined in the previous step • Applying these percentages to the census tract and zip code data to allocate the data to urban village and Head Start service areas An example can make the methodology clearer. In this example, an estimate of the number of service users – based on caseload estimates by zip code – is developed for Example Unified School District (EUSD): • An overlay analysis shows that all of zip code 12345 is within the city limits • Another overlay shows a portion, but not all, of zip code 12345 lies within EUSD • The 12345 zip code is composed of three census blocks • These census blocks have populations of 30, 40, and 50 individuals, for a total of 120 • Only one of these census blocks – the one with a population of 30 – is in EUSD; thus, 25 percent (30 divided by 120) of any data for zip code 12345 is allocated to EUSD • There are a total of 20 service users in zip code 12345 so an estimated 5 (20 multiplied by 25 percent) are in the EUSD boundaries The allocation keys that were created are attached as Appendices A-II through A-V.