A feature class describing the spatial location of the administrative boundary of the lands managed by the Forest Supervisor's office. An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area. This dataset is derived from the USFS Southwestern Region ALP (Automated Lands Program) data Project. This is one of six layers derived from ALP for the purpose of supplying data layers for recourse GIS analysis and data needs within the Forest Service. The six layers are Surface Ownership, Administrative Forest Boundary, District Boundary, Townships, Sections, and Wilderness. There were some gapes in the ALP data so a small portion of this dataset comes from CCF (Cartographic Feature Files) datasets and the USFS Southwestern Region Core Data Project. ALP data is developed from data sources of differing accuracy, scales, and reliability. Where available it is developed from GCDB (Geographic Coordinate Data Base) data. GCDB data is maintained by the Bureau of Land Management in their State Offices. GCDB data is mostly corner data. Not all corners and not all boundaries are available in GCDB so ALP also utilizes many other data sources like CFF data to derive its boundaries. GCDB data is in a constant state of change because land corners are always getting resurveyed. The GCDB data used in this dataset represents a snapshot in time at the time the GCDB dataset was published by the BLM and may not reflect the most current GCDB dataset available. The Forest Service makes no expressed or implied warranty with respect to the character, function, or capabilities of these data. These data are intended to be used for planning and analyses purposes only and are not legally binding with regards to title or location of National Forest System lands.

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

This is a layer of water service boundaries for 44,786 community water systems that deliver tap water to 307.1 million people in the US. This amounts to 97% of the population reportedly served by active community water systems and 91% of active community water systems. The layer is based on multiple data sources and a methodology developed by SimpleLab and collaborators called a Tiered, Explicit, Match, and Model approach–or TEMM, for short. The name of the approach reflects exactly how the nationwide data layer was developed. The TEMM is composed of three hierarchical tiers, arranged by data and model fidelity. First, we use explicit water service boundaries provided by states. These are spatial polygon data, typically provided at the state-level. We call systems with explicit boundaries Tier 1. In the absence of explicit water service boundary data, we use a matching algorithm to match water systems to the boundary of a town or city (Census Place TIGER polygons). When a water system and TIGER place match one-to-one, we label this Tier 2a. When multiple water systems match to the same TIGER place, we label this Tier 2b. In v1.0.0, Tier 2b reflects overlapping boundaries for multiple systems. In v2.0.0 Tier 2b is removed through a "best match" algorithm that assigns one water system to one TIGER place. Finally, in the absence of an explicit water service boundary (Tier 1) or a TIGER place polygon match (Tier 2a), a statistical model trained on explicit water service boundary data (Tier 1) is used to estimate a reasonable radius at provided water system centroids, and model a spherical water system boundary (Tier 3).

Several limitations to this data exist–and the layer should be used with these in mind. The case of assigning a Census Place TIGER polygon to the "best match" water system in v2.0.0 requires further validation. Many systems were then assigned to Tier 3. Tier 3 boundaries have modeled radii stemming from a lat/long centroid of a water system facility; but the underlying lat/long centroids for water system facilities are of variable quality. It is critical to evaluate the "geometry quality" column (included from the EPA ECHO data source) when looking at Tier 3 boundaries; fidelity is very low when geometry quality is a county or state centroid– but we did not exclude the data from the layer. Future iterations plan to improve upon geometry quality for modeled systems. Missing water systems are typically those without a centroid, in a U.S. territory, or missing population and connection data. Finally, Tier 1 systems are assumed to be high fidelity, but rely on the accuracy of state data collection and maintenance.

All data, methods, documentation, and contributions are open-source and available here: https://github.com/SimpleLab-Inc/wsb.

The Gridded Population of the World, Version 3 (GPWv3): National Administrative Boundaries are derived from the land area grid to show the outlines of pixels (cells) that contain administrative Units in GPWv3 on a per-country/territory basis. The National Boundaries data are derived from the pixels as polygons and thus have rectilinear boundaries at large scale. Note that the polygons that outline the countries and territories are not official representations; rather, they represent the area covered by the statistical data as provided. The national/territorial boundaries are designed for cartographic use with the GPWv3 population raster data sets. GPWv3 is produced by the Columbia University Center for International Earth Science Information Network (CIESIN) in collaboration with Centro Internacional de Agricultura Tropical (CIAT).

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 file contains a feature class depicting National Forest System land parcels that have a Congressionally designated boundary. Examples include National Wilderness Area, Primitive Area, or Wilderness Study Area. This dataset is derived from the USFS Southwestern Region ALP (Automated Lands Program) data Project. This is one of six layers derived from ALP for the purpose of supplying data layers for recourse GIS analysis and data needs within the Forest Service. The six layers are Surface Ownership, Administrative Forest Boundary, District Boundary, Townships, Sections, and Wilderness. There were some gaps in the ALP data so a small portion of this dataset comes from CCF (Cartographic Feature Files) datasets and the USFS Southwestern Region Core Data Project. ALP data are developed from data sources of differing accuracy, scales, and reliability. Where available they are developed from GCDB (Geographic Coordinate Data Base) data. GCDB data are maintained by the Bureau of Land Management in their State Offices. GCDB data are mostly corner data. Not all corners and not all boundaries are available in GCDB so ALP also utilizes many other data sources like CFF data to derive its boundaries. GCDB data are in a constant state of change because land corners are always being resurveyed. The GCDB data used in this dataset represents a snapshot in time when the GCDB dataset was published by the BLM and may not reflect the most current GCDB dataset available. The Forest Service makes no expressed or implied warranty with respect to the character, function, or capabilities of these data. These data are intended to be used for planning and analyses purposes only and are not legally binding with regard to title or location of National Forest System lands.

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

Purpose

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 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 (this dataset)
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
   • Without Coastal Buffers
4. City and County Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

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

Field and Abbreviation Definitions

• CDTFA_CITY: CDTFA incorporated city name
• 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_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 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

The Administrative boundaries at the level 3 dataset are part of the Global Administrative Areas (GADM) 3.6 vector dataset series which includes distinct datasets representing administrative boundaries for all countries in the world. The Administrative level 3 distinguishes Communes, Municipalities and equivalent. GADM makes use of high spatial resolution images, and an extensive set of attributes to map administrative areas at all levels of political sub-division. Information on administrative units associated attributes includes official names in Latin and non-Latin scripts, variant names, administrative type in local and English. Please read the GADM 3.6 - Global Administrative Areas dataset series metadata for more information.

Zimbabwe administrative level 0 (country), 1 (province), 2 (district) and 3 (ward) boundary polygon, line, and point shapefiles, KMZ files, geodatabase, and live services, and gazetteer.

Please note that administrative level 3 (ward) features are identified numerically.

Processed by ITOS 2018 09 17. ITOS live service deployment anticipated shortly.

These shapefiles are suitable for linkage by P-code to the Zimbabwe administrative levels 0 - 2 population statistics CSV population statistics tables.

Admin3 boundaries (national divisions) The Administrative Boundaries used by the Data in Emergencies Hub are the result of a collection of international and subnational divisions currently used by FAO country offices for mapping and reporting purposes. With only a few exceptions, they are mostly derived from datasets published on The Humanitarian Data Exchange (OCHA). The dataset consists of national boundaries, first subdivision and second subdivision for Bangladesh, Madagascar, Mali, Philippines, Senegal, Sri Lanka, Tchad, Uganda and Ukraine.In the Feature Layer, the administrative boundaries are represented by closed polygons, administrative levels are nested and multiple distinct polygons are represented as a single record. The Data in Emergencies Hub team is responsible for keeping the layer up to date, so please report any possible errors or outdated information. The boundaries and names shown and the designations used on these map(s) do not imply the expression of any opinion whatsoever on the part of FAO concerning the legal status of any country, territory, city, or area or of its authorities, or concerning the delimitation of its frontiers and boundaries. Dashed lines on maps represent approximate border lines for which there may not yet be full agreement. The final boundary between the Sudan and South Sudan has not yet been determined. The final status of the Abyei area is not yet determined. The dotted line represents approximately the Line of Control in Jammu and Kashmir agreed upon by India and Pakistan. The final status of Jammu and Kashmir has not yet been agreed upon by the parties.

Areas managed as WILDERNESSwithin Glacier National Park. This mapping was compiled in 2014, implementing NPS Director's Order 41 (2013), which provides guidelines to NPS units for delineating wilderness boundaries. The two main criteria provided by DO-41 are that boundaries 1) must be easily identifiable on the ground, and 2) standard boundary setbacks from roads, paved or unpaved, should be 100-feet either side of centerline. Included in this mapping are areas EXCLUDED from wilderness, which generally fall within 100-feet of road centerline or are part of the park's Visitor Service Zone (GMP, 1999). Additional areas categorized as 'Excluded from wilderness' include lands designated as part of the Visitor Service Zone (VSZ), documented in the GLAC Commercial Serices Plan (2004). Developed area footprints were mapped and then buffered 300-feet. Utility corridors and point locations were mapped and buffered 25-feet. Also, large lakes with existing commercial services were included in the VSZ and thus were categorized as Excluded.POTENTIAL WILDERNESS AREAS (PWA) are the 3rd map class; these lands are currently in private ownership, providing access to private ownership, or are small fragmented areas (i.e. not easily identified on the ground and difficult to manage as wilderness due to size and surrounding land uses) between areas excluded from wilderness (e.g. utility corridors and lands between utility corridors and other excluded areas).Chronology of edits:Begin edits 11/8/13 to implement DO-41. Update layer March 4, 2014 - create version 3 with the following edits - based on 3/3/14 meeting with GLAC Leadership Team (Kym Hall):1. Camas Cr patrol cabin, include 100-ft buffer of cabin + 100-ft buffer of roadway from Inside Rd.2. Bowman CG area: extend 'excluded' area from admin road to creek edge to accommodate admin road/trail (to bridge) not yet mapped. Also inlcude 100-ft buffered trail and 100-ft buffered buildings due east of bridge. 3. Kintla CG - same changes as Bowman, using standard 100-ft buffer of road/cabins4. Belly River enclave is added to the data set.-----------Update layer January 24, 2014 with these edits:1. Add Marias Pass 'excluded' area; 100-ft buffer of RR turnaround.2. Extend HQ area 'excluded' polygon to river /park bdy3. Create Dev Area footprints for Road Camp & Packer's Roost; buffer 300-ft and add to 'excluded'.----------Update layer January 13, 2014 with these edits:1. Bowman CG - add admin road missed, 2. Walton - remove exclusion area between road buffer and boundary, and 3. Swiftcurrent - include Swiftcurrent+Josephine Lakes as excluded, plus bump-out areas for boat storage and creek used to ferry supplies from Swift. Lake to Josephine Lake.---------Update layer April 15-18, 2014 with these additions/edits:1. Create developed area for Apgar Lookout; buffer 300-ft.2. Create developed area for 1913 Ranger Station (St Mary); buffer 300-ft.3. Add 2 monitoring wells in St Mary Flats (foot of lake south of GTSR); buffer 25-ft and connect to 'excluded area' polygon4. Add water source point for Many Glacier winter cabin (north of MG road near hotel jct; buffer 25-ft and add to 'excluded area' polygon5. Buffer McCarthy Homestead structures 100-ft and add to Excluded Area polygon for Inside North Fork Rd6. Buffer Ford Creek cabin structures 100-ft and add to Excluded Area polygon for Inside North Fork Rd7. Buffer Baring Crek cabin structures 100-ft and add to Excluded Area polygon Going to the Sun Rd8. Add to Excluded Area a strip of land 60-ft south of the International Boundary (per 1974 Wilderness proposal & MOU with GLAC and Int'l Boundary Comm).---------Updated layer 5/27/2014 - add approx. 2 acres to 'Excluded fro mWilderness' near the St Mary River bridge along GTSR. This sliver of land was included to utilize the river bank as a visible and distinguishable boundary in the field.

© NPS, Glacier NP GIS Program

This layer is a component of Glacier National Park.

This map service provides layers covering a variety of different datasets and themes for Glacier National Park. It is meant to be consumed by internet mapping applications and for general reference. It is for internal NPS use only. Produced November 2014.

© Denver Service Center Planning Division, IMR Geographic Resources Division, Glacier National Park

This data set is a subset of the complete digital hydrologic unit boundary layer to the Subwatershed (12-digit) 6th level for the State of Utah. The State Watershed Boundary (WBD) was dissolved to the 8 digit, 4th level sub-basin. The State WBD 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. Data downloaded from USDA on 8/14/2017.

Contains:World HillshadeWorld Street Map (with Relief) - Base LayerLarge Scale International Boundaries (v11.3)World Street Map (with Relief) - LabelsDoS Country Labels DoS Country LabelsCountry (admin 0) labels that have been vetted for compliance with foreign policy and legal requirements. These labels are part of the US Federal Government Basemap, which contains the borders and place names that have been vetted for compliance with foreign policy and legal requirements.Source: DoS Country Labels - Overview (arcgis.com)Large Scale International BoundariesVersion 11.3Release Date: December 19, 2023DownloadFor more information on the LSIB click here: https://geodata.state.gov/ A direct link to the data is available here: https://data.geodata.state.gov/LSIB.zipAn ISO-compliant version of the LSIB metadata (in ISO 19139 format) is here: https://geodata.state.gov/geonetwork/srv/eng/catalog.search#/metadata/3bdb81a0-c1b9-439a-a0b1-85dac30c59b2 Direct inquiries to internationalboundaries@state.govOverviewThe 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.3 (published 19 December 2023). The 11.3 release contains updates to boundary lines and data refinements enabling reuse 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 AssetThis dataset is a National Geospatial Data Asset managed by the Department of State on behalf of the Federal Geographic Data Committee's International Boundaries Theme.DetailsSources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process involves 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.Attribute StructureThe dataset uses thefollowing attributes:Attribute NameCC1COUNTRY1CC2COUNTRY2RANKSTATUSLABELNOTES These attributes are logically linked:Linked AttributesCC1COUNTRY1CC2COUNTRY2RANKSTATUS These attributes have external sources:Attribute NameExternal Data SourceCC1GENCCOUNTRY1DoS ListsCC2GENCCOUNTRY2DoS ListsThe eight attributes listed above describe the boundary lines contained within the LSIB dataset in both a human and machine-readable fashion. Other attributes in the release include "FID", "Shape", and "Shape_Leng" are components of the shapefile format and do not form an intrinsic part of the LSIB."CC1" and "CC2" fields are machine readable fields which contain political entity codes. These codes are derived from the Geopolitical Entities, Names, and Codes Standard (GENC) Edition 3 Update 18. The dataset uses the GENC two-character codes. The code ‘Q2’, which is not in GENC, denotes a line in the LSIB representing a boundary associated with an area not contained within the GENC standard.The "COUNTRY1" and "COUNTRY2" fields contain human-readable text corresponding to the name of the political entity. These names are names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the list of Independent States in the World and the list of Dependencies and Areas of Special Sovereignty maintained by the Department of State. To ensure the greatest compatibility, names are presented without diacritics and certain names are rendered using commonly accepted cartographic abbreviations. Names for lines associated with the code ‘Q2’ are descriptive and are not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS are names of independent states. Other names are those associated with dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.The following fields are an intrinsic part of the LSIB dataset and do not rely on external sources:Attribute NameMandatoryContains NullsRANKYesNoSTATUSYesNoLABELNoYesNOTESNoYesNeither the "RANK" nor "STATUS" field contains null values; the "LABEL" and "NOTES" fields do.The "RANK" field is a numeric, machine-readable expression of the "STATUS" field. Collectively, these fields encode the views of the United States Government on the political status of the boundary line.Attribute NameValueRANK123STATUSInternational BoundaryOther 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 necessarily to describe the line segment. The "LABEL" field is used when the line segment is displayed on maps or other forms of cartographic visualizations. This includes most interactive products. The requirement to incorporate the contents of the "LABEL" field on these 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 is not a line labeling field but does contain the preferred description for the three LSIB line types when lines are incorporated into a map legend. Using the "CC1", "CC2", or "RANK" fields for labeling purposes is prohibited.The "NOTES" field contains an explanation of any applicable special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, any limitations regarding the purpose of the lines, or the original source of the line. Use of the "NOTES" field for labeling purposes is prohibited.External Data SourcesGeopolitical Entities, Names, and Codes Registry: https://nsgreg.nga.mil/GENC-overview.jspU.S. Department of State List of Independent States in the World: https://www.state.gov/independent-states-in-the-world/U.S. Department of State List of Dependencies and Areas of Special Sovereignty: https://www.state.gov/dependencies-and-areas-of-special-sovereignty/The source for the U.S.—Canada international boundary (NGDAID97) is the International Boundary Commission: https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpThe source for the “International Boundary between the United States of America and the United States of Mexico” (NGDAID82) is the International Boundary and Water Commission: https://catalog.data.gov/dataset?q=usibwcCartographic UsageCartographic usage of the LSIB requires a visual differentiation between the three categories of boundaries. 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.Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues.ContactDirect inquiries to internationalboundaries@state.gov.CreditsThe lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre.Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.Changes from Prior ReleaseThe 11.3 release is the third update in the version 11 series.This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Notable changes to lines include:• AFGHANISTAN / IRAN• ALBANIA / GREECE• ALBANIA / KOSOVO• ALBANIA/MONTENEGRO• ALBANIA / NORTH MACEDONIA• ALGERIA / MOROCCO• ARGENTINA / BOLIVIA• ARGENTINA / CHILE• BELARUS / POLAND• BOLIVIA / PARAGUAY• BRAZIL / GUYANA• BRAZIL / VENEZUELA• BRAZIL / French Guiana (FR.)• BRAZIL / SURINAME• CAMBODIA / LAOS• CAMBODIA / VIETNAM• CAMEROON / CHAD• CAMEROON / NIGERIA• CHINA / INDIA• CHINA / NORTH KOREA• CHINA / Aksai Chin• COLOMBIA / VENEZUELA• CONGO, DEM. REP. OF THE / UGANDA• CZECHIA / GERMANY• EGYPT / LIBYA• ESTONIA / RUSSIA• French Guiana (FR.) / SURINAME• GREECE / NORTH MACEDONIA• GUYANA / VENEZUELA• INDIA / Aksai Chin• KAZAKHSTAN / RUSSIA• KOSOVO / MONTENEGRO• KOSOVO / SERBIA• LAOS / VIETNAM• LATVIA / LITHUANIA• MEXICO / UNITED STATES• MONTENEGRO / SERBIA• MOROCCO / SPAIN• POLAND / RUSSIA• ROMANIA / UKRAINEVersions 11.0 and 11.1 were updates to boundary lines. Like this version, they also contained topology fixes, land boundary terminus refinements, and tripoint adjustments. Version 11.2 corrected a few errors in the attribute data and ensured that CC1 and CC2 attributes are in alignment with an updated version of the Geopolitical Entities, Names, and Codes (GENC) Standard, specifically Edition 3 Update 17.LayersLarge_Scale_International_BoundariesTerms of

This dataset represents the boundaries of designated Main Street New Jersey Communities.

This dataset represents the boundaries of designated Main Street New Jersey Communities.

Source: http://www.nj.gov/dca/divisions/osg/resources/gis.html

A feature class describing the spatial location of the administrative boundary of the lands managed by the Forest Supervisor's office. An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area. This dataset is derived from the USFS Southwestern Region ALP (Automated Lands Program) data Project. This is one of fourteen layers derived from ALP for the purpose of supplying data layers for recourse GIS analysis and data needs within the Forest Service. The fourteen layers are Administrative Forest, Administrative Region, National Grassland, Ranger District, Military Reserve, Other National Designated Area, Proclaimed Forest, Section, Special Interest Management Area, Surface Ownership, Surface Ownership Dissolve, Township, Wilderness Status, and Wild Scenic River . There were some gapes in the ALP data so a small portion of this dataset comes from CCF (Cartographic Feature Files) datasets and the USFS Southwestern Region Core Data Project. ALP data is developed from data sources of differing accuracy, scales, and reliability. Where available it is developed from GCDB (Geographic Coordinate Data Base) data. GCDB data is maintained by the Bureau of Land Management in their State Offices. GCDB data is mostly corner data. Not all corners and not all boundaries are available in GCDB so ALP also utilizes many other data sources like CFF data to derive its boundaries. GCDB data is in a constant state of change because land corners are always getting resurveyed. The GCDB data used in this dataset represents a snapshot in time at the time the GCDB dataset was published by the BLM and may not reflect the most current GCDB dataset available. The Forest Service makes no expressed or implied warranty with respect to the character, function, or capabilities of these data. These data are intended to be used for planning and analyses purposes only and are not legally binding with regards to title or location of National Forest System lands.

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

Purpose

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

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

Related Layers

This dataset is part of a grouping of many datasets:

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

Point of Contact

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

Field and Abbreviation Definitions

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

The National Water Quality Network (NWQN) for Rivers and Streams includes 113 surface-water river and stream sites monitored by the U.S. Geological Survey (USGS) National Water Quality Program (NWQP). The NWQN represents the consolidation of four historical national networks: the USGS National Water-Quality Assessment (NAWQA) Project, the USGS National Stream Quality Accounting Network (NASQAN), the National Monitoring Network (NMN), and the Hydrologic Benchmark Network (HBN). The NWQN includes 22 large river coastal sites, 41 large river inland sites, 30 wadeable stream reference sites, 10 wadeable stream urban sites, and 10 wadeable stream agricultural sites. In addition to the 113 NWQN sites, 3 large inland river monitoring sites from the USGS Cooperative Matching Funds (Co-op) program are also included in this annual water-quality reporting Web site to be consistent with previous USGS studies of nutrient transport in the Mississippi-Atchafalaya River Basin. This data release contains geo-referenced digital data and associated attributes of watershed boundaries for 113 NWQN and 3 Co-op sites. Two sites, "Wax Lake Outlet at Calumet, LA"; 07381590, and "Lower Atchafalaya River at Morgan City, LA"; 07381600, are outflow distributaries into the Gulf of Mexico. Watershed boundaries were delineated for the portion of the watersheds between "Red River near Alexandria, LA"; 07355500 and "Atchafalaya River at Melville, LA"; 07381495 to the two distributary sites respectively. Drainage area was undetermined for these two distributary sites because the main stream channel outflows into many smaller channels so that streamflow is no longer relative to the watershed area. NWQN watershed boundaries were derived from the Watershed Boundary Dataset-12-digit hydrologic units (WBD-12). The development of the WBD-12 was a coordinated effort between the United States Department of Agriculture-Natural Resources Conservation Service (USDA-NRCS), the USGS, and the Environmental Protection Agency (EPA) (U.S. Department of Agriculture-Natural Resources Conservation Service, 2012). A hydrologic unit is a drainage area delineated to nest in a multi-level, hierarchical drainage system. Its boundaries are defined by hydrographic and topographic criteria that delineate an area of land upstream from a specific point on a river, stream or similar surface waters. The United States is divided and sub-divided into successively smaller hydrologic units identified by a unique hydrologic unit code (HUC) consisting of two to 12 digits based on the six levels of classification in the hydrologic unit system: regions, sub-regions, accounting units, cataloging units, watersheds, and sub-watersheds. NWQN watershed boundaries were delineated by selecting all sub-watershed polygons that flow into the most downstream WBD-12 polygon in which the NWQN site is located. The WBD-12 attribute table contains 8-digit, 10-digit, and 12-digit HUCs which were used to identify which sub-watersheds flow into the watershed pour point at the NWQN site location. When the NWQN site was located above the pour point of the most downstream sub-watershed, the sub-watershed was edited to make the NWQN site the pour point of that sub-watershed. To aid editing, USGS 1:24,000 digital topographic maps were used to determine the hydrologic divide from the sub-watershed boundary to the NWQN pour point. The number of sub-watersheds which are contained within the NWQN watersheds ranged from less than one to nearly 32,000 internal sub-watersheds. Internal sub-watershed boundaries were dissolved so that a single watershed boundary was generated for each NWQN watershed. Data from this release are presented at the USGS Tracking Water Quality page: http://cida.usgs.gov/quality/rivers/home (Deacon and others, 2015). Watershed boundaries delineated for this release do not take into account non-contributing area, diversions out of the watershed, or return flows into the watershed. Delineations are based solely on contributing WBD-12 polygons with modifications done only to the watershed boundary at the NWQN site location pour point. For this reason calculated drainage areas for these delineated watersheds may not match National Water Information System (MWIS) published drainage areas (http://dx.doi.org/10.5066/F7P55KJN). Deacon, J.R., Lee, C.J., Toccalino, P.L., Warren, M.P., Baker, N.T., Crawford, C.G., Gilliom, R.G., and Woodside, M.D., 2015, Tracking water-quality of the Nation’s rivers and streams, U.S. Geological Survey Web page: http://cida.usgs.gov/quality/rivers, https://dx.doi.org/doi:10.5066/F70G3H51. U.S. Department of Agriculture-Natural Resources Conservation Service, 2012, Watershed Boundary Dataset-12-digit hydrologic units: NRCS National Cartography and Geospatial Center, Fort Worth, Tex., WBDHU12_10May2012_9.3 version, accessed June 2012 at http://datagateway.nrcs.usda.gov.

Egypt administrative boundary level 0 (national), 1 (governorate), 2 (region), and 3 polygons, and major and minor populated places provided as a geodatabase, shapefiles, KMZ file.

This file contains the digital vector boundaries for Nomenclature of Territorial Units for Statistics Level 3, in the United Kingdom, as at January 2018. The boundaries are super generalised (200m) - clipped to the coastline (Mean High Water mark). Contains both Ordnance Survey and ONS Intellectual Property Rights.REST URL of ArcGIS for INSPIRE View Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/NUTS3_(Jan_2018)_SGCB_in_the_UK/MapServerREST URL of ArcGIS for INSPIRE Feature DownloadService – https://dservices1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/services/NUTS3_Jan_2018_Super_Generalised_Clipped_Boundaries_in_the_UK/WFSServer?service=wfs&request=getcapabilitiesREST URL of Feature Access Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/NUTS3_Jan_2018_SGCB_in_the_UK_2022/FeatureServer