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.

World Bank-approved administrative boundaries (Admin 0) (and polygons) including international boundaries, disputed areas, coastlines, and lakes. Boundaries are available as an ESRI GeoDatabase, in GeoJSON, a shapefile and API endpoints for interactive maps.

Overview

The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control.

National Geospatial Data Asset

This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee.

Dataset Source Details

Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground.

Cartographic Visualization

The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below.

Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html

Contact

Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip

Attribute Structure

The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension

These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE

The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB.

Core Attributes

The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields.

County Code and Country Name Fields

“CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard.

The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.

Descriptive Fields

The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes

Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line.

ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line

A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively.

The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps.

The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line.

Use of Core Attributes in Cartographic Visualization

Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between:

• International Boundaries (Rank 1);
• Other Lines of International Separation (Rank 2); and
• Special Lines (Rank 3).

Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction.

The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling.

Use of

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

ASAP information is provided at two spatial levels: national (Gaul0) and sub-national (Gaul1). The reference spatial layers are derived from the Global Administrative Unit Layers (GAUL) dataset, implemented by FAO within the CountrySTAT and Agricultural Market Information System (AMIS) projects. The original data sets were adapted to match specific ASAP requirements (e.g. in some countries, the sub-national units were aggregated, in others they were split in smaller units) and geometry was simplified (e.g. the number of vertex reduced and small islands removed).

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.

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.

This dataset contains existing and approved residential boundaries in Cary, NC. For additional information on properties check out our website. This dataset is updated as residential boundaries are changed.

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's 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 jurisdictions. The boundaries are continuously being revised 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 and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the Board of Equalization's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

This dataset displays level 0 world administrative boundaries. It contains countries as well as non-sovereign territories (like, for instance, French overseas).

January 2023 - Census population data were downloaded for 2020 and appended to the county dataset. Population fields were re-ordered and named for consistency.April 2013 - Census data were downloaded for 2010 and appended to the county coverage. Upon further review by the ND GIS Technical Meeting at their April 2013 meeting, it was decided that the demographic data included with the previous county feature class would be dropped, leaving only basic information with the necessary relational fields intact for joining of Census data tables and other related North Dakota data.The North Dakota county coverage was originally created by the North Dakota Geological Survey using US Census Bureau TIGER data in 1994. The source scale on these data was 1:100,000. Since its creation, with USGS Public Land Survey DLG data, and USGS DRG derived data. The North Dakota State Water Commission revamped this coverage by using the NDGS PLSS coverage (combination of ND PSC, USGS DLG and DRG 24k data) to obtain county boundaries that coincided with PLSS linework, and heads-up digitized irregular boundaries such as that on the State borders, and those that followed river/stream boundaries with USGS 1:24,000 scale Digital Raster Graphics. The resultant coverage should be much better than a 1:100,000 scale coverage, but may not meet 1:24,000 scale accuracy standards.

This GIS dataset contains polygons depicting U.S. EPA Superfund Site boundaries. Site boundaries are polygons representing the footprint of a whole site, defined for purposes of this effort as the sum of all of the Operable Units and the current understanding of the full extent of contamination. For Federal Facility sites, the total site polygon may be the Facility boundary. As site investigation and remediation progress, OUs may be added, modified or refined, and the total site polygon should be updated accordingly. Superfund features are managed by regional teams of geospatial professionals and remedial program managers (RPMs), and SEGS harvests regional data on a weekly basis to refresh the national dataset and feature services.

This data set is a complete digital hydrologic unit boundary layer to the Subbasin (8-digit) 8th level for the State of New Mexico. This data set consists of geo-referenced digital data and associated attributes created in accordance with the "FGDC Proposal, Version 1.0 - Federal Standards For Delineation of Hydrologic Unit Boundaries 3/01/02"(http://www.ftw.nrcs.usda.gov/huc_data.html). Polygons are attributed with hydrologic unit codes for 4th level sub-basins, 5th level watersheds, 6th level subwatersheds, name, size, downstream hydrologic unit, type of watershed, non-contributing areas and flow modification. Arcs are attributed with the highest hydrologic unit code for each watershed, linesource and a metadata reference file.

The borough boundaries for New York City clipped to the shoreline. All previously released versions of this data are available at BYTES of the BIG APPLE - Archive.

Boundaries for the municipalities that surround Chicago. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required.

Feature level Dataset for the BLM Administrative Unit Boundaries Data Standard. This feature dataset includes both BLM administrative land areas and office locations. Land areas are depicted with polygons for the smallest administrative unit (field offices). Larger administrative units, such as district offices, and administrative states may be derived from these polygons. Office locations at each level are depicted with points. This dataset is a subset of the official national dataset, containing features and attributes intended for public release and has been optimized for online map service performance. The Schema Workbook represents the official national dataset from which this dataset was derived.

Boston Neighborhood Boundaries represent a combination of zoning neighborhood boundaries, zip code boundaries and 2010 census tract boundaries. These boundaries are used in the broad sense for visualization purposes, research analysis and planning studies. However these boundaries are not official neighborhood boundaries for the City of Boston. The BPDA is not responsible for any districts or boundaries within the City of Boston except for the districts we use for planning purposes.

Stormwater Action Monitoring (SAM) is a collaborative monitoring program between western Washington municipal stormwater permittees, state and federal agencies. SAM’s role is to use the results of regional monitoring and focused studies to inform policy decisions and identify effective strategies to improve stormwater management in the Puget Sound region. The SAM program includes status and trends monitoring of water quality, stream biota (macroinvertebrates, algae), and stream habitat to measure whether conditions are getting better or worse and identify patterns in healthy and impaired Puget Lowland streams. To meet this objective, a framework of fundamental geospatial data was required to develop physical and anthropogenic characteristics of the study region, sampled sites and corresponding watersheds, and riparian zones. This dataset represents the watershed boundaries for the 105 sites sampled for the SAM small stream study, and is one of the four fundamental geospatial data lay ...

This layer file consists of three related datasets:
- Statutory boundary polygons of State Forests
- Lands managed by the Division of Forestry within the statutory boundaries, known as Management Units
- Lands managed by the Division of Forestry outside of the statutory boundaries, known as Other Forestry Lands

State Forests - Statutory Boundaries:
This theme shows the boundaries of those areas of Minnesota that have been legislatively designated as State Forests ( http://www.dnr.state.mn.us/state_forests/index.html )

Minnesota's 58 state forests were established to produce timber and other forest crops, provide outdoor recreation, protect watersheds, and perpetuate rare and distinctive species of native flora and fauna. The mapped boundaries are based on legislative/statutory language and are described in broad terms based on legal descriptions. Private or other ownerships included inside a State Forest boundary are typically NOT identified in legislative language and subsequently are NOT mapped in this layer. It is important to note that these data do not represent public ownership. State Forest boundaries often include private land and should not be used to determine ownership. Ownership information can be found in State Surface Interests Administered by MNDNR or by Counties ( https://gisdata.mn.gov/dataset/plan-stateland-dnrcounty ) and the GAP Stewardship 2008 layer ( http://gisdata.mn.gov/dataset/plan-gap-stewardship-2008 ).

Data has been updated during 2009 by the MNDNR Forest Resource Assessment office.

State Forests - Management Units
This theme shows the land owned and managed by the Division of Forestry within the Statutory Boundaries. The shapes were derived mostly from county parcel data, where available, and from plat maps and other ownership resources. This data presents an approximate location of the land ownership and is intended for cartographic purposes only. It is not survey quality and should never be used to resolve land ownership disputes.

State Forests - Other Forest Lands
This theme shows State Forest lands outside of the State Forest Statutory Boundaries. It was derived from MNDNR's Land Records System PLS40 data layer. Sub-40 shapes are not represented. Partial PLS40 ownership is represented as a whole PLS40. This data is not survey quality and should never be used to resolve land ownership disputes.