This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.

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

Orange County City Boundaries.

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.

Polygon vector map data covering city boundaries for Chicago, Illinois, containing 1 feature.

Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features..

This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.

Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.

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

​

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. Purpose City 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 Buffers (this dataset)Counties: Full county boundaries and attributes, including all cities within as a single polygonWith Coastal BuffersWithout 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) 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, odsdataservices@state.ca.gov Field and Abbreviation DefinitionsCDTFA_CITY: CDTFA incorporated city nameCDTFA_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_CITY_ABBR: Abbreviations of incorporated area names - originally derived from CalTrans Division of Local Assistance and now managed by CDT. Abbreviations are 4 characters. Not present in the county-specific layers.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

Pittsburgh City Boundary

Boundary lines and associated attributes for incorporated cities in the Commonwealth of Kentucky.

8/04/2025 - Updates to Mandan and Thompson. 4/25/2025 - Updates to Ellendale, Fargo, Kindred, Lincoln, Mandan, Rugby and Tappen.12/06/2024 - Update to Lincoln and Bismarck Corporate Boundaries based on requests from Lincoln.6/27/2024 - Update to the Valley City and Dickinson Corporate Boundary based on requests from their GIS personal.4/8/2024 - Update to the Valley City Corporate Boundary12/04/2023 - Update to Fargo City Boundary7/23/2023 - Removed Church’s Ferry due to proclamation and notice of dissolution.7/01/2023 - Changes to Binford - Ordinance 51; Lidgerwood - Ordinance 2022-1; Killdeer Golf Course annexation; Bismarck based on current City of Bismarck GIS boundary9/26/2022 - Changes to Steele boundary per Kidder County 911 coordinator.9/23/2022 - Updates to Grand Forks, Mandan and Fargo7/01/2022 - Updates to Killdeer, Mandan and Williston per State Tax Dept changes. 2/14/2022- Updates to Minot -13th ST SE/31st AVE SE, Updates to Elgin, Horace and St. John.11/16/2021 -Updates to Bismarck, Fargo and Killdeer based on city ordinances.7/2/21 – Changes were made to the City of Bismarck, Fargo and Hillsboro to include local taxing jurisdiction boundary changes from the State Tax Commissioner.5/4/21 - Updates were made to the City of Wahpeton due to an annexation.4/29/21 - Updated Minot and Makoti3/5/21 - Updated an annexation to Arnegard that was submitted to the DOT by Mackenzie's County Public Works GIS Coordinator.1/21/21 - Update to Sentinel Butte per Golden Valley 911 Coordinator7/17/20 - Updates to Bismarck, Linton and Stanley6/1/20 - Updates to Killdeer, New Town and Surrey1/17/2020 - Boundary changes have been updated for Bismarck, Bowman Fargo, Garrison, Linton, and New Salem.3/5/19 - The corporate boundary of Surrey has been updated.12/26/18 - The following corporate boundaries have been updated: Bismarck, Lincoln, Grand Forks, Horace, Casselton, Fargo, Oxbow, Tioga and Stanley.6/19/18 - City of Maza is not incorporated based on the 2011-2013 North Dakota Blue book. Removed Maza.5/14/18 - Updated Dickinson, Watford City, Berthold, Minnewauken, and Cavalier.1/31/18 - Updated Dickinson, Mandan, Minot, Tioga, Devils Lake, Belfield, Washburn, Mohall, Minnewauken, Lincoln, Bismarck and Casselton. 10/24/17 - Updated Watford City and Makoti10/16/17 - The following cities have been updated: Jamestown, Milnor, Bismarck, Carrington, Casselton, Mandan, Minot, Stanley, Larimore, Crosby, and Watford City.1/10/17 - The following cities have been updated: Lehr, Grand Forks, Langdon, Drayton, Flasher, Glen Ullin, Watford City, Zap, Lignite, Hankinson, Beach, Underwood, South Heart, Devils Lake, all cities in Ward County, Cavalier, Bismarck, Lincoln, Fargo, West Fargo, Ayr, Briarwood, Casselton, Davenport, Enderlin, Grandin, Horace, and North River.9/19/16 - Updated the following cities: Watford City, Steele, Richardton, Berthold, Carpio, Burlington, Des Lacs, Donnybrook, Douglas, Kenmare, Makoti, Ryder, Sawyer, and Surrey.6/23/16 - Updated cities are as follows: All cities in Pembina, Morton, Richland, and Williams Counties. The cities of Bismarck, West Fargo, Harwood, Oxbow, Beach, Minot, Stanley, Jamestown, Fargo, Dickinson and New Town.9/28/15 - The following cites have had annexation: Stanley, Bottineau, Minot, Casselton, Belfield and Watford City.7/24/15 - Updated Grafton, Stanley, Bismarck, Williston, Horace, Fargo, Grand Forks, Watford City, Turtle Lake, Leeds, Maxbass and Medora1/16/15 - Updated Grafton, Stanley and Bismarck.11/3/2014 - Updated Bismarck, Mandan, Minot, Stanley, and Watford City7/16/14 - Corporate limits updated include: Mandan, Towner, Fargo, West Fargo, Grand Forks, Bismarck, Bowman, Watford City, Stanley, Tioga, Kenmare, Casselton, Minot, Carrington, Kindred, and Killdeer. The corporate limit updates consisted of receiving from the cities, shape files, CADD files, scanned images of annexations or by converting pdf files into images, rectifying them within ArcGIS, then heads-up digitizing. 7/29/13 - updated Stanley, Williston, Minot, and Bismarck.4/30/13 - updated Williston, Hazen, Minot, Dickinson, Valley City, Velva, Rugby, Bismarck, and Lincoln1/28/13 - updated Valley City, Grand Forks, Bismarck, Williston, Jamestown, Harvey, Mohall, Park River, Ray, Rugby, Stanley, Tioga, Mayville and Glenfield10/9/12 - updated Williston and Dickinson6/20/12 - updated Williston via shapefile from city.3/20/12 - updated Bismarck and Minot10/3/2011 - Edited corporate limits for Bottineau, Grand Forks, Bismarck, Grafton, Fargo, West Fargo, Horace, Dickinson, Williston, Valley City and Devils Lake.2/4/11 - Removed urban areas so only corporate boundaries remain. Removed boolean field named URBAN_AREA. Updated corporate limist in Dickinson and cities with Cass county. 6/24/10 - Stanley, Lincoln, Oakes, Hankinson, Enderlin, Ellendale, Linton, Carrington, Minot, and Kulm corportate limits were changed 6/18/09 - Stanley, Wahpeton, Center, Watford City, Williston, Grand Forks, Killdeer, Beulah, Beach, Hazen, Garrison, Washburn, Bismarck and Lincoln corporate limits were changed 3/24/08 - Added Milton, Drayton, and Cavalier Boudaries updated: Park River 1/16/08 - Boundaries updated: Devils Lake, Glen Ullin, Langdon, Minnewaukan, Northwood, Thompson 2/13/07 - Boundaries updated: Amenia, Arthur, Bismarck, Bottineau, Buffalo, Casstleton, Davenport, Dickinson, Enderlin, Gardner, Grand Forks, Grandin, Harvey, Harvey, Hillsboro, Horace, Hunter, Jamestown, Kindred, Mapleton, Mayville, New Rockford, Oxbox, Page, Prairie Rose, Relies Acres, Tappen, Towner City 1/10/06 - Boundaries updated: Wishek, Fargo, Lincoln, Bottineau, Williston, Grand Forks, Granville, Velva, Stanley, urban areas in Fargo, West Fargo, Bismarck and Mandan. Deleted Larson This data came from the NDDOT's Mapping Section. The original data was digitized from hand scribed maps and registered to the 1:24000 USGS PLSS data. It was converted from a projection (NAD 1983 UTM Zone 14N) to a Geographic coordinate system.

San Bernardino County City Limits current as of August 13, 2025. City limit boundaries are maintained through maps of annexations and detachments by the County of San Bernardino Surveyor's Office. City Limits GIS data stores non-contiguous city polygons as individual polygons. For questions about this dataset, please email opendata@isd.sbcounty.gov. This feature service will be retired soon and will no longer be updated with the latest changes. To ensure you always get the latest updates, please instead point your maps and apps to use the Cities and Towns (Incorporated Areas) feature layer.

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

https://tigerweb.geo.census.gov/tigerweb/TIGER (2024) boundary data.Census Designated PlacesCities and TownsCountiesPlus:Metropolitan Statistical Areas (MSA)Regional Commissions.This layer is used in the WebApp(s): Latest City Boundaries (TIGER)

Alaska City Boundaries with Certificates as attachments. Boundaries are based on the actual certificates issued by the Local Boundary Commission.

The city boundary of Chicago. This dataset is in a format for spatial datasets that is inherently tabular but allows for a map as a derived view. Please click the indicated link below for such a map. To export the data in either tabular or geographic format, please use the Export button on this dataset.

KML file of boundary for the city of Chicago. To view or use these files, special GIS software, such as Google Earth, is required.

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.

Commerce City's city limits file is a digital, geospatial file depicting the legal boundaries of the city. There are enclaves that lie within this area that should be taken into account. The Mask file is used to differentiate areas outside of the city limits during spatial operations

The 2020 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any other place. The generalized boundaries of the consolidated cities in this file are based on those as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

Polygon vector map data covering boundaries for the City of Los Angeles containing 4 features.

Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features. This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.

Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.

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

​

Polygons depict the boundaries of Washington State's incorporated municipalities, as recorded by the Washington State Office of Financial Management. Attributes include city names as provided by the Washington State Office of Financial Management, and Federal Information Processing Standard codes(FIPS) as provided by the National Institute of Standards and Technology. The Washington State Office of Financial Management provided FIPS codes for cities incorporated after the National Institute of Standards and Technology's FIPS code publication date. GNIS (Geographic Name Information System) codes provided by the Washington State Department of Revenue have been included for this quarter. The calendar date shown by Time_Period_Of_Content is the date of annexation approval and certification by the Washington State Office of Financial Management. Please direct questions about this dataset to: TransportationGISDataSteward@wsdot.wa.gov.