Important Note: This item is in mature support as of November 2021 and will be retired. A NEW VERSION of this item is available for your use. We recommend updating your maps and apps to use the new version.Boundary-Line is a specialist 1:10 000 scale boundaries dataset. It contains all levels of electoral and administrative boundaries, from district, wards and civil parishes (or communities) up to parliamentary, assembly and European constituencies. The currency of this data is 10/2019.

The coverage of the map service is GB. The map projection is British National Grid. The service is appropriate for viewing down to a scale of approximately 1:20,000. Updated by Esri UK: 22/01/2020To download this dataset use the link here.Ever wondered how Boundary-Line data could be used in analysis? Take a look at our police or supermarket story map.

This line-based spatial data represents the Boundary Lines that exist in the Digital Tax Map Collection. • Updates: Data is extracted from DOF’s internal system on the last Friday of each month and refreshed on ArcGIS Online on the 1st. The online map always shows the most recent version. • Accessing the Data: • Digital Tax Map on NYC Open Data: See the complete collection. • Individual layers: Downloadable from the Digital Tax Map Feature Server. • Complete source: Available through the Digital Tax Map service, which always points to the latest monthly release. Note: To ensure reliability, the Tax Map alternates between Set A and Set B each month. If one set has issues, the previous month’s copy remains online. Both sets are kept about a month apart and are available for download: • Set A link • Set B link • Digital Alteration Book (DAB): The DAB is the official log of map changes—such as new lots, merges, or boundary shifts—providing a clear record of how the Tax Map evolves. It is available through the Property Information Portal. Disclaimer: This dataset reflects formal applications submitted to DOF but may not reflect the latest changes in other City systems (e.g., exemptions or buildings data). It is provided for informational purposes only and is not guaranteed to be accurate as of today’s date.

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 “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

Natural Earth is a public domain map dataset available at 1:10, 1:50 and 1:110 million scales. Featuring tightly integrated vector and raster data, with Natural Earth you can make a variety of visually pleasing, well-crafted maps with cartography or GIS software.

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 is a map service displaying country boundaries and geographic labels in the Antarctic. The map layers are from the Natural Earth project.Map projection: WGS84 Antarctic Polar Stereographic; standard parallel of 71 degrees; EPSG:3031; outer edge at 50 degrees south.Note: this will not display in the correct projection if you click on the thumbnail or choose "Add to Map". For a combined ArcGIS Online map displaying this service in Antarctic projection along with other useful reference layers, please see: https://noaa.maps.arcgis.com/home/item.html?id=d13b9d10219e4429974e48368b64e41f

Village boundary(lines) nationwide................

Village boundaries................................

The Watershed Boundary Dataset (WBD) is a comprehensive aggregated collection of hydrologic unit data consistent with the national criteria for delineation and resolution. It defines the areal extent of surface water drainage to a point except in coastal or lake front areas where there could be multiple outlets as stated by the "Federal Standards and Procedures for the National Watershed Boundary Dataset (WBD)"(https://pubs.usgs.gov/tm/11/a3/). Watershed boundaries are determined solely upon science-based hydrologic principles, not favoring any administrative boundaries or special projects, nor particular program or agency. This dataset represents the hydrologic unit boundaries to the 12-digit for the entire United States. Some areas may also include additional subdivisions representing the 14- and 16-digit hydrologic unit (HU). At a minimum, the HUs are delineated at 1:24,000-scale in the conterminous United States, 1:25,000-scale in Hawaii, Pacific basin and the Caribbean, and 1:63,360-scale in Alaska, meeting the National Map Accuracy Standards (NMAS). Higher resolution boundaries were developed where partners and data existed and were incorporated back into the WBD. WBD data are delivered as a dataset of polygons and corresponding lines that define the boundary of the polygon. WBD polygon attributes include hydrologic unit codes (HUC), size (in the form of acres and square kilometers), name, downstream hydrologic unit code, type of watershed, non-contributing areas, and flow modifications. The HUC describes where the unit is in the country and the level of the unit. WBD line attributes contain the highest level of hydrologic unit for each boundary, line source information and flow modifications. For additional information on NHD, go to https://www.usgs.gov/national-hydrography.

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.

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

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

California Department of Transportation (Caltrans), Division of Transportation Planning, Aeronautics Program provided airport layout drawings with estimated digitized airport property or fence lines with Google Pro images background.Caltrans Division of Research, Innovation and System Information (DRISI) GIS office digitized the airport boundary lines with Bing Maps Aerial background and built the boundary lines into a GIS polygon feature class.Generally, Airport Layout Plans do not show complete connected property or fence lines. In many cases the boundary lines were interpreted among the property and fence lines with our best judgment. The airport general information derived from FAA Airport Master Record and Reports with their URL are included in the attribute table.Airport boundary data is intended for general reference and does not represent official airport property boundary determinations.

This map layer contains hydrologic unit boundaries and codes for the United States, Puerto Rico, and the U.S. Virgin Islands. It was revised for inclusion in the National Atlas of the United States of America, and updated to match the streams file created by the USGS National Mapping Division (NMD) for the National Atlas of the United States of America. This is a revised version of the November 2002 map layer.

This dataset is refreshed on a weekly basis from the datasets the team works on daily.Last update date: 16 October 2025.National Highways Operational Highway Boundary (RedLine) maps out the land belonging to the highway for the whole Strategic Road Network (SRN). It comprises two layers; one being the an outline and another showing the registration status / category of land of land that makes up the boundary. Due to the process involved in creating junctions with local highway authority (LHA) roads, land in this dataset may represent LHA highway (owned by National Highways but the responsibility of the LHA to maintain). Surplus land or land held for future projects does not form part of this dataset.The highway boundary is derived from:Ordnance Survey Mastermap Topography,HM Land Registry National Polygon Service (National Highway titles only), andplots researched and digitised during the course of the RedLine Boundary Project.The boundary is split into categories describing the decisions made for particular plots of land. These categories are as follows:Auto-RedLine category is for plots created from an automated process using Ordnance Survey MasterMap Topography as a base. Land is not registered under National Highways' name. For example, but not limited to, unregistered ‘ancient’ highway vested in Highways England, or bridge carrying highways over a rail line.NH Title within RedLine category is for plots created from Land Registry Cadastral parcels whose proprietor is National Highways or a predecessor. Land in this category is within the highway boundary (audited) or meets a certain threshold by the algorithm.NH Title outside RedLine category is for plots created in the same way as above but these areas are thought to be outside the highway boundary. Where the Confidence is Low, land in this category is yet to be audited. Where the Confidence is High, land in this category has been reviewed and audited as outside our operational boundary.National Highways (Technician) Data category is for plots created by National Highways, digitised land parcels relating to highway land that is not registered, not yet registered or un-registerable.Road in Tunnel category, created using tunnel outlines from Ordnance Survey MasterMap Topography data. These represent tunnels on Highways England’s network. Land is not registered under National Highways' name, but land above the tunnel may be in National Highways’ title. Please refer to the definitive land ownership records held at HM Land Registry.The process attribute details how the decision was made for the particular plot of land. These are as follows:Automated category denotes data produced by an automated process. These areas are yet to be audited by the company.Audited category denotes data that has been audited by the company.Technician Data (Awaiting Audit) category denotes data that was created by National Highways but is yet to be audited and confirmed as final.The confidence attribute details how confident you can be in the decision. This attribute is derived from both the decisions made during the building of the underlying automated dataset as well as whether the section has been researched and/or audited by National Highways staff. These are as follows:High category denotes land that has a high probability of being within the RedLine boundary. These areas typically are audited or are features that are close to or on the highway.Moderate category denotes land that is likely to be within the highway boundary but is subject to change once the area has been audited.Low category denotes land that is less likely to be within the highway boundary. These plots typically represent Highways England registered land that the automated process has marked as outside the highway boundary.Please note that this dataset is indicative only. For queries about this dataset please contact the GIS and Research Team.

Global Map data are part of a cooperative effort among national mapping organizations around the world to produce and maintain a standard set of basic cartographic data that supports global investigations of natural and human-built environments. Participating nations prepare data using a common data structure and description to ensure compatibility and to tangibly promote the tenets of the Global Spatial Data Infrastructure. These data are intended for geographic display and analysis at the national level, and for large regional areas. The data should be displayed and analyzed at scales appropriate for 1:1,000,000-scale data. No responsibility is assumed by the National Atlas of the United States in the use of these data.

U.S. collision regulation boundaries are lines of demarcation delineating those waters upon which mariners shall comply with the International Regulations for Preventing Collisions at Sea, 1972 (72 COLREGS) and those waters upon which mariners shall comply with the Inland Navigation Rules. The waters inland of these lines are subject to the Inland Navigation Rules Act of 1980. The waters outside these lines are subject to the International Navigation Rules of the International Regulations for Preventing Collisions at Sea, 1972 (COLREGS). The Coast Guard has the legal authority to effect regulatory changes to COLREGS. Creation of features was interpreted from descriptions published in the Code of Federal Regulations Title 33, Part 80.

© MarineCadastre.gov This layer is a component of Navigation and Marine Transportation.

Marine Cadastre themed service for public consumption featuring layers associated with navigation and marine transportation.

This map service presents spatial information about MarineCadastre.gov services across the United States and Territories in the Web Mercator projection. The service was developed by the National Oceanic and Atmospheric Administration (NOAA), but may contain data and information from a variety of data sources, including non-NOAA data. NOAA provides the information “as-is” and shall incur no responsibility or liability as to the completeness or accuracy of this information. NOAA assumes no responsibility arising from the use of this information. The NOAA Office for Coastal Management will make every effort to provide continual access to this service but it may need to be taken down during routine IT maintenance or in case of an emergency. If you plan to ingest this service into your own application and would like to be informed about planned and unplanned service outages or changes to existing services, please register for our Data Services Newsletter (http://coast.noaa.gov/digitalcoast/publications/subscribe). For additional information, please contact the NOAA Office for Coastal Management (coastal.info@noaa.gov).

© MarineCadastre.gov

Village (township) boundaries of each county and city

This layer provides the latest bearing (direction) and/or distance for cadastral boundaries.

When a cadastral survey is undertaken the relationship between boundary and non-boundary marks is ascertained or measured. • This commonly is in the form or a vector (bearing and distance), but occasionally just one component. • Some relationships are defined as arcs. In this data layer, the arc length is recorded in the distance field and a separate record holds the chord.

Only observations that have been captured in Landonline are available. This includes vectors that were re-captured in the Survey Capture Areas from survey plans lodged prior to Landonline and all survey observations since.