The features in this layer represent the five-digit ZIP Code areas that are used by the U.S. Postal Service to deliver mail more effectively. This layer provides ZIP Code, postal district name, population, and area for the ZIP Code areas in California.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2020 Census.

U.S. ZIP Code Areas (Five-Digit) represents five-digit ZIP Code areas used by the U.S. Postal Service to deliver mail more effectively. The first digit of a five-digit ZIP Code divides the United States into 10 large groups of states numbered from 0 in the Northeast to 9 in the far West. Within these areas, each state is divided into an average of 10 smaller geographical areas, identified by the second and third digits. These digits, in conjunction with the first digit, represent a sectional center facility or a mail processing facility area. The fourth and fifth digits identify a post office, station, branch or local delivery area.

Adult respondents ages 18+ who were ever diagnosed with heart disease by a doctor. Years covered are from 2013-2014 by zip code. Data taken from the California Health Interview Survey Neighborhood Edition (AskCHIS NE) (http://askchisne.ucla.edu/), downloaded February 2018.AskCHIS Neighborhood Edition is an online data dissemination and visualization platform that provides health estimates at sub-county geographic regions. Estimates are powered by data from The California Health Interview Survey (CHIS). CHIS is conducted by The UCLA Center for Health Policy Research, an affiliate of UCLA Fielding School of Public Health.Health estimates available in AskCHIS NE (Neighborhood Edition) are model-based small area estimates (SAEs).SAEs are not direct estimates (estimates produced directly from survey data, such as those provided through AskCHIS).CHIS data and analytic results are used extensively in California in policy development, service planning and research, and is recognized and valued nationally as a model population-based health survey.Before using estimates from AskCHIS NE, it is recommended that you read more about the methodology and data limitations at: http://healthpolicy.ucla.edu/Lists/AskCHIS%20NE%20Page%20Content/AllItems.aspx. You can go to http://askchisne.ucla.edu/ to create your own account.Produced by The California Health Interview Survey and The UCLA Center for Health Policy Research and compiled by the Los Angeles County Department of Public Health. "Field Name = Field Definition"Zipcode" = postal zip code in the City of Los Angeles “Percent” = estimated percentage of adult respondents ages 18+ who were ever diagnosed with heart disease by a doctor"LowerCL" = the lower 95% confidence limit represents the lower margin of error that occurs with statistical sampling"UpperCL" = the upper 95% confidence limit represents the upper margin of error that occurs in statistical sampling "Population" = estimated population 18 and older (denominator) residing in the zip code Notes: 1) Zip codes are based on the Los Angeles Housing Department Zip Codes Within the City of Los Angeles map (https://media.metro.net/about_us/pla/images/lazipcodes.pdf).2) Zip codes that did not have data available (i.e., null values) are not included in the dataset; there are additional zip codes that fall within the City of Los Angeles.3) Zip code boundaries do not align with political boundaries. These data are best viewed with a City of Los Angeles political boundary file (i.e., City of Los Angeles jurisdiction boundary, City Council boundary, etc.) FAQS: 1. Which cycle of CHIS does AskCHIS Neighborhood Edition provide estimates for?All health estimates in this version of AskCHIS Neighborhood Edition are based on data from the 2013-2014 California Health Interview Survey. 2. Why do your population estimates differ from other sources like ACS? The population estimates in AskCHIS NE represent the CHIS 2013-2014 population sample, which excludes Californians living in group quarters (such as prisons, nursing homes, and dormitories). 3. Why isn't there data available for all ZIP codes in Los Angeles?While AskCHIS NE has data on all ZCTAs (Zip Code Tabulation Areas), two factors may influence our ability to display the estimates:A small population (under 15,000): currently, the application only shows estimates for geographic entities with populations above 15,000. If your ZCTA has a population below this threshold, the easiest way to obtain data is to combine it with a neighboring ZCTA and obtain a pooled estimate.A high coefficient of variation: high coefficients of variation denote statistical instability.

A dataset showing the population of 91331 between 2010 and 2020.

Adult respondents ages 18+ who were ever diagnosed with asthma by a doctor. Years covered are from 2013-2014 by zip code. Data taken from the California Health Interview Survey Neighborhood Edition (AskCHIS NE) (http://askchisne.ucla.edu/), downloaded February 2018. AskCHIS Neighborhood Edition is an online data dissemination and visualization platform that provides health estimates at sub-county geographic regions. Estimates are powered by data from The California Health Interview Survey (CHIS). CHIS is conducted by The UCLA Center for Health Policy Research, an affiliate of UCLA Fielding School of Public Health.Health estimates available in AskCHIS NE (Neighborhood Edition) are model-based small area estimates (SAEs).SAEs are not direct estimates (estimates produced directly from survey data, such as those provided through AskCHIS).CHIS data and analytic results are used extensively in California in policy development, service planning and research, and is recognized and valued nationally as a model population-based health survey.Before using estimates from AskCHIS NE, it is recommended that you read more about the methodology and data limitations at: http://healthpolicy.ucla.edu/Lists/AskCHIS%20NE%20Page%20Content/AllItems.aspx. You can go to http://askchisne.ucla.edu/ to create your own account.Produced by The California Health Interview Survey and The UCLA Center for Health Policy Research and compiled by the Los Angeles County Department of Public Health. "Field Name = Field Definition "Zipcode" = postal zip code in the City of Los Angeles “Percent” = estimated percentage of adult respondents ages 18+ who were ever diagnosed with asthma by a doctor"LowerCL" = the lower 95% confidence limit represents the lower margin of error that occurs with statistical sampling"UpperCL" = the upper 95% confidence limit represents the upper margin of error that occurs in statistical sampling "Population" = estimated population 18 and older (denominator) residing in the zip code Notes: 1) Zip codes are based on the Los Angeles Housing Department Zip Codes Within the City of Los Angeles map (https://media.metro.net/about_us/pla/images/lazipcodes.pdf).2) Zip codes that did not have data available (i.e., null values) are not included in the dataset; there are additional zip codes that fall within the City of Los Angeles.3) Zip code boundaries do not align with political boundaries. These data are best viewed with a City of Los Angeles political boundary file (i.e., City of Los Angeles jurisdiction boundary, City Council boundary, etc.) FAQS: 1. Which cycle of CHIS does AskCHIS Neighborhood Edition provide estimates for?All health estimates in this version of AskCHIS Neighborhood Edition are based on data from the 2013-2014 California Health Interview Survey. 2. Why do your population estimates differ from other sources like ACS? The population estimates in AskCHIS NE represent the CHIS 2013-2014 population sample, which excludes Californians living in group quarters (such as prisons, nursing homes, and dormitories). 3. Why isn't there data available for all ZIP codes in Los Angeles?While AskCHIS NE has data on all ZCTAs (Zip Code Tabulation Areas), two factors may influence our ability to display the estimates:A small population (under 15,000): currently, the application only shows estimates for geographic entities with populations above 15,000. If your ZCTA has a population below this threshold, the easiest way to obtain data is to combine it with a neighboring ZCTA and obtain a pooled estimate.A high coefficient of variation: high coefficients of variation denote statistical instability.

This layer is a component of Map service for the zipcodes web page.

The most complete and up-to-date Canadian postal code database for accurate customer profiling, direct marketing optimization, precise territory management, and serviceability insights. Postal Code Suite offers six digit postal code polygons so you can visualize postal code boundaries on a map. Each zip package includes Multiple Enhanced Postal Codes, Forward Sortation Areas, Local Delivery Units and topographic layers, for the province/territory, as well as Canada wide layers for area codes, capital cities, provincial boundaries, municipal boundaries, topographic boundaries, time zones and water layers.

US Census American Community Survey (ACS) 2018, 5-year estimates of the key economic characteristics of ZIP Code Tabulation Areas geographic level in Orange County, California. The data contains 397 fields for the variable groups E01: Employment status (universe: population 16 years and over, table X23, 7 fields); E02: Work status by age of worker (universe: population 16 years and over, table X23, 36 fields); E03: Commuting to work (universe: workers 16 years and over, table X8, 8 fields); E04: Travel time to work (universe: workers 16 years and over who did not work at home, table X8, 14 fields); E05: Number of vehicles available for workers (universe: workers 16 years and over in households, table X8, 8 fields); E06: Median age by means of transportation to work (universe: median age, workers 16 years and over, table X8, 7 fields); E07: Means of transportation to work by race (universe: workers 16 years and over, table X8, 64 fields); E08: Occupation (universe: civilian employed population 16 years and over, table X24, 53 fields); E09: Industry (universe: civilian employed population 16 years and over, table X24, 43 fields); E10: Class of worker (universe: civilian employed population 16 years and over, table X24, 19 fields); E11: Household income and earnings in the past 12 months (universe: total households, table X19, 37 fields); E12: Income and earnings in dollars (universe: inflation-adjusted dollars, tables X19-X20, 31 fields); E13: Family income in dollars (universe: total families, table X19, 17 fields); E14: Health insurance coverage (universe: total families, table X19, 17 fields); E15: Ratio of income to Poverty level (universe: total population for whom Poverty level is determined, table X17, 8 fields); E16: Poverty in population in the past 12 months (universe: total population for whom Poverty level is determined, table X17, 7 fields); E17: Poverty in households in the past 12 months (universe: total households, table X17, 9 fields); E18: Percentage of families and people whose income in the past 12 months is below the poverty level (universe: families, population, table X17, 8 fields), and; X19: Poverty and income deficit (dollars) in the past 12 months for families (universe: families with income below Poverty level in the past 12 months, table X17, 4 fields). The US Census geodemographic data are based on the 2018 TigerLines across multiple geographies. The spatial geographies were merged with ACS data tables. See full documentation at the OCACS project github page (https://github.com/ktalexan/OCACS-Geodemographics).

The Forward Sortation Area Boundary File depicts the boundaries of forward sortation areas (FSAs) derived from postal codes captured from federal census questionnaires. This is based on census dissemination areas. The file is periodically updated, following the federal census which is currently mandated every 5 years (2011, 2016, 2021...). More information is available at: Forward Sortation Area Boundary File

This data set of line features represent Riverside County's recorded street centerlines.This data set was designed to carry out functions of the Transportation department and is not a true street network layer. Centerlines do not have complete "connectivity" due to the fact that this layer is primarily roads that have been recorded but does not necessarily contain all roads. OBJECTID - Internal feature number. STNAME - Recorded name of the centerline. TYPE - Used to classify roads, primarily by surface type. Description of the codes found in the attribute "TYPE" TYPE DESCRIPTION C01 Federal Aid Interstate C02 State Highways C03 F.A.U. Maintained C04 F.A.S. Maintained C05 Paved Surface Maintained C06 Paved Surface (Traveled) C07 Graveled Surface Maintained C08 Graveled Surface (Traveled) C09 Dirt Surface Maintained C10 Dirt Surface (Traveled) C11 Accepted For Public Use C12 Non-County/Accepted for P.U. C13 Non-County road C14 Vacated C15 Abandon C16 Maintained F.A.U./Non-County C17 Maintained F.A.S./Non-County C18 Maintained Paved/Accepted C19 Maintained Paved/Non-County C20 Maintained Paved/Vacated C21 Maintained Gravel/Accepted C22 Maintained Gravel/Non-County C23 Maintained Gravel/Vacated C24 Maintained Dirt/Accepted C25 Maintained Dirt/Non-County C26 Maintained Dirt/Vacated C27 Accepted/Vacated C28 Maintained Under Contract C29 City Road C30 Paved Maintained/Dirt Maintained C31 Dedicated and Accepted/CFD Maintained W01 Maintained for City W02 Maintained for City/Non-County W03 Maintained for City/Non-County (Reversed) W04 Maintained for City/Accepted W05 F.A.U. Maintained/Maintained for City W06 Dirt Surface Maintained/Maintained for City W07 Paved Surface Maintained/Maintained for City W08 Graveled Surface Maintained/Maintained for City Z01 Traffic Division Modeling Connectivity Use Only (The "W" series within the TYPE field were initially created for the City of Wildomar, but have had their application expanded to include any Centerline where the County maintains the road for a City - typically for a limited period after a City's incorporation. The "W" will continue as a convention to make it easy to distinguish such roads from roads normally maintained by the County, even though it is understood that the "W" will lose its initial association with the City of Wildomar over time.). GENPLANTYPE - General Plan Classification of the Road. Not corrected for the RCLIS 2003 updated at thsi time. Description of the codes found in the attribute "GENPLANTYPE" GENPLANTYPE SYMBOL DESCRIPTION 01 101 FREEWAY 02 201 EXPRESSWAY 03 301 URBAN ARTERIAL 04 304 URBAN ARTERIAL (PROPOSED) 05 401 ARTERIAL 06 404 ARTERIAL (PROPOSED) 07 501 MOUNTAIN ARTERIAL 08 504 MOUNTAIN ARTERIAL (PROPOSED) 09 13 MAJOR 10 16 MAJOR (PROPOSED) 11 21 SECONDARY 12 24 SECONDARY (PROPOSED) 13 801 SPECIFIC PLAN ROAD 14 804 SPECIFIC PLAN ROAD (PROPOSED) 15 25 SCENIC ROUTE 16 28 SCENIC ROUTE (PROPOSED) 17 0 COLLECTOR(PROPOSED) indicates that the road is part of the "General PLan Alignment" but does not currently exist as a legal centerline. This type of centerline will be stored in the CENTERLINEREF data set. DIRECTION - Represents the direction of traffic flow. Presently not supported. NAMEID - Numerical representation of the recorded street name. Unique STNAME and NAMEID values are tracked in the STNMS table. RDNUMBER - Used by the Transportation Department to identify county maintained roads. Used for accounting purposes. SEGNUMBER - Used in combination with the RDNUMBER to uniquely identify an individual centerline, segment, or length. No longer supported. FLAG - Indicates whether or not an arc will be used in a street network data set. Presently not used because there is no street network data set. L_F_ADD - The starting address for the left side of the street. L_T_ADD - The ending address for the left side of the street. R_F_ADD - The starting address for the right side of the street. R_T_ADD - The ending address for the right side of the street. PRE_DIR - The street direction prefix. Example: 'E' for east. STREET_NAME - The base legal street name of the centerline. Example: "MAIN". STREET_TYPE - The Street Name Type abbreviation. Example: 'ST' for street. Valid values for the STREET_TYPE field are: ' ' - ' ' (No Type is a space) AVE - AVENUE BLVD - BOULEVARD CIR - CIRCLE CT - COURT CV - COVE DR - DRIVE EXPY - EXPRESSWAY FWY - FREEWAY HWY - HIGHWAY LN - LANE LOOP - LOOP PATH - PATH PKWY - PARKWAY PL - PLACE PT - POINT RD - ROAD SQ - SQUARE ST- STREET TER - TERRACE TRL - TRAIL WALK - WALK WAY - WAY SUF_DIR - The street direction suffix. Example: "N' for north. TRACT - The tract map number in which the centerline can be found. MODIFIED - Modified Date CREATED - Created Date SOURCE_NOTES - References to legal documentation related to the Centerline found during research, including such things as recordation histroy, name change history, and acceptance for or termination of maintenance information, FULL_NAME - Name used to construct ROUTE_NAME field values. Used to detect changes in the STNAME value. AREA_PLAN_ABBREVIATION - Abbreviated Area Plan Name used to create ROUTE_NAME Valid values for AREA_PLAN_ABBREVIATION are: DESCN - Desert Center ECDES - East County/Desert ECVAP - Eastern Coachella Valley Plan ELSIN - Lake Elsinore EVALE - Eastvale HIGHG - Highgrove HVWIN - Harvest Valley/Winchester JURUP - Jurupa LAKEV - Lakeview/Nuevo LMATH - Lake Mathews MARCH - March MEADV - Mead Valley PASS - Pass Area PVERD - Palo Verde Valley RECHE - Reche Canyon REMAP - REMAP (Riverside Extended Mountain Area Plan) RIVER - Riverside/Corona/Norco SANJA - San Jacinto Valley SBCO - San Bernardino County SUNCI - Sun City/Menifee Valley SWAP - Southwest Area Plan TEMES - Temescal Valley WCVAP - Western Coachella Valley Area Plan SUBROUTE - Optional Identifier used to build ROUTE_NAME to separate branches or distiguish discontinuous portions of a street within an area plan that are unlikely to ever form a continuous route. ROUTE_NAME - Primary field used to construct a Linear Referencing derivative of the Centerlines layer. THis values is a component of ROUTE_ALT1 and ROUTE_ALT2 and is overriden by those fields when they have values. ROUTE_DIR1 - Used with ROUTE_NAME to build values for ROUTE_ALT1 when there is a value assigned. ROUTE_ALT1 - First Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Norh or East. ROUTE_DIR2 - Used with ROUTE_NAME to build values for ROUTE_ALT2 when there is a value assigned. ROUTE_ALT2 - Second Alternative ROUTE_NAME value. Typically used for one-way streets that are oriented Souh or West. BUILD_PRIORITY - Used to create Linear Referenced Routes. Sets the corner from which to build routes. Valuid values for BUILD_PRIORITY are: UL - Upper Left (Default) LL - Lower Left UR - Upper Right LR - Lower Right LINE_LINK - Geometric ID of Centerline arc. Made up of the From X/Y coordinate, the To X/Y coordinate and the Length. Used to detect geometric changes to an existing Centerline. CL_ID - Duplicate of OBJECTID. USed for detecting newly added segments to the network each week or to relate and join exported versions of CENTERLINES back to the original CENTERLINE feature class.FROM_X_COORDINATE, FROM_Y_COORDINATE, TO_X_COORDINATE and TO_Y_COORDINATE: The coordinate data for the end points of the line in numeric format.ROUTE_ORIENTED: Indicates if the line is drawn in the direction that corresponds to the Routes created based on the ROUTE_NAME fields.TRAVEL_DIRECTIONS: Indicates whether the road can be driven and in what directions. Values include "Both Ways", "From-To", "To-From" and "No Ways".CA_ROAD_SYSTEM_PAGE: The map page location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_ROAD_SYSTEM_INDEX: The map index grid location of the California Roadway System (CRS) Maps containing the Centerline: See http://www.dot.ca.gov/hq/tsip/hseb/crs_maps/CA_FUNCTIONAL_CLASS: The California Functional Classification of the Roadway per the CRS maps. Only classifications between 1 and 5 may qualify for state and federal funds. Classifications include:1 - Interstate2 - Other Freeway or Expressway3 - Other Principal Arterial4 - Minor Arterial5 - Major Collector6 - Minor Collector7 - LocalFEDERAL_ROUTE and FEDERAL_ROUTE_TYPE: The number of the Federal Interstate or U.S. Highway and the operational type of the facility, where applicable.STATE_ROUTE and STATE_ROUTE_TYPE: The number of the State Route or Highway and the operational type of the facility, where applicable.COUNTY_ROUTE: The number of a County Route.CITY_LEFT or CITY_RIGHT: The City or Community name to the left or right of the Centerline. Used for address geolocators.STATE: CA for Califonia. For geolocators that use the State field.ZIP_LEFT or ZIP_RIGHT: The ZIP code to the left or right of the Centerline. Used for address geolocators.FULL_NAME_MIXED_CASE: The full street name in mixed Upper and Lower case letters, sometimes also called Title case. May be used for labeling and geolocators.

US Census American Community Survey (ACS) 2014, 5-year estimates of the key housing characteristics of ZIP Code Tabulation Areas geographic level in Orange County, California. The data contains 406 fields for the variable groups H01: Housing occupancy (universe: total housing units, table X25, 3 fields); H02: Units in structure (universe: total housing units, table X25, 11 fields); H03: Population in occupied housing units by tenure by units in structure (universe: total population in occupied housing units, table X25, 13 fields); H04: Year structure built (universe: total housing units, table X25, 15 fields); H05: Rooms (universe: total housing units, table X25, 18 fields); H06: Bedrooms (universe: total housing units, table X25, 21 fields); H07: Housing tenure by race of householder (universe: occupied housing units, table X25, 51 fields); H08: Total population in occupied housing units by tenure (universe: total population in occupied housing units, table X25, 3 fields); H09: Vacancy status (universe: vacant housing units, table X25, 8 fields); H10: Occupied housing units by race of householder (universe: occupied housing units, table X25, 8 fields); H11: Year householder moved into unit (universe: occupied housing units, table X25, 18 fields); H12: Vehicles available (universe: occupied housing units, table X25, 18 fields); H13: Housing heating fuel (universe: occupied housing units, table X25, 10 fields); H14: Selected housing characteristics (universe: occupied housing units, table X25, 9 fields); H15: Occupants per room (universe: occupied housing units, table X25, 13 fields); H16: Housing value (universe: owner-occupied units, table X25, 32 fields); H17: Price asked for vacant for sale only, and sold not occupied housing units (universe: vacant for sale only, and sold not occupied housing units, table X25, 28 fields); H18: Mortgage status (universe: owner-occupied units, table X25, 10 fields); H19: Selected monthly owner costs, SMOC (universe: owner-occupied housing units with or without a mortgage, table X25, 45 fields); H20: Selected monthly owner costs as a percentage of household income, SMOCAPI (universe: owner-occupied housing units with or without a mortgage, table X25, 26 fields); H21: Contract rent distribution and rent asked distribution in dollars (universe: renter-occupied housing units paying cash rent and vacant, for rent, and rented not occupied housing units, table X25, 7 fields); H22: Gross rent (universe: occupied units paying rent, table X25, 28 fields), and; X23: Gross rent as percentage of household income (universe: occupied units paying rent, table X25, 11 fields). The US Census geodemographic data are based on the 2014 TigerLines across multiple geographies. The spatial geographies were merged with ACS data tables. See full documentation at the OCACS project github page (https://github.com/ktalexan/OCACS-Geodemographics).