This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES: additional clarifying information about the action. BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the BOE's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

Counties in California intended for the NEVI Map.

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.

Jurisdictional boundaries for all cities and towns within Napa County, California.Jurisdictional boundaries for all cities and towns within Napa County, California.

Item last updated 03-07-2025 04:30

This is SCAG’s 2019 city boundary data (v.1.0), updated as of July 6, 2021, including the boundaries for each of the 191 cities and 6 county unincorporated areas in the SCAG region. The original city boundary data was obtained from county LAFCOs to reflect the most current updates and annexations to the city boundaries. This data will be further reviewed and updated as SCAG continues to receive feedbacks from LAFCOs, subregions and local jurisdictions.Data-field description:COUNTY: County name COUNTY_ID: County FIPS CodeCITY: City NameCITY_ID: City FIPS CodeACRES: Area in acresSQMI: Area in square milesYEAR: Dataset year

This map shows cases broken down by the county level and city level in Southern California.

Half-mile access sheds to open access open space in the conservation areas dataset built for CA Nature. Each has been intersected to a city and county dataset to allow summarization of demographics. These were then enriched using ESRI's geoenrichment services to provide select demographics. Three layers are included:1. Half-mile access sheds from open access areas considered 30x30 Conservation Areas (GAP Code 1 and 2)2. Half-mile access sheds from open access areas in the Conservation Areas dataset (GAP Codes 1, 2, 3, 4)3. All city and county areas to provide baseline demographics for comparison. Demographic variables include:PopulationAge DistributionEducational AttainmentHousing Unit OccupancyHispanic or Latino OriginRaceHousehold income

Geospatial data about Sacramento County, California City Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

City is a topologically correct polygon representation of city boundaries as recorded in Marin County Assessor map pages. Coverage includes the entire jurisdiction of Marin County, California.

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.

Vector polygon map data of city limits from Fresno, California containing 1 feature.

City limits GIS (Geographic Information System) data provides valuable information about the boundaries of a city, which is crucial for various planning and decision-making processes. Urban planners and government officials use this data to understand the extent of their jurisdiction and to make informed decisions regarding zoning, land use, and infrastructure development within the city limits.

By overlaying city limits GIS data with other layers such as population density, land parcels, and environmental features, planners can analyze spatial patterns and identify areas for growth, conservation, or redevelopment. This data also aids in emergency management by defining the areas of responsibility for different emergency services, helping to streamline response efforts during crises..

This city limits data is available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

This feature layer is a complete account of all incorporated cities, including the boundary and name of each individual city. This is a CAL FIRE dataset and it's primarily used for identifying incorporated areas, which are not eligible for State Responsibility Area (SRA) designation. Secondary uses are for cartographic purposes, e.g. adding city names and city limits to maps, and for creating contact lists for which cities fall within a certain designation. For CAL FIRE, this was especially relevant for notification of cities with Very High Fire Hazard Severity Zones.For this version (16_1), in addition to capturing annexations, we adusted city boundaries where appropriate to match updated county parcel data. These adjustments were typically done in areas where cities are adjacent to SRA, the process did not cover all city boundaries. This story map is part of the Watershed Improvement Program (WIP) and Watershed Information Network (WIN).The California Communities layer is a feature service used in the Sierra Nevada Cascade story map; therefore, it should not be altered or deleted under any circumstances while the story map is in use.

Vector polygon map data of property parcels from Fresno County, California containing 202,076 features.

Property parcel GIS map data consists of detailed information about individual land parcels, including their boundaries, ownership details, and geographic coordinates.

Property parcel data can be used to analyze and visualize land-related information for purposes such as real estate assessment, urban planning, or environmental management.

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

This website provides a limited number of Substructure Maps in “pdf” format via GIS polygons representing grids containing URL links. Across various areas of Los Angeles County, paper maps were created by Public Works (PW) and its predecessor Departments to show underground utilities such as cable TV, gas, oil, and telephone lines.

Though most of these maps are no longer updated, they can be useful as a research resource. Every reasonable effort has been made to assure the accuracy of this data and the maps referenced. Some cities may provide substructure information for the areas not covered by these grids. Additional and more accurate substructure data and information may also be obtained through the utility companies. Before digging, it is strongly advised to contact the Underground Service Alert (DigAlert Express) at www.digalert.org/digexpress.html or by calling 811.

Please note that California State Law Says, You Must Contact DigAlert!

The County of Los Angeles makes no warranty, representation, or guarantee as to the content, sequence, accuracy, timeliness, or completeness of any of the data provided herein or of any maps referenced. Los Angeles County Public Works recommends that all utility research be conducted under the supervision of a licensed civil engineer.

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.

This data depicts the boundaries for the City of Salinas, Monterey County, California. City boundaries are regulated and generated by the Local Agency Formation Commission (LAFCO) of Monterey County. The city's Sphere of Influence (SOI) is not included in this dataset but is available from the City of Salinas data portal.

This is the current Medical Service Study Area. California Medical Service Study Areas are created by the California Department of Health Care Access and Information (HCAI).Check the Data Dictionary for field descriptions.Search for the Medical Service Study Area data on the CHHS Open Data Portal.Checkout the California Healthcare Atlas for more Medical Service Study Area information.This is an update to the MSSA geometries and demographics to reflect the new 2020 Census tract data. The Medical Service Study Area (MSSA) polygon layer represents the best fit mapping of all new 2020 California census tract boundaries to the original 2010 census tract boundaries used in the construction of the original 2010 MSSA file. Each of the state's new 9,129 census tracts was assigned to one of the previously established medical service study areas (excluding tracts with no land area), as identified in this data layer. The MSSA Census tract data is aggregated by HCAI, to create this MSSA data layer. This represents the final re-mapping of 2020 Census tracts to the original 2010 MSSA geometries. The 2010 MSSA were based on U.S. Census 2010 data and public meetings held throughout California.Source of update: American Community Survey 5-year 2006-2010 data for poverty. For source tables refer to InfoUSA update procedural documentation. The 2010 MSSA Detail layer was developed to update fields affected by population change. The American Community Survey 5-year 2006-2010 population data pertaining to total, in households, race, ethnicity, age, and poverty was used in the update. The 2010 MSSA Census Tract Detail map layer was developed to support geographic information systems (GIS) applications, representing 2010 census tract geography that is the foundation of 2010 medical service study area (MSSA) boundaries. ***This version is the finalized MSSA reconfiguration boundaries based on the US Census Bureau 2010 Census. In 1976 Garamendi Rural Health Services Act, required the development of a geographic framework for determining which parts of the state were rural and which were urban, and for determining which parts of counties and cities had adequate health care resources and which were "medically underserved". Thus, sub-city and sub-county geographic units called "medical service study areas [MSSAs]" were developed, using combinations of census-defined geographic units, established following General Rules promulgated by a statutory commission. After each subsequent census the MSSAs were revised. In the scheduled revisions that followed the 1990 census, community meetings of stakeholders (including county officials, and representatives of hospitals and community health centers) were held in larger metropolitan areas. The meetings were designed to develop consensus as how to draw the sub-city units so as to best display health care disparities. The importance of involving stakeholders was heightened in 1992 when the United States Department of Health and Human Services' Health and Resources Administration entered a formal agreement to recognize the state-determined MSSAs as "rational service areas" for federal recognition of "health professional shortage areas" and "medically underserved areas". After the 2000 census, two innovations transformed the process, and set the stage for GIS to emerge as a major factor in health care resource planning in California. First, the Office of Statewide Health Planning and Development [OSHPD], which organizes the community stakeholder meetings and provides the staff to administer the MSSAs, entered into an Enterprise GIS contract. Second, OSHPD authorized at least one community meeting to be held in each of the 58 counties, a significant number of which were wholly rural or frontier counties. For populous Los Angeles County, 11 community meetings were held. As a result, health resource data in California are collected and organized by 541 geographic units. The boundaries of these units were established by community healthcare experts, with the objective of maximizing their usefulness for needs assessment purposes. The most dramatic consequence was introducing a data simultaneously displayed in a GIS format. A two-person team, incorporating healthcare policy and GIS expertise, conducted the series of meetings, and supervised the development of the 2000-census configuration of the MSSAs.MSSA Configuration Guidelines (General Rules):- Each MSSA is composed of one or more complete census tracts.- As a general rule, MSSAs are deemed to be "rational service areas [RSAs]" for purposes of designating health professional shortage areas [HPSAs], medically underserved areas [MUAs] or medically underserved populations [MUPs].- MSSAs will not cross county lines.- To the extent practicable, all census-defined places within the MSSA are within 30 minutes travel time to the largest population center within the MSSA, except in those circumstances where meeting this criterion would require splitting a census tract.- To the extent practicable, areas that, standing alone, would meet both the definition of an MSSA and a Rural MSSA, should not be a part of an Urban MSSA.- Any Urban MSSA whose population exceeds 200,000 shall be divided into two or more Urban MSSA Subdivisions.- Urban MSSA Subdivisions should be within a population range of 75,000 to 125,000, but may not be smaller than five square miles in area. If removing any census tract on the perimeter of the Urban MSSA Subdivision would cause the area to fall below five square miles in area, then the population of the Urban MSSA may exceed 125,000. - To the extent practicable, Urban MSSA Subdivisions should reflect recognized community and neighborhood boundaries and take into account such demographic information as income level and ethnicity. Rural Definitions: A rural MSSA is an MSSA adopted by the Commission, which has a population density of less than 250 persons per square mile, and which has no census defined place within the area with a population in excess of 50,000. Only the population that is located within the MSSA is counted in determining the population of the census defined place. A frontier MSSA is a rural MSSA adopted by the Commission which has a population density of less than 11 persons per square mile. Any MSSA which is not a rural or frontier MSSA is an urban MSSA. Last updated December 6th 2024.

The District boundary definitions are primarily based on the California county boundaries. The Board of Equalization (BOE) County and City Boundary web service is the authoritative source of County boundaries and this was used to digitize the district boundaries based on the data from March 2023. This data is solely for informational purposes. District 9 has been operating independent of the Central Region since November 1, 2015. Kern County remains the only split county in the state, between Districts 6 and 9 respectively. The BOE data was also used to create the district boundary layers along the coastline.