This map layer portrays the State boundaries of the United States, Puerto Rico, and the U.S. Virgin Islands. The map layer was created by extracting county polygon features from the CENSUS 2006 TIGER/Line files produced by the U.S. Census Bureau. These files were then merged into a single file and county boundaries within States were removed. This is a revised version of the July 2012 map layer.The data and related materials are made available through Esri (http://www.esri.com) and are intended for educational purposes only (see Access and Use Constraints section).

This dataset represents States and equivalent entities, which are the primary governmental divisions of the United States. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. In addition to the fifty States, the Census Bureau treats the District of Columbia, Puerto Rico, and each of the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands) as the statistical equivalents of States for the purpose of data presentation.

Important Note: This item is in mature support as of June 2024 and will retire in December 2026. A new version of this item is available for your use.This layer presents the USA 2020 Census State boundaries of the United States in the 50 states and the District of Columbia. The geography is sourced from US Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrology to add a detailed coastline for cartographic purposes.Attribute fields include 2020 total population from the US Census PL94 data.The boundaries are sourced from US Census TIGER files. These were published in May 2023. A new layer will be published in 12-18 months. Other administrative boundaries for this country are also available: Country County ZIP Code Tract BlockGroup

Three feature layers of Unites States internal state boundaries at different scales: 1:500K, 1:5M, and 1:20M. These layers are intended for use as a cartographic product. It is up to the user to determine which layer is most appropriate for their map.Derived from 2019 US Census Bureau Cartographic Boundary Files for state boundaries using ArcGIS Pro 2.4.3. Process:Original files were downloaded from US Census for the three different scales.Polygons were then converted to lines using the Polygon-to-Line tool.To remove the coastlines, all rows not having a LEFT_FID or RIGHT_FID attribute equal to -1 were then exported to a new geodatabase feature class.The geodatabase was zipped and uploaded to ArcGIS Online.For more information on Cartographic Boundary Files visit https://www.census.gov/programs-surveys/geography/technical-documentation/naming-convention/cartographic-boundary-file.html and https://www.census.gov/geographies/mapping-files/time-series/geo/cartographic-boundary.html.Created by Ryan Davis (RDavis9@cdc.gov) on behalf of CDC/ATSDR/DTHHS/GRASP.

The 2022 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. This file depicts the shape of the United States clipped back to a generalized coastline. This nation layer covers the extent of the fifty states, the District of Columbia, Puerto Rico, and each of the Island Areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands) when scale appropriate.

Abstract Australia's Land Borders is a product within the Foundation Spatial Data Framework (FSDF) suite of datasets. It is endorsed by the ANZLIC – the Spatial Information Council and the Intergovernmental Committee on Surveying and Mapping (ICSM) as the nationally consistent representation of the land borders as published by the Australian states and territories. It is topologically correct in relation to published jurisdictional land borders and the Geocoded National Address File (G-NAF). The purpose of this product is to provide:

a building block which enables development of other national datasets; integration with other geospatial frameworks in support of data analysis; and visualisation of these borders as cartographic depiction on a map.

Although this service depicts land borders, it is not nor does it purport to be a legal definition of these borders. Therefore it cannot and must not be used for those use-cases pertaining to legal context. This foundation dataset consists of edges (polylines) representing mediated segments of state and/or territory borders, connected at the nodes and terminated at the coastline defined as the Mean High Water Mark (MHWM) tidal boundary. These polylines are attributed to convey information about provenance of the source.
It is envisaged that land borders will be topologically interoperable with the future national coastline dataset/s, currently being built through the ICSM coastline capture collaboration program. Topological interoperability will enable closure of land mass polygon, permitting spatial analysis operations such as vector overlay, intersect, or raster map algebra. This feature layer is a sub-layer of the Land Borders service. Currency Date modified: 10 November 2021 Modification frequency: None Data extent Spatial extent North: -14.88° South: -38.06° East: 153.55° West: 129.00° Source information Catalog entry: Australia's Land Borders The Land Borders dataset is created using a range of source data including:

Australian Capital Territory data was sourced from the ACT Government GeoHub – ‘ACT Boundary’. No changes have been made to the polylines or vertices of the source data. In the absence of any custodian published border for Jervis Bay – New South Wales, a border has been constructed from the boundary of the NSW cadastre supplied by NSW Spatial Services. Geoscience Australia’s GEODATA TOPO 250K data was considered as an alternative, however, that border terminated short of the coastline as it stops at the shoreline of the major water bodies. Therefore, a decision was made to use the NSW and OT supplied cadastre to create a new representation of the Jervis Bay border that continued to the coastline (MHWM), in place of the TOPO 250K data. In the absence of publicly available data from New South Wales, the land borders for New South Wales have been constructed using the data of adjoining states Queensland, South Australia, Victoria and the Australian Capital Territory. This approach is agreeable to New South Wales Government for this interim product. In the absence of publicly available data from the Northern Territory the land borders for the Northern Territory have been constructed using the data of adjoining states Western Australia, Queensland and South Australia. This approach is agreeable to Northern Territory Government for this interim product. Queensland state border and coastline data have been download from the Queensland Spatial, Catalogue – QSpatial. Publicly available data for the state borders of South Australia was downloaded from data.gov.au and is ‘SA State Boundary - PSMA Administrative Boundaries’. Downloaded as a file geodatabase in GDA2020. Victorian state border data has been downloaded from the Victorian state Government Spatial Datamart, it is titled ‘FR_FRAMEWORK_AREA_LINE’. The Victorian state border data was used for the NSW/VIC section of border due to the absence of any publicly available data from New South Wales for this section of the border. Western Australian state border data was downloaded from the WA Government as publicly available. The Western Australia state border data has been used for the WA/NT section of the border due to the absence of publicly available data from Northern Territory for this section of the border. Selecting the SA data for the WA/SA border would introduce mismatches with the WA cadastre. It would also not improve the SA relationship with the SA cadastre. Using the WA data for the WA/SA section of the border aligns each state with its own cadastre without causing overlaps.

Lineage statement At the southwest end of the NT/SA/WA border the South Australian data for the border was edited by moving the end vertex ~1.7m to correctly create the intersection of the 3 states (SA/WA/NT). At the southeast end of the NT/QLD/SA border the South Australian data for the border was edited by moving the end vertex ~0.4m to correctly create the intersection of the 3 states (NT/SA/QLD). Queensland data was used for the NT/QLD border and the QLD/NSW border due to the absence of publicly available data from the Northern Territory for these section of the border. Data published by Queensland also included a border sections running westwards along the southern Northern Territory border and southwards along the western New South Wales border. These two sections were excluded from the product as they are not within the state of Queensland. Queensland data was also used in the entirety for the SA/QLD segment of the land borders. Although the maximum overlap between SA and QLD state border data was less than ~5m (and varied along the border), the Queensland data closely matched its own cadastre and that of South Australia. The South Australian data overlapped the Queensland data, it also did not match the South Australian cadastre. Therefore, a decision to use the Queensland data for the QLD/SA section of the border ensured the best possible topological consistency with the published cadastre of each state. The South Australian/Victorian state border, north-south, were generally very similar with some minor deviations from each other from less than 1m to ~60m (there is one instance of deviation of 170m). The section of border that follows the Murray River is matched, for the most part by both states. Over three quarters of the border running along the river is matched with both states. There is a mismatch between the states in the last quarter of the border along the river, the northern section, however, both states still have the border running inside, or along, the river polygon (Surface hydrology), the Victorian data was chosen for this section purely for consistency as the Victorian data was used for the preceding arcs. Overall, the Victorian data was selected for use as the South Australia/Victoria land border. After taking the existing cadastre and GNAF points into account and it did not introduce extra errors into the relationship between the land borders and the cadastre of either state. In parts, it improved the relationship between the South Australian cadastre and the SA/VIC state border. This interim product will be updated when all states and territories have published agreed, authoritative representations of their land borders. This product will also be updated to include land mass polygons at time when the Coastline Capture Program is complete. This dataset is GDA 2020 compliant - transformed into GDA2020 from it's original source datum. Reference System Code 2020.00. Data dictionary All layers

Attribute name Description

COMMENT Legal disclaimer for the positional data

CREATED Date on which the positional data point was created in the data set

CUSTODIAN Department or jurisdiction from which the data point information is derived

DATE_DOWNLOADED Date on which the positional data point was created in the data set

FEATURE_TYPE All features in this data set are labelled "STATE BORDER"

LAST_UPDAT_FROM_SOURCE Date on which the positional data point was refreshed from source data

METADATA_LINK External link to metadata from the data source

SOURCE_DATA External link to metadata from the data source

SOURCE_STATE State or Territory which hosts the data source

STATE Land borders divide exactly two states and/or territories

STATEMENT Legal disclaimer for the positional data

Contact Geoscience Australia, clientservices@ga.gov.au

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 Advanced Weather Interactive Processing System (AWIPS) uses shapefiles for base maps in the system. These shapefiles contain boundaries of areas used by NWS for forecasts and warnings as well as map backgrounds.NWS BordersThe County Warning Area boundaries are the counties/zones for which each Weather Forecast Office (WFO) is responsible for issuing forecasts and warnings. The shapefile was created by aggregating public zones with the same CWA designation into a single polygon and manually adjusting the boundaries of the exceptions to the rule.The NWS county and state borders are background map used internally in NWS.Coastal Marine Zone ForecastThis map layer contains links to NWS marine weather forecasts for coastal or nearshore waters within 20nm of shore out to Day 5. It includes predictions on the likelihood of precipitation and/or reduced visibility, surface wind direction and speed, seas or combined seas, and icing. Air temperature forecasts are optional. The forecasts will also include any marine weather advisories, watches, and/or warnings. The purpose of the forecasts is to support and promote safe transportation across the coastal waters. The forecasts are issued twice per day with updates as necessary by NWS Weather Forecast Offices (WFOs) along the coast and Great Lakes.Offshore Zone ForecastsThis map layer contains links to NWS marine weather forecasts for offshore waters beyond 20 or 30nm of shore out to Day 5. The forecast provides information to mariners who travel on the oceanic waters adjacent to the U.S., its territorial coastal waters and the Caribbean Sea. The forecasts include predictions on the likelihood of precipitation and/or reduced visibility, surface wind direction and speed, seas and likelihood of icing out to Day 5 along with information about any warnings. The offshore forecasts for the Western North Atlantic and Eastern North Pacific Oceans are produced by NWS/NCEP's Ocean Prediction Center. The offshore forecasts for the Gulf of Mexico and Caribbean Sea are issued by the NWS/NCEP National Hurricane Center's Tropical Analysis and Forecast Branch (TAFB). OPC and NHC/TAFB issues the forecasts four times daily at regular intervals, with updates when necessary. The offshore forecast for the waters around Hawaii are issued by the NWS Weather Forecast Office in Honolulu, HI four times daily at regular intervals, with updates when necessary. The offshore forecasts for Alaska waters in the Bering Sea and Gulf of Alaska are issued by NWS Weather Forecast Offices in Alaska at least twice a day with updates as necessary. The WFOs in Alaska include WFO Anchorage, WFO Fairbanks, and WFO Juneau.Public Weather Zone ForecastsThis layer includes links to NWS web pages posting the latest NWS surface weather forecasts, a zone-type forecast providing the average forecast conditions across the zone, usually at the county-scale or sub-county scale. These text forecasts include predictions of weather, sky cover, maximum and minimum surface air temperatures, surface wind direction and speed, and probability of precipitation out to 7 days into the future. In addition, the forecast highlights at the top include any active weather advisories, watches, and/or warnings. These zone predictions are derived from gridded forecasts created by NWS Weather Forecast Offices throughout the U.S. The text weather forecasts are usually issued in the early morning (e.g. 4AM LT) and early evening (4PM LT). They are updated during late mornings and late night and during fast changing weather conditions.Fire Weather Zone ForecastsThis layer includes links to NWS web pages posting the latest NWS Fire Weather Planning Forecasts, a zone-type forecast providing the average fire weather conditions across the zone. According to the NWS, the forecast is "used by land management personnel primarily for input in decision-making related to pre-suppression and other planning." The forecast is valid from the time of issuance through day five and sometimes through day seven and usually has a minimum of three 12-hour time periods. The forecast will have included a discussion of weather patterns affecting the forecast zone or area, identification of any active fire weather watches/warnings and a table of predicted fire weather variables for the next two days: 1) sky/weather conditions, 2) max/min air temperatures, 3) max/min relative humidity, 4) 0-minute average wind direction/speed at 20 feet and sometimes at another height (e.g. 10,000, 15,000 ft), 5) precipitation amount, duration, and timing, 6) mixing height, 7) transport winds, 8) vent category, and 9) several fire weather indices such as Haines Index, Lightning Activity (LAL), Chance of Wetting Rainfall (CWR), Dispersion Index, Low Visibility Occurrence Risk Index (LVORI), and Max LVORI. In addition, it will usually have a forecast in plain text for days 3 to 7. Sometimes an optional outlook of expected conditions for day 6 or possibly for day 6 and 7 is expected. The forecasts are issued by NWS WFOs at least once daily during the local fire season.Metadata:CWA: https://www.weather.gov/gis/CWAmetadataCoastal Marine: https://www.weather.gov/gis/CoastalMarineMetadataOffshore: https://www.weather.gov/gis/OffshoreZoneMetadataPublic Zones: https://www.weather.gov/gis/PublicZoneMetadataFire Zones: https://www.weather.gov/gis/FireZoneMetadataCounties: https://www.weather.gov/gis/CountyMetadataStates: https://www.weather.gov/gis/StateMetadataLink to data download: https://www.weather.gov/gis/AWIPSShapefilesQuestions/Concerns about the service, please contact the DISS GIS teamTime Information:This service is not time enabled

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri, Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for counties and equivalent entities are as of January 1, 2017, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

Connecticut and Vicinity 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 "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

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 2019 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. Regions are four groupings of states (Northeast, South, Midwest, and West) established by the Census Bureau in 1942 for the presentation of census data.

This dataset portrays the Western State's boundaries based on the 2010 Cadastral National Spatial Data Infrastructure (CADNSDI) Geographic Coordinate Data Base (GCDB) distribution. The GCDB was acquired from a Premier Data contract in coordination with the BLM state GCDB Data Stewards to deliver a standardized GCDB product. This product would be capable, where GCDB data exists, to identify the State borders. Where GCDB data does not exist, in cases or rivers, lakes, and unsurveyed terrain, then alternative sources were used to identify the state boundary. Alternative sources include original 24K USGS Maps and US Forest Service Cartographic Feature File (CFF) PLSS data.

This web map created by the Colorado Governor's Office of Information Technology GIS team, serves as a basemap specific to the state of Colorado. The basemap includes general layers such as counties, municipalities, roads, waterbodies, state parks, national forests, national wilderness areas, and trails.Layers:Layer descriptions and sources can be found below. Layers have been modified to only represent features within Colorado and are not up to date. Layers last updated February 23, 2023. Colorado State Extent: Description: “This layer provides generalized boundaries for the 50 States and the District of Columbia.” Notes: This layer was filtered to only include the State of ColoradoSource: Esri Living Atlas USA States Generalized Boundaries Feature LayerState Wildlife Areas:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state wildlife areas layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer hosted in ArcGIS Online Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerMunicipal Boundaries:Description: "Boundaries data from the State Demography Office of Colorado Municipalities provided by the Department of Local Affairs (DOLA)"Source: Colorado Information Marketplace Municipal Boundaries in ColoradoCounties:Description: “This layer presents the USA 2020 Census County (or County Equivalent) boundaries of the United States in the 50 states and the District of Columbia. It is updated annually as County (or County Equivalent) boundaries change. The geography is sources from US Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrology to add a detailed coastline for cartographic purposes. Geography last updated May 2022.” Notes: This layer was filtered to only include counties in the State of ColoradoSource: Esri USA Census Counties Feature LayerInterstates:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: Interstates are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointU.S. Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: U.S. Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointState Highways:Description: Authoritative data from the Colorado Department of Transportation representing Highways Notes: State Highways are filtered by route sign from this CDOT Highways layer Source: Colorado Department of Transportation Highways REST EndpointMajor Roads:Description: Authoritative data from the Colorado Department of Transportation representing major roads Source: Colorado Department of Transportation Major Roads REST EndpointLocal Roads:Description: Authoritative data from the Colorado Department of Transportation representing local roads Source: Colorado Department of Transportation Local Roads REST EndpointRail Lines:Description: Authoritative data from the Colorado Department of Transportation representing rail lines Source: Colorado Department of Transportation Rail Lines REST EndpointCOTREX Trails:Description: “The Colorado Trail System, now titled the Colorado Trail Explorer (COTREX), endeavors to map every trail in the state of Colorado. Currently their are nearly 40,000 miles of trails mapped. Trails come from a variety of sources (USFS, BLM, local parks & recreation departments, local governments). Responsibility for accuracy of the data rests with the source.These data were last updated on 2/5/2019” Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerNHD Waterbodies:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include waterbodies in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerNHD Flowlines:Description: “The National Hydrography Dataset Plus (NHDplus) maps the lakes, ponds, streams, rivers and other surface waters of the United States. Created by the US EPA Office of Water and the US Geological Survey, the NHDPlus provides mean annual and monthly flow estimates for rivers and streams. Additional attributes provide connections between features facilitating complicated analyses.”Notes: This layer was filtered to only include flowline features in the State of ColoradoSource: National Hydrography Dataset Plus Version 2.1 Feature LayerState Parks:Description: “This data was created by the CPW GIS Unit. Property boundaries are created by dissolving CDOWParcels by the property name, and property type and appending State Park boundaries designated as having public access. All parcel data correspond to legal transactions made by the CPW Real Estate Unit. The boundaries of the CDOW Parcels were digitized using metes and bounds, BLM's GCDB dataset, the PLSS dataset (where the GCDB dataset was unavailable) and using existing digital data on the boundaries.” Notes: The state parks layer in this basemap is filtered from the CPW Managed Properties (public access only) layer from this feature layer Source: Colorado Parks and Wildlife CPW Admin Data Feature LayerDenver Parks:Description: "This dataset should be used as a reference to locate parks, golf courses, and recreation centers managed by the Department of Parks and Recreation in the City and County of Denver. Data is based on parcel ownership and does not include other areas maintained by the department such as medians and parkways. The data should be used for planning and design purposes and cartographic purposes only."Source: City and County of Denver Parks REST EndpointNational Wilderness Areas:Description: “A parcel of Forest Service land congressionally designated as wilderness such as National Wilderness Area.”Notes: This layer was filtered to only include National Wilderness Areas in the State of ColoradoSource: United States Department of Agriculture National Wilderness Areas REST EndpointNational Forests: Description: “A depiction of the boundaries encompassing the National Forest System (NFS) lands within the original proclaimed National Forests, along with subsequent Executive Orders, Proclamations, Public Laws, Public Land Orders, Secretary of Agriculture Orders, and Secretary of Interior Orders creating modifications thereto, along with lands added to the NFS which have taken on the status of 'reserved from the public domain' under the General Exchange Act. The following area types are included: National Forest, Experimental Area, Experimental Forest, Experimental Range, Land Utilization Project, National Grassland, Purchase Unit, and Special Management Area.”Notes: This layer was filtered to only include National Forests in the State of ColoradoSource: United States Department of Agriculture Original Proclaimed National Forests REST Endpoint

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.

World Countries Generalized represents generalized boundaries for the countries of the world as of August 2022. The generalized political boundaries improve draw performance and effectiveness at a global or continental level. This layer is best viewed out beyond a scale of 1:5,000,000.This layer's geography was developed by Esri and sourced from Garmin International, Inc., the U.S. Central Intelligence Agency (The World Factbook), and the National Geographic Society for use as a world basemap. It is updated annually as country names or significant borders change.

description: This dataset portrays the state boundary based on the 2010 Cadastral National Spatial Data Infrastructure (CADNSDI) Geographic Coordinate Data Base (GCDB) distribution. The GCDB was acquired from a Premier Data contract in coordination with the BLM state GCDB Data Stewards to deliver a standardized GCDB product. This product would be capable, where GCDB data exists, to identify the State borders. Where GCDB data does not exist, in cases or rivers, lakes, and unsurveyed terrain, then alternative sources were used to identify the state boundary. Alternative sources include original 24K USGS Maps and US Forest Service Cartographic Feature File (CFF) PLSS data.; abstract: This dataset portrays the state boundary based on the 2010 Cadastral National Spatial Data Infrastructure (CADNSDI) Geographic Coordinate Data Base (GCDB) distribution. The GCDB was acquired from a Premier Data contract in coordination with the BLM state GCDB Data Stewards to deliver a standardized GCDB product. This product would be capable, where GCDB data exists, to identify the State borders. Where GCDB data does not exist, in cases or rivers, lakes, and unsurveyed terrain, then alternative sources were used to identify the state boundary. Alternative sources include original 24K USGS Maps and US Forest Service Cartographic Feature File (CFF) PLSS data.

This dataset represents the international boundary between Canada and the United States.

This shapefile is a digital representation of the International boundary between the United States and Canada as per the Treaty of 1908. It has been generated from a combination of recent surveys and datum conversions. It is intended for mapping purposes only.

Analysis of ‘Northeast State Lines’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/c289af13-58b6-49b2-a1ff-f344e657ca0a on 27 January 2022.

--- Dataset description provided by original source is as follows ---

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

--- Original source retains full ownership of the source dataset ---