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://hiu.state.gov/data/cartographic_guidance_bulletins/ 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. 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 “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the feature—either line geometry or attribute—but it is still conceptually the same feature. The “PARENTID” field

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.

Homeland Infrastructure Foundation-Level Data (HIFLD) geospatial data sets containing information on Watershed Boundary Lines.

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

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.

The Watershed Boundary Dataset (WBD) in Texas was developed as a collaborative product by TWDB, USDA Natural Resources Conservation Service (NRCS) and USGS. The WBD is a seamless and consistent national Geographic Information System (GIS) database at a scale of 1:24,000, which has been extensively reviewed and matches to a minimum the USGS topographical 7.5 minute quadrangle map series. The traditional 8-digit hydrologic units (HUCs) have been further divided into smaller units called watersheds (10-digit HUCs) and sub-watersheds (12-digit HUCs). The watershed level is typically 40,000 to 250,000 acres, and the sub-watershed level is typically 10,000 to 40,000 acres with some as small as 3,000 acres. Federal Certification of the WBD for Texas was completed jointly by the NRCS and USGS in January 2009.This dataset, which has been developed to national standards (USGS and USDA/NRCS 2009), is intended to be managed in concert with the National Hydrography Dataset (NHD) as part of the Stewardship Program, supported by the U.S. Geological Survey with partner Federal, State and Local entities. Continuing development of the WBD in Texas will be completion of the 10 and 12-digit delineations of coastal watersheds. Some of the low lying coastal HUCs were not completed due to a lack of ultra high resolution elevation data necessary to determine the watershed boundaries.

The Atlas of Canada National Scale Data 1:15,000,000 Series consists of boundary, coast and coastal islands, place name, railway, river, road, road ferry and waterbody data sets that were compiled to be used for atlas small scale (1:15,000,000 and 1:30,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.

These data contain a national scale Submerged Lands Act (SLA) boundary line, Limit of "8(g) Zone," line and Continental Shelf Boundary. The SLA boundary defines the seaward limit of a state's submerged lands and the landward boundary of federally managed OCS lands. The Outer Continental Shelf Lands Act "8(g) Zone" lies between the Submerged Lands Act (SLA) boundary line and a line projected 3 nautical miles seaward of the SLA boundary line. Within this zone, oil and gas revenues are shared with the coastal state(s). The Continental Shelf Boundary defines the seaward limit of federally managed OCS lands. The line depicts the limit of U.S. jurisdiction for offshore mineral development.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

Show the line where a land mass is in contact with a body of water.

The Digital Geologic Map of International Boundary and Water Commission Mapping in Amistad National Recreation Area, Texas and Mexico is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Eddie Collins, Amanda Masterson and Tom Tremblay (Texas Bureau of Economic Geology); Rick Page (U.S. Geological Survey); Gilbert Anaya (International Boundary and Water Commission). Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (ibwc_metadata.txt; available at http://nrdata.nps.gov/amis/nrdata/geology/gis/ibwc_metadata.xml). All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.3 personal geodatabase (ibwc_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 14N. The data is within the area of interest of Amistad National Recreation Area.

The purpose of this featureclass is to allow national forest system boundary managers to query and report on the status of these boundaries for planning boundary management and maintenance work, and to provide this information to anyone else needing this information for analysis, querying, reporting, mapping. The lines should indicate the current status of the physical marked and posted lines in the field, and their maintenance status. Surface Management Agency (SMA) lines represent the surveyed boundary lines for which the Forest Service is responsible for marking and posting. These include the boundaries between NFS lands and non-NFS lands and the boundaries of congressionally designated areas such as National Wilderness. Metadata

Political boundary lines for Palau.

Large Scale International Boundaries

Version 11.1 Release Date: August 22, 2022

Overview

The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. These data and their derivatives are the only international boundary lines approved for U.S. Government use. They reflect U.S. Government policy, and not necessarily de facto limits of control. This dataset is a National Geospatial Data Asset.

Details

Sources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery of the data 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.

Attributes

The dataset uses the following attributes: Attribute Name Explanation Country Code Country-level codes are from the Geopolitical Entities, Names, and Codes Standard (GENC). The Q2 code denotes a line representing a boundary associated with an area not in GENC. Country Names Names approved by the U.S. Board on Geographic Names (BGN). Names for lines associated with a Q2 code are descriptive and are not necessarily BGN-approved. Label Required text label for the line segment where scale permits Rank/Status Rank 1: International Boundary Rank 2: Other Line of International Separation Rank 3: Special Line Notes Explanation of any applicable special circumstances Cartographic Usage Depiction of the LSIB requires a visual differentiation between the three categories of boundaries: 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. Please direct inquiries to internationalboundaries@state.gov.

Credits

The 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 Release

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. Changes to lines include: • Akrotiri (UK) / Cyprus • Albania / Montenegro • Albania / Greece • Albania / North Macedonia • Armenia / Turkey • Austria / Czechia • Austria / Slovakia • Austria / Hungary • Austria / Slovenia • Austria / Germany • Austria / Italy • Austria / Switzerland • Azerbaijan / Turkey • Azerbaijan / Iran • Belarus / Latvia • Belarus / Russia • Belarus / Ukraine • Belarus / Poland • Bhutan / India • Bhutan / China • Bulgaria / Turkey • Bulgaria / Romania • Bulgaria / Serbia • Bulgaria / Romania • China / Tajikistan • China / India • Croatia / Slovenia • Croatia / Hungary • Croatia / Serbia • Croatia / Montenegro • Czechia / Slovakia • Czechia / Poland • Czechia / Germany • Finland / Russia • Finland / Norway • Finland / Sweden • France / Italy • Georgia / Turkey • Germany / Poland • Germany / Switzerland • Greece / North Macedonia • Guyana / Suriname • Hungary / Slovenia • Hungary / Serbia • Hungary / Romania • Hungary / Ukraine • Iran / Turkey • Iraq / Turkey • Italy / Slovenia • Italy / Switzerland • Italy / Vatican City • Italy / San Marino • Kazakhstan / Russia • Kazakhstan / Uzbekistan • Kosovo / north Macedonia • Kosovo / Serbia • Kyrgyzstan / Tajikistan • Kyrgyzstan / Uzbekistan • Latvia / Russia • Latvia / Lithuania • Lithuania / Poland • Lithuania / Russia • Moldova / Ukraine • Moldova / Romania • Norway / Russia • Norway / Sweden • Poland / Russia • Poland / Ukraine • Poland / Slovakia • Romania / Ukraine • Romania / Serbia • Russia / Ukraine • Syria / Turkey • Tajikistan / Uzbekistan

This release also contains topology fixes, land boundary terminus refinements, and tripoint adjustments.

Copyright Notice and Disclaimer

While U.S. Government works prepared by employees of the U.S. Government as part of their official duties are not subject to Federal copyright protection (see 17 U.S.C. § 105), copyrighted material incorporated in U.S. Government works retains its copyright protection. The works on or made available through download from the U.S. Department of State’s website may not be used in any manner that infringes any intellectual property rights or other proprietary rights held by any third party. Use of any copyrighted material beyond what is allowed by fair use or other exemptions may require appropriate permission from the relevant rightsholder. With respect to works on or made available through download from the U.S. Department of State’s website, neither the U.S. Government nor any of its agencies, employees, agents, or contractors make any representations or warranties—express, implied, or statutory—as to the validity, accuracy, completeness, or fitness for a particular purpose; nor represent that use of such works would not infringe privately owned rights; nor assume any liability resulting from use of such works; and shall in no way be liable for any costs, expenses, claims, or demands arising out of use of such works.

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

The Atlas of Canada National Scale Data 1:1,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 large scale (1:1,000,000 to 1:4,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.

DCHC MPO boundary revised boundary that was approved and adopted on November 2012. Triangle Regional Model (TRM), for transportation modeling purposes. Version 5, 2010 base year. Data dictionary available at https://sites.google.com/a/ncsu.edu/dchc-mpo/home The NC State County Boundary GIS data set is to provide location information for the North Carolina State and County Boundary lines with best available information to facilityat planing siting, impact analysis in the 100 counties of NC. Sources for information are NC Division of Transportation, United States Geological Survey and actual field surveys conducted by North Carolina and South Carolina Licensed Surveyors that have been approved and recoded in their respective counties. This file shows some of the boundaries of counties which have a completed boundary survey but the majority of lines have not been surveyed. Also some boundaries cannot be surveyed in cases where boundaries are coincident with river centers. Most of the lines currently are from the DOT county maps which originally come from USGS but might have been updated by the county parcel maps.

Use Constraints:This mapping tool is for reference and guidance purposes only and is not a binding legal document to be used for legal determinations. The data provided may contain errors, inconsistencies, or may not in all cases appropriately represent the current boundaries of PWSs in California. The data in this map are subject to change at any time and should not be used as the sole source for decision making. By using this data, the user acknowledges all limitations of the data and agrees to accept all errors stemming from its use.Description:This mapping tool provides a representation of the general PWS boundaries for water service, wholesaler and jurisdictional areas. The boundaries were created originally by collection via crowd sourcing by CDPH through the Boundary Layer Tool, this tool was retired as of June 30, 2020. State Water Resources Control Board – Division of Drinking Water is currently in the process of verifying the accuracy of these boundaries and working on a tool for maintaining the current boundaries and collecting boundaries for PWS that were not in the original dataset. Currently, the boundaries are in most cases have not been verified. Map Layers· Drinking Water System Areas – representation of the general water system boundaries maintained by the State Water Board. This layer contains polygons with associated data on the water system and boundary the shape represents.· LPA office locations – represents the locations of the Local Primacy Agency overseeing the water system in that county. Address and contact information are attributes of this dataset.· LPA office locations – represents the locations of the Local Primacy Agency overseeing the water system in that county. Address and contact information are attributes of this dataset· California Senate Districts – represents the boundaries of the senate districts in California included as a reference layer in order to perform analysis with the Drinking Water System Boundaries layers.· California Senate Districts – represents the boundaries of the assembly districts in California included as a reference layer in order to perform analysis with the Drinking Water System Boundaries layers.· California County – represents the boundaries of the counties in California included as a reference layer in order to perform analysis with the Drinking Water System Boundaries layers.Informational Pop-up Box for Boundary layer· Water System No. – unique identifier for each water system· Water System Name – name of water system· Regulating Agency – agency overseeing the water system· System Type – classification of water system.· Population the approximate population served by the water system· Boundary Type – the type of water system boundary being displayed· Address Line 1 – the street or mailing address on file for the water system· Address Line 2 – additional line for street or mailing address on file for the water system, if applicable· City – city where water system located or receives mail· County – county where water system is located· Verification Status – the verification status of the water system boundary· Verified by – if the boundary is verified, the person responsible for the verification Date Created and Sources:This web app was most recently updated on July, 21, 2021. Each layer has a data created date and data source is indicated in the overview/metadata page and is valid up to the date provided.

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

For large areas, like Washington State, download as a file geodatabase. Large data sets like this one, for the State of Washington, may exceed the limits for downloading as shape files, excel files, or KML files. For areas less than a county, you may use the map to zoom to your area and download as shape file, excel or KML, if that format is desired.The Boundary layer consists of lines representing the boundaries of Parcels and Legal Descriptions. (See the metadata for those two layers.) Boundary lines are the places that are surveyed in order to delimit the extent of Parcels and Legal Descriptions. The character and accuracy of Boundary locations is held in the attributes of the Points that are at the ends of Boundary lines. All the boundaries of Parcels and Legal Descriptions are covered by a Boundary line. Currently the Boundary layer has little functionality. The only distinction it makes is between upland boundaries and shorelines. In the future Boundary lines will have a richer set of attributes in order to accommodate cartographic needs to distinguish between types of boundaries.WA Boundaries Metadata

This dataset contains shapefile boundaries for CA State, counties and places from the US Census Bureau's 2023 MAF/TIGER database. Current geography in the 2023 TIGER/Line Shapefiles generally reflects the boundaries of governmental units in effect as of January 1, 2023.