The "Map Imager Layer - Administrative Boundaries" is a Map Image Layer of Administrative Boundaries. It has been designed specifically for use in ArcGIS Online (and will not directly work in ArcMap or ArcPro). This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.The Administrative Boundaries Data Group contains the following layers: Populated Places (USGS)US Census Urbanized Areas and Urban Clusters (USCB)US Census Minor Civil Divisions (USCB)PLSS Townships (MnDNR, MnGeo)Counties (USCB)American Indian, Alaska Native, Native Hawaiian (AIANNH) Areas (USCB)States (USCB)Countries (MPCA)These datasets have not been optimized for fast display (but rather they maintain their original shape/precision), therefore it is recommend that filtering is used to show only the features of interest. For more information about using filters please see "Work with map layers: Apply Filters": https://doc.arcgis.com/en/arcgis-online/create-maps/apply-filters.htmFor additional information about the Administrative Boundary Dataset please see:United States Census Bureau TIGER/Line Shapefiles and TIGER/Line Files Technical Documentation: https://www.census.gov/programs-surveys/geography/technical-documentation/complete-technical-documentation/tiger-geo-line.htmlUnited States Census Bureau Census Mapping Files: https://www.census.gov/geographies/mapping-files.htmlUnited States Census Bureau TIGER/Line Shapefiles: https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html and https://www.census.gov/cgi-bin/geo/shapefiles/index.php

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.

Purpose

County and incorporated place (city) 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. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. 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, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. 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
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 (this dataset)
   • Without Coastal Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
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

• 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
• Place Name: CDTFA incorporated (city) or county name
• 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.
• Legal 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.
• 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 System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_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".
• 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.

Accuracy

CDTFA"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

This layer contains information for locating past and present legal city boundaries within Los Angeles County. The Los Angeles County Department of Public Works provides the most current shapefiles representing city annexations and city boundaries on the Los Angeles County GIS Data Portal. True, legal boundaries are only determined on the ground by surveyors licensed in the State of California. Numerous records are freely available at the Land Records Information website, hosted by the Department of Public Works.Principal Attributes:NO: The row number in the attribute table of the PDF Annexation Maps. (See Below)

ANNEX_No: These values are only used for the City of Los Angeles and Long Beach.

NAME: The official annexation name.

TYPE: Indicates the legal action.

A - represents an Annexation to that city. D - represents a Detachment from that city. V - is used to indicate the annexation was void or withdrawn before an effective date could be declared. 33 - Some older city annexation maps indicate a city boundary declared 'as of February 8, 1933'.

ANNEX_AREA: is the land area annexed or detached, in square miles, per the recorded legal description.

TOTAL_AREA: is the cumulative total land area for each city, arranged chronologically.

SHADE: is used by some of our cartographers to store the color used on printed maps.

INDEXNO: is a matching field used for retrieving documents from our department's document management system.

STATE (Secretary of State): Date filed with the Secretary of State. These are not available for earlier annexations and are Null.

COUNTY (County Recorder): Date filed with the County Recorder. These are not available for earlier annexations and are Null.

EFFECTIVE (Effective Date): The effective date of the annexation or detachment.

CITY: The city to which the annexation or detachment took place.

URL: This text field contains hyperlinks for viewing city annexation documents. See the ArcGIS Help for using the Hyperlink Tool.

FEAT_TYPE: contains the type of feature each polygon represents:

Land - Use this value for your definition query if you want to see only land features on your map. Pier - This value is used for polygons representing piers along the coastline. One example is the Santa Monica Pier. Breakwater - This value is used for polygons representing man-made barriers that protect the harbors. Water - This value is used for polygons representing navigable waters inside the harbors and marinas. 3NM Buffer - Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles from the coastline. (A nautical mile is 1,852 meters, or about 6,076 feet.) Annexation Maps by City (PDF)Large format, high quality wall maps are available for each of the 88 cities in Los Angeles County in PDF format.Agoura HillsHermosa BeachNorwalkAlhambraHidden HillsPalmdaleArcadiaHuntington ParkPalos Verdes EstatesArtesiaIndustryParamountAvalonInglewoodPasadenaAzusaIrwindalePico RiveraBaldwin ParkLa Canada FlintridgePomonaBellLa Habra HeightsRancho Palos VerdesBell GardensLa MiradaRedondo BeachBellflowerLa PuenteRolling HillsBeverly HillsLa VerneRolling Hills EstatesBradburyLakewoodRosemeadBurbankLancasterSan DimasCalabasasLawndaleSan FernandoCarsonLomitaSan GabrielCerritosLong BeachSan MarinoClaremontLos Angeles IndexSanta ClaritaCommerceLos Angeles Map 1Santa Fe SpringsComptonLos Angeles Map 2Santa MonicaCovinaLos Angeles Map 3Sierra MadreCudahyLos Angeles Map 4Signal HillCulver CityLos Angeles Map 5South El MonteDiamond BarLos Angeles Map 6South GateDowneyLos Angeles Map 7South PasadenaDuarteLos Angeles Map 8Temple CityEl MonteLynwoodTorranceEl SegundoMalibuVernonGardenaManhattan BeachWalnutGlendaleMaywoodWest CovinaGlendoraMonroviaWest HollywoodHawaiian GardensMontebelloWestlake VillageHawthorneMonterey ParkWhittier

This web map created by the Colorado Governor's Office of Information Technology GIS team, serves as a basemap specific to the state of Colorado. The basemap includes general layers such as counties, municipalities, roads, waterbodies, state parks, national forests, national wilderness areas, and trails.Layers:Layer descriptions and sources can be found below. Layers have been modified to only represent features within Colorado and are not up to date. Layers last updated February 23, 2023. Colorado State Extent: Description: “This layer provides generalized boundaries for the 50 States and the District of Columbia.” Notes: This layer was filtered to only include the State of ColoradoSource: Esri Living Atlas USA States Generalized Boundaries Feature LayerState Wildlife Areas:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state wildlife areas layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer hosted in ArcGIS Online Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerMunicipal Boundaries:Description: "Boundaries data from the State Demography Office of Colorado Municipalities provided by the Department of Local Affairs (DOLA)"Source: Colorado Information Marketplace Municipal Boundaries in ColoradoCounties:Description: “This layer presents the USA 2020 Census County (or County Equivalent) boundaries of the United States in the 50 states and the District of Columbia. It is updated annually as County (or County Equivalent) boundaries change. The geography is sources from US Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrology to add a detailed coastline for cartographic purposes. Geography last updated May 2022.” Notes: This layer was filtered to only include counties in the State of ColoradoSource: Esri USA Census Counties Feature LayerInterstates:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: Interstates are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointU.S. Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: U.S. Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointState Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: State Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointMajor Roads:Description: Authoritative data from the Colorado Department of Transportation representing major roads Source: Colorado Department of Transportation Major Roads REST EndpointLocal Roads:Description: Authoritative data from the Colorado Department of Transportation representing local roads Source: Colorado Department of Transportation Local Roads REST EndpointRail Lines:Description: Authoritative data from the Colorado Department of Transportation representing rail lines Source: Colorado Department of Transportation Rail Lines REST EndpointCOTREX Trails:Description: “The Colorado Trail System, now titled the Colorado Trail Explorer (COTREX), endeavors to map every trail in the state of Colorado. Currently their are nearly 40,000 miles of trails mapped. Trails come from a variety of sources (USFS, BLM, local parks & recreation departments, local governments). Responsibility for accuracy of the data rests with the source.These data were last updated on 2/5/2019” Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerNHD Waterbodies:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include waterbodies in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerNHD Flowlines:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include flowline features in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerState Parks:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state parks layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerDenver Parks:Description: "This dataset should be used as a reference to locate parks, golf courses, and recreation centers managed by the Department of Parks and Recreation in the City and County of Denver. Data is based on parcel ownership and does not include other areas maintained by the department such as medians and parkways. The data should be used for planning and design purposes and cartographic purposes only."Source: City and County of Denver Parks REST EndpointNational Wilderness Areas:Description: “A parcel of Forest Service land congressionally designated as wilderness such as National Wilderness Area.”Notes: This layer was filtered to only include National Wilderness Areas in the State of ColoradoSource: United States Department of Agriculture National Wilderness Areas REST EndpointNational Forests: Description: “A depiction of the boundaries encompassing the National Forest System (NFS) lands within the original proclaimed National Forests, along with subsequent Executive Orders, Proclamations, Public Laws, Public Land Orders, Secretary of Agriculture Orders, and Secretary of Interior Orders creating modifications thereto, along with lands added to the NFS which have taken on the status of 'reserved from the public domain' under the General Exchange Act. The following area types are included: National Forest, Experimental Area, Experimental Forest, Experimental Range, Land Utilization Project, National Grassland, Purchase Unit, and Special Management Area.”Notes: This layer was filtered to only include National Forests in the State of ColoradoSource: United States Department of Agriculture Original Proclaimed National Forests REST Endpoint

The "Map Image Layer - Watershed Boundaries" is the Map Image Layer of Watershed Boundaries. It has been designed specifically for use in ArcGIS Online (and will not directly work in ArcMap or ArcPro). This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.The Watershed Boundaries Data Group contains the following layers: DNR Catchments (MnDNR)HUC 12 Boundaries (USGS)HUC 12 IWM Group Boundaries (MPCA)HUC 10 Boundaries (USGS)HUC 8 Boundaries (USGS): HUC 8s represent part or all of a surface drainage basin, a combination of drainage basins, or a distinct hydrologic feature. There are 80 HUC 2s in Minnesota. (i.e. Zumbro (07040004))HUC 6 Boundaries (USGS): HUC 6s are areas which divide the subregions into more than 350 hydrologic accounting units. Minnesota has 17 of the nations hydrologic accounting units: Northwestern Lake Superior (040101), St. Louis (040102), Southwestern Lake Superior (040103), Mississippi Headwaters (070101), Upper Mississippi-Crow-Rum (070102), Minnesota (070200), St. Croix (070300), Upper Mississippi-Black-Root (070400), Upper Mississippi-Maquoketa-Plum (070600), Upper Mississippi-Skunk-Wapsipinicon (070801), Iowa (070802), Des Moines (071000), Upper Red (090201), Lower Red (090203), Rainy (090300), Big Sioux (101702), Missouri-Little Sioux (102300).HUC 4 Boundaries (USGS): HUC 4s are geographic subregions which are drained by a river system, a reach of river and its tributaries in that reach, a closed basin, or a group of streams forming a coastal drainage areas. Minnesota has 12 of the nations 222 subregions: Western Lake Superior (0401), Mississippi Headwaters (0701), Minnesota (0702), St. Croix (0703), Upper Mississippi-Black-Root (0704), Upper Mississippi-Maquoketa-Plum (0706), Upper Mississippi-Iowa-Skunk-Wapsipinicon (0708), Des Moines (0710), Red (0902), Rainy (0903), Missouri-Big Sioux (1017), Missouri-Little Sioux (1023).HUC 2 Boundaries (USGS): HUC 2s are geographic regions which contain the drainage of a major river or a series of rivers. Minnesota has 4 of the nations 21 regions: Great Lakes (R04), Upper Mississippi (R07), Souris-Red-Rainy (R09), and Missouri (R10).These datasets have not been optimized for fast display (but rather they maintain their original shape/precision), therefore it is recommend that filtering is used to show only the features of interest. For more information about using filters please see "Work with map layers: Apply Filters": https://doc.arcgis.com/en/arcgis-online/create-maps/apply-filters.htmFor additional information about the Watershed Boundary Dataset please see:United States Geological Survey Water-Supply Paper 2294: https://pubs.usgs.gov/wsp/wsp2294/Hydrologic Units, The National Atlas of the United State of America: https://pubs.usgs.gov/gip/hydrologic_units/pdf/hydrologic_units.pdfNational Hydrography Dataset, Watershed Boundary Dataset: https://www.usgs.gov/core-science-systems/ngp/national-hydrography/watershed-boundary-dataset

This layer contains Legal City boundaries within Los Angeles County. The Los Angeles County Department of Public Works provides the most current shape file of these city boundaries for download at its Spatial Information Library.Note: This boundary layer will not line up with the Thomas Brothers city layer. Principal attributes include:CITY_NAME: represents the city's name.CITY_TYPE: may be used for definition queries; "Unincorporated" or "City".FEAT_TYPE: contains the type of feature each polygon represents:Land - Use this value for your definition query if you want to see only land features on your map.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 - Polygons with this attribute value represent internal navigable waters. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.3NM Buffer - 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.

Note: 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 beginning 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, gis@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.

This layer shows language group of language spoken at home by age. Data is from US Census American Community Survey (ACS) 5-year estimates.This layer is symbolized to show the percentage of the population age 5+ who speak Spanish at home. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. To view only the census tracts that are predominantly in Tempe, add the expression City is Tempe in the map filter settings.A ‘Null’ entry in the estimate indicates that data for this geographic area cannot be displayed because the number of sample cases is too small (per the U.S. Census).Vintage: 2017-2021ACS Table(s): B16007 (Not all lines of these ACS tables are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Data Preparation: Data curated from Esri Living Atlas clipped to Census Tract boundaries that are within or adjacent to the City of Tempe boundaryDate of Census update: December 8, 2022National Figures: data.census.govAdditional Census data notes and data processing notes are available at the Esri Living Atlas Layer:https://tempegov.maps.arcgis.com/home/item.html?id=527ea2b5ba814c8ca1c34a2945e1b751

This layer contains Legal City boundaries within Los Angeles County. The Landbase is jointly maintained by the Los Angeles County Assessor and the Los Angeles County Department of Public Works.The Los Angeles County Department of Public Works provides the most current shape file of these city boundaries for download at its https://egis-lacounty.hub.arcgis.com/datasets/la-county-city-boundaries/explore?location=34.153321%2C-118.083123%2C9.49.Note: This boundary layer will not line up with the Thomas Brothers® city layer.Principal attributes include:CITY_NAME: represents the city's name.CITY_TYPE: may be used for definition queries; "Unincorporated" or "City".FEAT_TYPE: contains the type of feature each polygon represents:Land - Use this value for your definition query if you want to see only land features on your map.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 - Polygons with this attribute value represent internal navigable waters. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.3NM Buffer - 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 coastlineURL: cities website current as of 01/01/2023This product is for information purposes and should not be used for legal, engineering, or survey purposes. County assumes no liability for any errors or omissions.

Note: 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 beginning 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.This dataset is regularly 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 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 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 Buffers (this dataset)Without Coastal BuffersCities 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 BuffersCity and County AbbreviationsUnincorporated Areas (Coming Soon)Census Designated PlacesCartographic CoastlinePolygonLine source (Coming Soon)State BoundaryWith Bay CutsWithout Bay Cuts Working with Coastal Buffers The dataset you are currently viewing includes the coastal buffers for cities and counties that have them in the 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 OFFSHORE and AREA_SQMI to get a version with the correct identifiers. Point of ContactCalifornia Department of Technology, Office of Digital Services, gis@state.ca.gov Field and Abbreviation DefinitionsCDTFA_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 BureauCENSUS_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 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.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 countyCENSUS_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. Boundary AccuracyCounty boundaries were originally derived from a 1:24,000 accuracy dataset, with improvements made in some places to boundary alignments based on research into historical records and boundary changes as CDTFA learns of them. City boundary data are derived from pre-GIS tax maps, digitized at BOE and CDTFA, with adjustments made directly in GIS for new annexations, detachments, and corrections.Boundary accuracy within the dataset varies. While CDTFA strives to correctly include or exclude parcels from jurisdictions for accurate tax assessment, this dataset does not guarantee that a parcel is placed in the correct jurisdiction. When a parcel is in the correct jurisdiction, this dataset cannot guarantee accurate placement of boundary lines within or between parcels or rights of way. This dataset also provides no information on parcel boundaries. For exact jurisdictional or parcel boundary locations, please consult the county assessor's office and a licensed surveyor. CDTFA's data is used as the best available source because BOE and CDTFA receive information about changes in jurisdictions which otherwise need to be collected independently by an agency or company to compile into usable map boundaries. CDTFA maintains the best available statewide boundary information. CDTFA'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. 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

The Asset Polygons layer shows the location of park assets by type captured as polygons shapes.  Park assets are features and/or objects found within or near a park boundary. Some assets serve as park attractions and amenities such as soccer fields and basketball courts. The layer comprises of assets that are external and not easily moved. This Asset Polygons layer pulls from individual asset layers and integrates with information in EAM to provide a comprehensive dataset. Assets will only show up in this layer if the asset source layer contains the correct GIS ID with a match in EAM. A list of these layers is below:Athletic Fields layer - contains athletic fields such as baseball, soccer, etc.Bike & Skate Parks layer - contains bike parks and skate parks.Community Gardens layer - contains community gardens.Court Pads layer - contains court pads, which are the underlying contiguous court surfaces like asphalt for a set of basketball courts or sand for a volleyball court.Courts layer - contains the various the variously sported courts spanning basketball to handball to pickleball and more.Dog Parks layer - contains dog parks.Meadows layer - contains meadows.Playgrounds layer - contains playgrounds (category = "PLAYGROUND PAD").Picnic Shelters layer - contains both permitted and non-permitted shelters.Reforestation Sites layer - contains reforestation sites. NotesIf you need assets represented as points instead, refer to the Asset Points layer, which contains these same polygon assets as points plus other every other asset.Contact the Data Analytics Section of Montgomery Parks for more information via email: dataanalytics@montgomeryparks.org. Update CycleLayer is updated every Monday and Thursday morning on an automated basis. The Analytics Team programs the Azure cloud to source data from the assorted layers representing assets that Montgomery Parks has in both its EAM & GIS systems and ArcGIS Data Pipelines pulls said data back into this layer on an automated basis. Not all asset layers are incorporated but they eventually will be. Explore the Categories and Source Layers available in the layer to discover which are currently available. BenefitsStreamline assets for GIS - A unified asset layer simplifies mapping and analysis by reducing the need to manage multiple layers. This is especially beneficial for divisions and teams frequently engaged in GIS, improving workflow efficiency and productivity.Foundational for Key Applications - The comprehensive asset layers serve as core data for various mapping applications, supporting decision-making and enhancing public engagement across multiple platforms.Integrated Data and Reduced Silos - By integrating data from multiple sources, the asset layers provide users with more comprehensive insights, minimizing the confusion of dealing with scattered data across systems. This leads to faster analysis and better decision-making.Broader Access and Flexibility - While detailed layers are maintained by specific teams, the comprehensive asset layer allows for broader access across divisions and the public. This makes asset data more readily available and usable for a wide range of stakeholders, promoting transparency and efficiency.

This feature service is derived from the Esri "United States Zip Code Boundaries" layer, queried to only CA data.For the original data see: https://esri.maps.arcgis.com/home/item.html?id=5f31109b46d541da86119bd4cf213848Published by the California Department of Technology Geographic Information Services Team.The GIS Team can be reached at ODSdataservices@state.ca.gov.U.S. ZIP Code Boundaries 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 (or equivalent areas) 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 (SCF) or a mail processing facility area. The fourth and fifth digits identify a post office, station, branch or local delivery area.As of the time this layer was published, in January 2025, Esri's boundaries are sourced from TomTom (June 2024) and the 2023 population estimates are from Esri Demographics. Esri updates its layer annually and those changes will immediately be reflected in this layer. Note that, because this layer passes through Esri's data, if you want to know the true date of the underlying data, click through to Esri's original source data and look at their metadata for more information on updates.Cautions about using Zip Code boundary dataZip code boundaries have three characteristics you should be aware of before using them:Zip code boundaries change, in ways small and large - these are not a stable analysis unit. Data you received keyed to zip codes may have used an earlier and very different boundary for your zip codes of interest.Historically, the United States Postal Service has not published zip code boundaries, and instead, boundary datasets are compiled by third party vendors from address data. That means that the boundary data are not authoritative, and any data you have keyed to zip codes may use a different, vendor-specific method for generating boundaries from the data here.Zip codes are designed to optimize mail delivery, not social, environmental, or demographic characteristics. Analysis using zip codes is subject to create issues with the Modifiable Areal Unit Problem that will bias any results because your units of analysis aren't designed for the data being studied.As of early 2025, USPS appears to be in the process of releasing boundaries, which will at least provide an authoritative source, but because of the other factors above, we do not recommend these boundaries for many use cases. If you are using these for anything other than mailing purposes, we recommend reconsideration. We provide the boundaries as a convenience, knowing people are looking for them, in order to ensure that up-to-date boundaries are available.

This file is based on the Mapping and Boundary Branch's Official Protraction Diagram (OPD)and Leasing Maps (LM). Each offshore area is defined by an API Number corresponding to those in the API Bulletin Number D12A. OPDs are numbered using the United Nations International Map of the World Numbering System, and are generally named for land or hydrographic features contained within the limits of the diagram. This data set contains Official Protraction Diagram (OPD) and Leasing Map (LM) outlines in ESRI shape file formats for the BOEM Gulf of Mexico Region. The use of OPDs and LMs makes it easier to refer to individual blocks within a region or planning area. These diagrams were clipped along the Submerged Lands Act (SLA) boundary and along lines contained in the Continental Shelf Boundaries (CSB) GIS data files to show only those blocks or portions thereof within federal jurisdiction. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are NOT an OFFICIAL record for the exact OPD boundaries. Only the paper OPD or a digital image of them serves as OFFICIAL records.Official Protraction Diagrams and other cadastre information the BOEM produces are generated in accordance with 30 Code of Federal Regulations (CFR) Part 556.8 Subpart A, (formerly Part 256.8 Subpart A (2010)) to support Federal land ownership and mineral resource management. Further information on the SLA and development of this line from baseline points can be found in OCS Report BOEM 99-0006: Boundary Development on the Outer Continental Shelf. https://www.boem.gov/BOEM-Newsroom/Library/Publications/1999/99-0006-pdf.aspx Because GIS projection and topology functions can change or generalize coordinates, and because shapefiles cannot represent true arcs, these GIS files are considered to be approximate and are NOT an OFFICIAL record for the exact block coordinates or areas. The Official Protraction Diagrams (OPDs)and Leasing Maps (LMs) and Supplemental Official Block Diagrams (SOBDs) serve as the legal definition for BOEM offshore boundary coordinates and area descriptions and can be found at the following location: https://www.boem.gov/Official-Protraction-Diagrams/. Contains the protraction polygons clipped on the fedstate (SLA-Boundary) as of March 15, 2013. Used ArcCatalog to create shape files.

This layer shows poverty status by age group. Data is from US Census American Community Survey (ACS) 5-year estimates.This layer is symbolized to show the percentage of the population whose income falls below the Federal poverty line. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). To view only the census tracts that are predominantly in Tempe, add the expression City is Tempe in the map filter settings.A ‘Null’ entry in the estimate indicates that data for this geographic area cannot be displayed because the number of sample cases is too small (per the U.S. Census).Vintage: 2017-2021ACS Table(s): B17020 (Not all lines of these ACS tables are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Data Preparation: Data curated from Esri Living Atlas clipped to Census Tract boundaries that are within or adjacent to the City of Tempe boundaryDate of Census update: December 8, 2022National Figures: data.census.govAdditional Census data notes and data processing notes are available at the Esri Living Atlas Layer:https://tempegov.maps.arcgis.com/home/item.html?id=0e468b75bca545ee8dc4b039cbb5aff6 (Esri's Living Atlas always shows latest data)

This parcels polygons feature class represents current city parcels within the City of Los Angeles. It shares topology with the Landbase parcel lines feature class. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way, ownership and land record information. The legal boundaries are determined on the ground by license surveyors in the State of California, and by recorded documents from the Los Angeles County Recorder's office and the City Clerk's office of the City of Los Angeles. Parcel and ownership information are available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the landbase parcels is entered into attributes. Principal attributes include:PIN and PIND: represents the unique auto-generated parcel identifier and key to related features and tables. This field is related to the LA_LEGAL, LA_APN and LA_HSE_NBR tables. PIN contains spaces and PIND replaces those spaces with a dash (-).LA_LEGAL - Table attributes containing legal description. Principal attributes include the following:TRACT: The subdivision tract number as recorded by the County of Los AngelesMAP_REF: Identifies the subdivision map book reference as recorded by the County of Los Angeles.LOT: The subdivision lot number as recorded by the County of Los Angeles.ENG_DIST: The four engineering Districts (W=Westla, C=Central, V= Valley and H=Harbor).CNCL_DIST: Council Districts 1-15 of the City of Los Angeles. OUTLA means parcel is outside the City.LA_APN- Table attributes containing County of Los Angeles Assessors information. Principal attributes include the following:BPP: The Book, Page and Parcel from the Los Angeles County Assessors office. SITUS*: Address for the property.LA_HSE_NBR - Table attributes containing housenumber information. Principal attributes include the following:HSE_ID: Unique id of each housenumber record.HSE_NBR: housenumber numerical valueSTR_*: Official housenumber addressFor a complete list of attribute values, please refer to Landbase_parcel_polygons_data_dictionary.Landbase parcels polygons data layer was created in geographical information systems (GIS) software to display the location of the right of way. The parcels polygons layer delineates the right of way from Landbase parcels lots. The parcels polygons layer is a feature class in the LACityLandbaseData.gdb Geodatabase dataset. The layer consists of spatial data as a polygon feature class and attribute data for the features. The area inside a polygon feature is a parcel lot. The area outside of the parcel polygon feature is the right of way. Several polygon features are adjacent, sharing one line between two polygons. For each parcel, there is a unique identifier in the PIND and PIN fields. The only difference is PIND has a dash and PIN does not. The types of edits include new subdivisions and lot cuts. Associated legal information about the landbase parcels lots is entered into attributes. The landbase parcels layer is vital to other City of LA Departments, by supporting property and land record operations and identifying legal information for City of Los Angeles. The landbase parcels polygons are inherited from a database originally created by the City's Survey and Mapping Division. Parcel information should only be added to the Landbase Parcels layer if documentation exists, such as a Deed or a Plan approved by the City Council. When seeking the definitive description of real property, consult the recorded Deed or Plan.List of Fields:ID: A unique numeric identifier of the polygon. The ID value is the last part of the PIN field value.ASSETID: User-defined feature autonumber.MAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral grid index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers. An A-map is the smallest grid in the index map and is used when there is a large amount of spatial information in the map display. There are more parcel lines and annotation than can fit in the B-map, and thus, an A-map is used. There are 4 A-maps in a B-map. In areas where parcel lines and annotation can fit comfortably in an index map, a B-map is used. The B-maps are at a scale of 100 feet, and A-maps are at a scale of 50 feet.OBJECTID: Internal feature number.BPPMAP_REFTRACTBLOCKMODLOTARBCNCL_DIST: LA City Council District. Values: • (numbers 1-15) - Current City Council Member for that District can be found on the mapping website http://navigatela.lacity.org/navigatela, click Council Districts layer name, under Boundaries layer group.SHAPE: Feature geometry.BOOKPAGEPARCELPIND: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. The D in the field name PIND, means "dash", and there is a dash between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District. • W - West LA Engineering District.PIN: The value is a combination of MAPSHEET and ID fields, creating a unique value for each parcel. There are spaces between the MAPSHEET and ID field values. This is a key attribute of the LANDBASE data layer. This field is related to the APN and HSE_NBR tables.

This shapefile contains the zoning district boundaries for the Town of Newfane, Vt., and is to be used in conjunction with other GIS data for mapping. Most of these boundaries coincide with either existing parcel lines or with roads and streams. In this shapefile, the district boundaries were made to coincide with GIS representations of roads and streams where the proposed zoning district boundaries coincide with such features, but not parcel lines. No GIS parcel data for Newfane existed at the time of this shapefile was created, so scans of paper tax maps developed on an unrectified photo base were used. The zoning district boundaries that coincide with parcel boundaries are only approximate. The zoning district boundaries, where they coincide with roads or streams are accurate to the acccuracy of the GIS data representation of those features, but where district boundaries coincide with parcel boundaries, the district boundaries will likely be off by 200 to 500 feet, or more in some areas. As such, these data should be used only in map form to give a general overally impression of the zoning district boundaries for the Town of Newfane, but cannot be used to determine actual zoning district boundaries in any locations other than where these districts coincide with roads or streams. The shapefile Newfane\zoning_prop_taxmap.shp has been created to show the relationship with zoning district boundaries and parcel lines as represented on a series of scanned tax map images. For a more accurate depiction of the Village zoning districts (Newfane, South Newfane, and Williamsville) in relation to the scanned tax map images, see the shapefile Newfane\zoning_prop_village.shp.Data were created in September 2008 but are current to the most recent zoning bylaw amendment of February 19, 2015.

This layer shows population broken down by race and Hispanic origin. Data is from US Census American Community Survey (ACS) 5-year estimates.This layer is symbolized to show the percent of population that is Hispanic or Latino. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). To view only the census tracts that are predominantly in Tempe, add the expression City is Tempe in the map filter settings.A ‘Null’ entry in the estimate indicates that data for this geographic area cannot be displayed because the number of sample cases is too small (per the U.S. Census).Vintage: 2018-2022ACS Table(s): B03002 (Not all lines of this ACS table are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community SurveyData Preparation: Data curated from Esri Living Atlas clipped to Census Tract boundaries that are within or adjacent to the City of Tempe boundaryDate of Census update: December 15, 2023National Figures: data.census.gov

The Digital Bedrock Geologic-GIS Map of Marsh-Billings-Rockefeller National Historical Park and the Town Boundary of Woodstock, Vermont is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (mabi_bedrock_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (mabi_bedrock_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (mabi_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (mabi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (mabi_bedrock_geology_metadata_faq.pdf). Please read the mabi_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Vermont Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (mabi_bedrock_geology_metadata.txt or mabi_bedrock_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual _location as presented by this dataset. Users of this data should thus not assume the _location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

This layer shows population broken down by race and Hispanic origin. Data is from US Census American Community Survey (ACS) 5-year estimates.This layer is symbolized to show the percent of population that is Hispanic or Latino. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). To view only the census tracts that are predominantly in Tempe, add the expression City is Tempe in the map filter settings.A ‘Null’ entry in the estimate indicates that data for this geographic area cannot be displayed because the number of sample cases is too small (per the U.S. Census).Vintage: 2016-2020ACS Table(s): B03002 (Not all lines of this ACS table are available in this feature layer.)Data downloaded from: Census Bureau's API for American Community Survey Data Preparation: Data curated from Esri Living Atlas clipped to Census Tract boundaries that are within or adjacent to the City of Tempe boundaryDate of Census update: March 17, 2022National Figures: data.census.govAdditional Census data notes and data processing notes are available at the Esri Living Atlas Layer:https://tempegov.maps.arcgis.com/home/item.html?id=23ab8028f1784de4b0810104cd5d1c8f&view=list&sortOrder=desc&sortField=defaultFSOrder#overview(Esri's Living Atlas always shows latest data)

This map layer portrays the State boundaries of the United States, Puerto Rico, and the U.S. Virgin Islands. The map layer was created by extracting county polygon features from the CENSUS 2006 TIGER/Line files produced by the U.S. Census Bureau. These files were then merged into a single file and county boundaries within States were removed. This is a revised version of the July 2012 map layer.The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).