This feature class is used for cartographic purposes, for generating statistical data, and for clipping data. Ideally, state and federal agencies should be using the same framework data for common themes such as county boundaries. This layer provides an initial offering as "best available" at 1:24,000 scale for counties.Incorporated cities were merged from the Board of Equalization's 11/16/2021 City and County boundaries dataset. The Cal Fire FRAP County boundaries v 19_1 were maintained for consistency with other use in CA Nature.

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).

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.

Feature layer of the Counties in California as used by Cal OES. Columns designating CalOES Regions, Fire and Law Mutual Aid Regions, and county name.

Counties in California intended for the NEVI Map.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:Metadata is missing or incomplete for some layers at this time and will be continuously improved.We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.This dataset is continuously updated as the source data from CDTFA is updated, as often as many times a month. If you require unchanging point-in-time data, export a copy for your own use rather than using the service directly in your applications.PurposeCounty boundaries boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.Related LayersThis dataset is part of a grouping of many datasets:Cities: Only the city boundaries and attributes, without any unincorporated areasWith Coastal BuffersWithout Coastal BuffersCounties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout Coastal Buffers (this dataset)Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.With Coastal BuffersWithout Coastal BuffersPlace AbbreviationsUnincorporated Areas (Coming Soon)Census Designated Places (Coming Soon)Cartographic CoastlinePolygonLine source (Coming Soon)Working with Coastal BuffersThe dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the authoritative source data from CDTFA. In the versions where they are included, they remain as a second polygon on cities or counties that have them, with all the same identifiers, and a value in the COASTAL field indicating if it"s an ocean or a bay buffer. If you wish to have a single polygon per jurisdiction that includes the coastal buffers, you can run a Dissolve on the version that has the coastal buffers on all the fields except COASTAL, Area_SqMi, Shape_Area, and Shape_Length to get a version with the correct identifiers.Point of ContactCalifornia Department of Technology, Office of Digital Services, odsdataservices@state.ca.govField and Abbreviation DefinitionsCOPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering systemPlace Name: CDTFA incorporated (city) or county nameCounty: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information SystemGNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information SystemPlace Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area namesCNTY Abbr: CalTrans Division of Local Assistance abbreviations of county namesArea_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".AccuracyCDTFA"s source data notes the following about accuracy:City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization"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).Boundary ProcessingThese data make a structural change from the source data. While the full boundaries provided by CDTFA include coastal buffers of varying sizes, many users need boundaries to end at the shoreline of the ocean or a bay. As a result, after examining existing city and county boundary layers, these datasets provide a coastline cut generally along the ocean facing coastline. For county boundaries in northern California, the cut runs near the Golden Gate Bridge, while for cities, we cut along the bay shoreline and into the edge of the Delta at the boundaries of Solano, Contra Costa, and Sacramento counties.In the services linked above, the versions that include the coastal buffers contain them as a second (or third) polygon for the city or county, with the value in the COASTAL field set to whether it"s a bay or ocean polygon. These can be processed back into a single polygon by dissolving on all the fields you wish to keep, since the attributes, other than the COASTAL field and geometry attributes (like areas) remain the same between the polygons for this purpose.SliversIn cases where a city or county"s boundary ends near a coastline, our coastline data may cross back and forth many times while roughly paralleling the jurisdiction"s boundary, resulting in many polygon slivers. We post-process the data to remove these slivers using a city/county boundary priority algorithm. That is, when the data run parallel to each other, we discard the coastline cut and keep the CDTFA-provided boundary, even if it extends into the ocean a small amount. This processing supports consistent boundaries for Fort Bragg, Point Arena, San Francisco, Pacifica, Half Moon Bay, and Capitola, in addition to others. More information on this algorithm will be provided soon.Coastline CaveatsSome cities have buffers extending into water bodies that we do not cut at the shoreline. These include South Lake Tahoe and Folsom, which extend into neighboring lakes, and San Diego and surrounding cities that extend into San Diego Bay, which our shoreline encloses. If you have feedback on the exclusion of these items, or others, from the shoreline cuts, please reach out using the contact information above.Offline UseThis service is fully enabled for sync and export using Esri Field Maps or other similar tools. Importantly, the GlobalID field exists only to support that use case and should not be used for any other purpose (see note in field descriptions).Updates and Date of ProcessingConcurrent with CDTFA updates, approximately every two weeks, Last Processed: 12/17/2024 by Nick Santos using code path at https://github.com/CDT-ODS-DevSecOps/cdt-ods-gis-city-county/ at commit 0bf269d24464c14c9cf4f7dea876aa562984db63. It incorporates updates from CDTFA as of 12/12/2024. Future updates will include improvements to metadata and update frequency.

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of March 2025. The schema changed in February 2025 - please see below. We will post a roadmap of upcoming changes, but service URLs and schema are now stable. For deployment status of new services in February 2025, see https://gis.data.ca.gov/pages/city-and-county-boundary-data-status. Additional roadmap and status links at the bottom of this metadata.

Purpose

County boundaries along with third party identifiers used to join in external data. Boundaries are from the California Department of Tax and Fee Administration (CDTFA). These boundaries are the best available statewide data source in that CDTFA receives changes in incorporation and boundary lines from the Board of Equalization, who receives them from local jurisdictions for tax purposes. Boundary accuracy is not guaranteed, and though CDTFA works to align boundaries based on historical records and local changes, errors will exist. If you require a legal assessment of boundary location, contact a licensed surveyor.

This dataset joins in multiple attributes and identifiers from the US Census Bureau and Board on Geographic Names to facilitate adding additional third party data sources. In addition, we attach attributes of our own to ease and reduce common processing needs and questions. Finally, coastal buffers are separated into separate polygons, leaving the land-based portions of jurisdictions and coastal buffers in adjacent polygons. This layer removes the coastal buffer polygons. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers (this dataset)
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• CDTFA_COUNTY: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• CDTFA_COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system. The boundary data originate with CDTFA's teams managing tax rate information, so this field is preserved and flows into this dataset.
• CENSUS_GEOID: numeric geographic identifiers from the US Census Bureau
• CENSUS_PLACE_TYPE: City, County, or Town, stripped off the census name for identification purpose.
• GNIS_PLACE_NAME: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• CDT_COUNTY_ABBR: Abbreviations of county names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 3 characters.
• CDT_NAME_SHORT: The name of the jurisdiction (city or county) with the word "City" or "County" stripped off the end. Some changes may come to how we process this value to make it more consistent.
• AREA_SQMI: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• OFFSHORE: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• PRIMARY_DOMAIN: Currently empty/null for all records. Placeholder field for official URL of the city or county
• CENSUS_POPULATION: Currently null for all records. In the future, it will include the most recent US Census population estimate for the jurisdiction.
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

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

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 map shows cases broken down by the county level and city level in Southern California.

This line feature layer contains Legal City boundaries within Los Angeles County.

The principal attribute is BDRY_TYPE which represents the boundary feature types. Use its values below for definition queries and layer symbology for your mapping needs.

Coast - This value represents the coastline. This data is carefully maintained by DPW staff, based Los Angeles Region Imagery Acquisition Consortium data.

Land City - This value represents city boundaries on land.

Land County - This value represents the county boundary on land.

Pier - One example is the Santa Monica Pier. Man-made features may be regarded as extensions of the coastline.

Breakwater - Examples include the breakwater barriers that protect the Los Angeles Harbor.

Water - This value is used to separate features representing internal navigable waters and the ocean. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.

Ocean - This value is used to represent ocean boundaries between cities in addition to the seaward boundaries of coastal cities. Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles (a nautical mile is 1852 meters) from the coastline.

The City Official boundary extends six miles off the coast of Los Angeles County as required by the State of California official boundary for City's along the coast. The City Boundary provided here supports map cartography is the traditional view of Long Beach that highlights the Port of Long Beach and shore line. This is not the official City Limits and is commonly used to support map products for the Harbor and beach communities.

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.

This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax areas and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the California State Board of Equalization'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).

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

This map presents a tour of the City of Redlands, California using the detailed map of Redlands included in the community basemap. The City of Redlands is located in Southern California, about 65 miles east of Los Angeles. The map tour highlights some of the unique features in the history of Redlands as well as several of the places and events that make it a very livable community today.The map features a detailed basemap for the City of Redlands, California, including buildings, parcels, vegetation, land use, landmarks, streets, and more. The map features special detail for areas of high interest within the City, including local parks, landmarks, and the ESRI campus.The map references detailed GIS data provided by the City of Redlands, Department of Innovation and Technology, GIS Division. The map was authored using map templates available from ESRI, including:Topographic Map Template - Large ScalesCampus Basemap TemplateThe map was published as part of ESRI's Community Maps Program and is one of several detailed maps of cities and counties in the World Topographic Map.