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

The "Map Image Layer - Watershed Boundaries" is the Map Image Layer of Watershed 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 Watershed Boundaries Data Group contains the following layers: DNR Catchments (MnDNR)HUC 12 Boundaries (USGS)HUC 12 IWM Group Boundaries (MPCA)HUC 10 Boundaries (USGS)HUC 8 Boundaries (USGS): HUC 8s represent part or all of a surface drainage basin, a combination of drainage basins, or a distinct hydrologic feature. There are 80 HUC 2s in Minnesota. (i.e. Zumbro (07040004))HUC 6 Boundaries (USGS): HUC 6s are areas which divide the subregions into more than 350 hydrologic accounting units. Minnesota has 17 of the nations hydrologic accounting units: Northwestern Lake Superior (040101), St. Louis (040102), Southwestern Lake Superior (040103), Mississippi Headwaters (070101), Upper Mississippi-Crow-Rum (070102), Minnesota (070200), St. Croix (070300), Upper Mississippi-Black-Root (070400), Upper Mississippi-Maquoketa-Plum (070600), Upper Mississippi-Skunk-Wapsipinicon (070801), Iowa (070802), Des Moines (071000), Upper Red (090201), Lower Red (090203), Rainy (090300), Big Sioux (101702), Missouri-Little Sioux (102300).HUC 4 Boundaries (USGS): HUC 4s are geographic subregions which are drained by a river system, a reach of river and its tributaries in that reach, a closed basin, or a group of streams forming a coastal drainage areas. Minnesota has 12 of the nations 222 subregions: Western Lake Superior (0401), Mississippi Headwaters (0701), Minnesota (0702), St. Croix (0703), Upper Mississippi-Black-Root (0704), Upper Mississippi-Maquoketa-Plum (0706), Upper Mississippi-Iowa-Skunk-Wapsipinicon (0708), Des Moines (0710), Red (0902), Rainy (0903), Missouri-Big Sioux (1017), Missouri-Little Sioux (1023).HUC 2 Boundaries (USGS): HUC 2s are geographic regions which contain the drainage of a major river or a series of rivers. Minnesota has 4 of the nations 21 regions: Great Lakes (R04), Upper Mississippi (R07), Souris-Red-Rainy (R09), and Missouri (R10).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 Watershed Boundary Dataset please see:United States Geological Survey Water-Supply Paper 2294: https://pubs.usgs.gov/wsp/wsp2294/Hydrologic Units, The National Atlas of the United State of America: https://pubs.usgs.gov/gip/hydrologic_units/pdf/hydrologic_units.pdfNational Hydrography Dataset, Watershed Boundary Dataset: https://www.usgs.gov/core-science-systems/ngp/national-hydrography/watershed-boundary-dataset

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.

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.

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

Village (Neighborhood) Boundaries across the Nation

Connecticut and Vicinity Town Boundary data are intended for geographic display of state, county and town (municipal) boundaries at statewide and regional levels. Use it to map and label towns on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

Public view of the parcel layer. This view is limited to only the attributes that can be seen by the general public.The data table includes the following fields: Shape Type (Shape), Shape.STArea() (Shape_Area), Shape.STLength() (Shape_Area), Name (APN), Created By Record (CreatedbyR), Retired By Record (RetiredbyR), Stated Area, Stated Area Unit (StatedAr_1), Calculated Area (Calculated), Misclose Ratio (MiscloseRa), Misclose Distance (MiscloseDi), Is Seed (IsSeed), Created By (created_us), Created Date (created_da), Modified By (last_edite), Modified Date (last_edi_1), Validation Status (VALIDATION), APN Dashed (APN_Dashed), Map Page (Map_Page), Municipality (Municipali), FloorOrder, HideThere are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.

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.

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

Digital line graph (DLG) data are digital representations of cartographic information. DLGs of map features are converted to digital form from maps and related sources. Intermediate-scale DLG data are derived from USGS 1:100,000-scale 30- by 60-minute quadrangle maps. If these maps are not available, Bureau of Land Management planimetric maps at a scale of 1:100,000 are used. Intermediate-scale DLGs are sold in five categories: (1) Public Land Survey System; (2) boundaries; (3) transportation; (4) hydrography; and (5) hypsography. All DLG data distributed by the USGS are DLG-Level 3 (DLG-3), which means the data contain a full range of attribute codes, have full topological structuring, and have passed certain quality-control checks.

Northeastern United States State Boundary data are intended for geographic display of state boundaries at statewide and regional levels. Use it to map and label states on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

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)" "Standard" (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 Cari ...

Connecticut and Vicinity County Boundary data are intended for geographic display of state and county boundaries at statewide and regional levels. Use it to map and label counties on a map. These data are derived from Northeastern United States Political Boundary Master layer. This information should be displayed and analyzed at scales appropriate for 1:24,000-scale data. The State of Connecticut, Department of Environmental Protection (CTDEP) assembled this regional data layer using data from other states in order to create a single, seamless representation of political boundaries within the vicinity of Connecticut that could be easily incorporated into mapping applications as background information. More accurate and up-to-date information may be available from individual State government Geographic Information System (GIS) offices. Not intended for maps printed at map scales greater or more detailed than 1:24,000 scale (1 inch = 2,000 feet.)

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 Sure! Here's the reformatted list as requested:

Afghanistan, Angola, Bangladesh, Burkina Faso, Burundi, Cambodia, Cameroon, Central African Republic, Chad, Colombia, Comoros, Democratic Republic of the Congo, Ecuador, El Salvador, Federated States of Micronesia, Ghana, Guatemala, Haiti, Honduras, Iraq, Kingdom of Tonga, Kiribati, Kyrgyzstan, Lao People's Democratic Republic, Lebanon, Liberia, Libya, Madagascar, Malawi, Mali, Mauritania, Mozambique, Myanmar, Namibia, Nepal, Niger, Nigeria, Pakistan, Palestine, Philippines, Republic of the Marshall Islands, Saint Lucia, Samoa, Senegal, Sierra Leone, Solomon Islands, Somalia, South Sudan, Sri Lanka, Sudan, Suriname, Syrian Arab Republic, Tajikistan, Thailand, Timor-Leste, Togo, Tuvalu, Uganda, Ukraine, Venezuela, Vietnam, Yemen, and Zimbabwe.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.

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.

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.

This web map provides provides a customized world basemap that is uniquely symbolized. It is optimized to display special areas of interest (AOIs) that have been created and edited by Community Maps contributors. These special areas of interest include landscaping features such as grass, trees, and rock and sports amenities like tennis courts, football and baseball field lines, and more. This vector tile layer is built using the same data sources used for the World Topographic Map and other Esri basemaps. Alignment of boundaries is a presentation of the feature provided by our data vendors and does not imply endorsement by Esri or any governing authority.Use this MapThis map is designed to be used as a basemap for overlaying other layers of information or as a stand-alone reference map. You can add layers to this web map and save as your own map. If you like, you can add this web map to a custom basemap gallery for others in your organization to use in creating web maps. If you would like to add this map as a layer in other maps you are creating, you may use the Community tile layer referenced in this map.Customize this MapBecause this map includes a vector tile layer, you can customize the map to change its content and symbology. You are able to turn on and off layers, change symbols for layers, switch to alternate local language (in some areas), and refine the treatment of disputed boundaries. For details on how to customize this map, please refer to the Esri Vector Basemap Reference Document (v2) and vector basemap articles on the ArcGIS Online Blog.Fonts available for use in the style resource directory are under the OFL, Open Font License.This map was designed and created by Cindy Prostak.

This polygon files contains 2015-2016 school-year data delineating school attendance boundaries. These data were collected and processed as part of the School Attendance Boundary Survey (SABS) project which was funded by NCES to create geography delineating school attendance boundaries. Original source information that was used to create these boundary files were collected were collected over a web-based self-reporting system, through e-mail, and mailed paper maps. The web application provided instructions and assistance to users via a user guide, a frequently asked questions document, and instructional videos. Boundaries supplied outside of the online reporting system typically fell into one of six categories: a digital geographic file, such as a shapefile or KML file; digital image files, such as jpegs and pdfs; narrative descriptions; an interactive web map; Excel or pdf address lists; and paper maps. 2015 TIGER/line features (that consist of streets, hydrography, railways, etc.) were used to digitize school attendance boundaries and was the primary source of information used to digitize analog information. This practice works well as most school attendance boundaries align with streets, railways, water bodies and similar line features included in the 2015 TIGER/line "edges" files. In those few cases in which a portion of a school attendance boundary serves both sides of a street contractor staff used Esri’s Imagery base map to estimate the property lines of parcels. The data digitized from analog maps and verbal descriptions do not conform to cadastral data (and many of the original GIS files created by school districts do not conform with cadastral or parcel data).The SABS 2015-2016 file uses the WGS 1984 Web Mercator Auxiliary Sphere coordinate system.Additional information about SABS can be found on the EDGE website.The SABS dataset is intended for research purposes only and reflects a single snapshot in time. School boundaries frequently change from year to year. To verify legal descriptions of boundaries, users must contact the school district directly.All information contained in this file is in the public domain. Data users are advised to review NCES program documentation and feature class metadata to understand the limitations and appropriate use of these data.

Abstract copyright UK Data Service and data collection copyright owner.

This research project aimed to fill a major lacuna militating against the effective exploitation of many post-medieval to mid-Victorian historical sources collected by local administrative areas: the lack of information on the boundaries of those administrative areas, the so-called 'historic' or 'ancient' parishes of England and Wales. It is known that these districts came into being during the Middle Ages, that the map of these ecclesiastical parishes was essentially complete by the fifteenth century, that these ecclesiastical boundaries were adopted during the early modern period for secular and judicial purposes, and that boundaries remained essentially unchanged until a number of reforms from the mid-nineteenth century onwards reorganised the local administrative geography of the country. The project aimed to reconstruct those boundaries as they were before the post-nineteenth century changes.
Main Topics:

The digitised maps cover the whole of England and Wales, and are organised by Ordnance Survey Sheet number. The maps contain a scanned bitmap image of the Ordnance Survey one inch to one mile (1:63,360) New Popular Edition maps (1945-8) with National Grid. They contain the boundaries of some 18,233 places, and are arranged as three electronic 'layers'. The first is a scan of the Ordnance Survey maps stored as grey tone sheet images. This enables Ordnance Survey physical, cultural and place-name content to be readily visible in the background for orientation and general location purposes, while not obscuring the added boundary and reference number material. The second layer consists of the boundaries, stored as solid red lines; and the third layer contains the reference numbers that link places on the map to the gazetteer/metadata dataset that accompanies the maps.

The maps are available on CD-ROM in Adobe Illustrator (ISBN:0-9540032-2-5) or Adobe Acrobat (ISBN:0-9540032-1-7) PDF formats. We recommend using the Adobe Illustrator format if you already have the software (as it enables you to edit the maps and select the layers to view). However, the Adobe Acrobat PDF format is perfectly suitable for viewing the maps, and we will supply the necessary reader software.

An accompanying book Historic Parishes of England and Wales: An Electronic Map of Boundaries before 1850 with a Gazetteer and Metadata by Roger Kain and Richard Oliver (ISBN:0-9540032-0-9) provides an introduction to the provenance of the maps. It also includes an abbreviated version of the gazetteer/metadata dataset, and a discussion of historical boundaries.

This unique combination publication is set to become a standard reference resource and is an invaluable tool for all those interested in plotting local area-based data from the past (population, agricultural, statistics, tax data etc.) from the fourteenth to the nineteenth centuries.

Please note: this study does not include information on named individuals and would therefore not be useful for personal family history research.