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.

ATTOM’s census boundary data includes various geographies with a large range of sizes, population, and governmental functions. These datasets enable property searches for familiar named areas such as counties, cities, and townships. The included boundaries can be utilized for census boundary map overlays.

The dataset is available to download in Geotiff format at a resolution of 3 arc-second (approximately 100m at the equator). The projection is Geographic Coordinate System, WGS84. Grid cell values represent International Standard 3-digit numerical ISO 3166 Country Codes corresponding to country and territory names as designated by the United Nations (ISO, 2017). It is important to note that these data are not official representations of country boundaries, some of which are disputed, but simply represent the source of the population count data.Data Source: Global national level input population data-summaryMethodology: Lloyd, C. T., H. Chamberlain, D. Kerr, G. Yetman, L. Pistolesi, F. R. Stevens, A. E. Gaughan, J. J. Nieves, G. Hornby, K. MacManus, P. Sinha, M. Bondarenko, A. Sorichetta, and A. J. Tatem, 2019. “Global Spatio-temporally Harmonised Datasets for Producing High-resolution Gridded Population Distribution Datasets”. Big Earth Data (https://doi.org/10.1080/20964471.2019.1625151).

This document 'How BoundaryLine, ONS Boundaries and the NSPL and ONSPD are processed' shows, in a flow diagram, the interaction between OS Boundary Line releases and updates to ONS boundary and postcode products. (File Size - 182 KB)

Boundaries of boroughs (water areas excluded). All previously released versions of this data are available at BYTES of the BIG APPLE - Archive.

(Link to Metadata) COUSUB2010 contains a subset of attributes from Summary File 1 of the 2010 Decennial Census.The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data, and they include legally minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the legal MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas is covered by county subdivisions. The boundaries of all 2010 Census legal MCDs are as of January 1, 2010 as reported through the Census Bureau's Boundary and Annexation Survey (BAS). For the 2010 Census, CCDs or their equivalents are delineated in 21 States. The boundaries of all 2010 Census statistical CCDs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP).

This layer represents current city boundaries within Los Angeles County. The Los Angeles County Department of Public Works provides the most current shapefiles representing city boundaries and city annexations 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 include:CITY_NAME: represents the city's name.CITY_TYPE: may be used for definition queries; "Unincorporated" or "City".FEAT_TYPE: identifies the feature that each polygon represents:Land - This value is used for polygons representing the land masses, 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 - This value is used for polygons representing the three seaward nautical miles within the cities' limits, per the Submerged Lands Act.POPULATION: Information in this field is supplied by Mark Greninger (mgreninger@cio.lacounty.gov).Reference Date: 2021

An in-depth description of the various Political Boundaries GIS data layers outlining terms of use, update frequency, attribute explanations, and more. District data layers include: Lake County Boundary, County Board, Judicial Circuit Court Subcircuits, Political Townships, State Representative Districts, State Senate, Congressional Districts, and Voting Precincts.

This data set shows Administrative Boundary data, specifically for Neighboring Countries. The data is acquired from the Bureau of Statistics.

The Atlas of Canada National Scale Data 1:5,000,000 Series consists of boundary, coast, island, place name, railway, river, road, road ferry and waterbody data sets that were compiled to be used for atlas medium scale (1:5,000,000 to 1:15,000,000) mapping. These data sets have been integrated so that their relative positions are cartographically correct. Any data outside of Canada included in the data sets is strictly to complete the context of the data.

(Link to Metadata) The BNDHASH dataset depicts Vermont village, town, county, and Regional Planning Commission (RPC) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) BNDHASH_POLY_VILLAGES = Vermont villages 2) BNDHASH_POLY_TOWNS = Vermont towns 3) BNDHASH_POLY_COUNTIES = Vermont counties 4) BNDHASH_POLY_RPCS = Vermont's Regional Planning Commissions 5) BNDHASH_POLY_VTBND = Vermont's state boundary 6) BNDHASH_LINE = Lines on which all POLY feature classes are built The master BNDHASH data is managed as an ESRI geodatabase feature dataset by VCGI. The dataset stores village, town, county, RPC, and state boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/RPC/state boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the locations of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line feature with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

Digital boundary dataset - Statistical Areas Level 1 (SA1)Australian Statistical Geography Standard (ASGS) Edition 3

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.

Washington State County Boundaries including Department of Natural Resources (DNR) county codes. This data is created from the WA Public Land Survey source data maintained by the DNR.WA County Boundaries Metadata

This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.

NUTS2 boundaries ungeneralised. The Nomenclature of Territorial Units for Statistics (NUTS) were drawn up by Eurostat in order to define territorial units for the production of regional statistics across the European Union. The NUTS classification has been used in EU legislation since 1988, but it was only in 2003 that the EU Member States, the European Parliament and the Commission established the NUTS regions within a legal framework (Regulation (EC) No 1059/2003).The Irish NUTS 3 regions comprise the eight Regional Authorities established under the Local Government Act, 1991 (Regional Authorities) (Establishment) Order, 1993 which came into operation on January 1st 1994. The NUTS 2 regions, which were proposed by Government and agreed to by Eurostat in 1999, are groupings of the Regional Authorities.This dataset is provided by Tailte Éireann

This layer shows population broken down by race and Hispanic origin. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the predominant race living within an area. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B03002Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

In 2014 and 2015, The LA County Enterprise GIS team under the Geographic Information Officer worked with the Unincorporated Area Deputies and Field Deputies of each Board Office to establish names that reflect the desires of residents. CSAs differ from the more informal Community geographies because:They are focused on broad statistics and reporting, not mapping of communities.They represent board approved names assigned to Census block groups and city boundaries.They cover the entire unincorporated County (no gaps).There are not overlapping areas. Additionally, CSAs use the following naming conventions:All names are assumed to begin with Unincorporated (e.g. Unincorporated El Camino Village) which will not be part of the CSA Name (so the name of the Statistical Area would be El Camino Village).Names will not contain “Island.” Beginning each name with Unincorporated will distinguish an area from any surrounding cities. There may be one or more exceptions for certain small areas (e.g. Bandini Islands)A forward slash implies an undetermined boundary between two areas within a statistical geography (e.g. Westfield/Academy Hills or View Park/Windsor Hills)Certain established names may include hyphens (e.g. Florence-Firestone)Aliases may be defined in parentheses (e.g. Unincorporated Long Beach (Bonner/Carson Park))The original set of names were derived from community names used in the 2011 Redistricting process, chosen with the assistance of the Board of Supervisors.Updates: 2025 March: CSA update for Duarte City annexation; and Arcadia City detachment and Monrovia City annexation (effective date 3/17/2025).2024 December: CSA data update to include Whittier City annexation (effective date 11/13/2024).2024 April: CSA data updated to include La Verne City annexation (effective date 4/1/2024).2023 December: CSA data updated to include "Unincorporated Charter Oak" (south of 10 Freeway) into "Unincorporated Covina".2023 June: CSA data was updated to include "Kinneloa Mesa" community, which was a part of Unincorporated East Pasadena.2023 January: Updated layer schema to include feature type (“FEAT_TYPE”) field, which can be one of land, water, breakwater, or pier (consistent with the City Boundaries layer).2022 December: CSA data was updated to incorporate the “Tesoro Del Valle” annexation to the city of Santa Clarita. Unincorporated Valencia is now completely annexed to the City of Santa Clarita. In addition to land area, this data also includes other feature types such as piers, breakwater and water area. 2022 September: CSA data was updated to match with city boundaries along shoreline/coastal area and minor boundary adjusted in some other areas.

The document explains the differences between the different boundary sets that ONS Geography provides. Valid from 2021. (File Size - 500 KB)

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset was made available (approximately 2004) through CALFIRE - FRAP and the California Spatial Information Library (CaSIL), with additional updates throughout subsequent years. More recently, an effort was made to improve the coastal linework by using the previous interior linework from the 24k data, but replacing the coastal linework based on NOAA's ERMA coastal dataset (which used NAIP 2010). In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included, with the exception of the Channel Islands which ARE included.This service represents the latest released version, and is updated when new versions are released. As of June, 2019 it represents cnty19_1.