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.

description: This data set represents the state (political) boundaries of Mexico. The Digitial Chart of the World data set had incomplete state boundaries, which was the reason to create this coverage. It was digitized from a 1992 CIA map at a scale of 1:3 million. The coast line came from the Digital Chart of the world at a scale of 1:1 million. The state names were labeled from the map and an attribute to help fill the states was added. The labeling process was done manually.; abstract: This data set represents the state (political) boundaries of Mexico. The Digitial Chart of the World data set had incomplete state boundaries, which was the reason to create this coverage. It was digitized from a 1992 CIA map at a scale of 1:3 million. The coast line came from the Digital Chart of the world at a scale of 1:1 million. The state names were labeled from the map and an attribute to help fill the states was added. The labeling process was done manually.

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

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

From the U.S. Census Tiger/Line 2019 Technical Documentation (https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2019/TGRSHP2019_TechDoc.pdf page 3-62): States and equivalent entities are the primary governmental divisions of the United States. In addition to the fifty states, the Census Bureau treats the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the U.S. Virgin Islands) as statistical equivalents of states for the purpose of data presentation. Census regions and divisions consist of groupings of states and equivalent entities. Region and division codes are included in the state shapefiles and users can merge state records to form those areas.

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

This administrative map Germany is a view of the selected administrative units state border, federal states and districts of the Federal Republic of Germany. It is available in the output formats ai, eps and svg.

Overview The Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.4 (published 24 February 2025). The 11.4 release contains updated boundary lines and data refinements designed to extend the functionality of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control. National Geospatial Data Asset This dataset is a National Geospatial Data Asset (NGDAID 194) managed by the Department of State. It is a part of the International Boundaries Theme created by the Federal Geographic Data Committee. Dataset Source Details Sources for these data include treaties, relevant maps, and data from boundary commissions, as well as national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process includes analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground. Cartographic Visualization The LSIB is a geospatial dataset that, when used for cartographic purposes, requires additional styling. The LSIB download package contains example style files for commonly used software applications. The attribute table also contains embedded information to guide the cartographic representation. Additional discussion of these considerations can be found in the Use of Core Attributes in Cartographic Visualization section below. Additional cartographic information pertaining to the depiction and description of international boundaries or areas of special sovereignty can be found in Guidance Bulletins published by the Office of the Geographer and Global Issues: https://data.geodata.state.gov/guidance/index.html Contact Direct inquiries to internationalboundaries@state.gov. Direct download: https://data.geodata.state.gov/LSIB.zip Attribute Structure The dataset uses the following attributes divided into two categories: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | Core CC1_GENC3 | Extension CC1_WPID | Extension COUNTRY1 | Core CC2 | Core CC2_GENC3 | Extension CC2_WPID | Extension COUNTRY2 | Core RANK | Core LABEL | Core STATUS | Core NOTES | Core LSIB_ID | Extension ANTECIDS | Extension PREVIDS | Extension PARENTID | Extension PARENTSEG | Extension These attributes have external data sources that update separately from the LSIB: ATTRIBUTE NAME | ATTRIBUTE STATUS CC1 | GENC CC1_GENC3 | GENC CC1_WPID | World Polygons COUNTRY1 | DoS Lists CC2 | GENC CC2_GENC3 | GENC CC2_WPID | World Polygons COUNTRY2 | DoS Lists LSIB_ID | BASE ANTECIDS | BASE PREVIDS | BASE PARENTID | BASE PARENTSEG | BASE The core attributes listed above describe the boundary lines contained within the LSIB dataset. Removal of core attributes from the dataset will change the meaning of the lines. An attribute status of “Extension” represents a field containing data interoperability information. Other attributes not listed above include “FID”, “Shape_length” and “Shape.” These are components of the shapefile format and do not form an intrinsic part of the LSIB. Core Attributes The eight core attributes listed above contain unique information which, when combined with the line geometry, comprise the LSIB dataset. These Core Attributes are further divided into Country Code and Name Fields and Descriptive Fields. County Code and Country Name Fields “CC1” and “CC2” fields are machine readable fields that contain political entity codes. These are two-character codes derived from the Geopolitical Entities, Names, and Codes Standard (GENC), Edition 3 Update 18. “CC1_GENC3” and “CC2_GENC3” fields contain the corresponding three-character GENC codes and are extension attributes discussed below. The codes “Q2” or “QX2” denote a line in the LSIB representing a boundary associated with areas not contained within the GENC standard. The “COUNTRY1” and “COUNTRY2” fields contain the names of corresponding political entities. These fields contain names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the ‘"Independent States in the World" and "Dependencies and Areas of Special Sovereignty" lists maintained by the Department of State. To ensure maximum compatibility, names are presented without diacritics and certain names are rendered using common cartographic abbreviations. Names for lines associated with the code "Q2" are descriptive and not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS denote independent states. Names rendered in normal text represent dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user. Descriptive Fields The following text fields are a part of the core attributes of the LSIB dataset and do not update from external sources. They provide additional information about each of the lines and are as follows: ATTRIBUTE NAME | CONTAINS NULLS RANK | No STATUS | No LABEL | Yes NOTES | Yes Neither the "RANK" nor "STATUS" fields contain null values; the "LABEL" and "NOTES" fields do. The "RANK" field is a numeric expression of the "STATUS" field. Combined with the line geometry, these fields encode the views of the United States Government on the political status of the boundary line. ATTRIBUTE NAME | | VALUE | RANK | 1 | 2 | 3 STATUS | International Boundary | Other Line of International Separation | Special Line A value of “1” in the “RANK” field corresponds to an "International Boundary" value in the “STATUS” field. Values of ”2” and “3” correspond to “Other Line of International Separation” and “Special Line,” respectively. The “LABEL” field contains required text to describe the line segment on all finished cartographic products, including but not limited to print and interactive maps. The “NOTES” field contains an explanation of special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, limitations regarding the purpose of the lines, or the original source of the line. Use of Core Attributes in Cartographic Visualization Several of the Core Attributes provide information required for the proper cartographic representation of the LSIB dataset. The cartographic usage of the LSIB requires a visual differentiation between the three categories of boundary lines. Specifically, this differentiation must be between: International Boundaries (Rank 1); Other Lines of International Separation (Rank 2); and Special Lines (Rank 3). Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary. Please consult the style files in the download package for examples of this depiction. The requirement to incorporate the contents of the "LABEL" field on cartographic products is scale dependent. If a label is legible at the scale of a given static product, a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field contains the preferred description for the three LSIB line types when they are incorporated into a map legend but is otherwise not to be used for labeling. Use of the “CC1,” “CC1_GENC3,” “CC2,” “CC2_GENC3,” “RANK,” or “NOTES” fields for cartographic labeling purposes is prohibited. Extension Attributes Certain elements of the attributes within the LSIB dataset extend data functionality to make the data more interoperable or to provide clearer linkages to other datasets. The fields “CC1_GENC3” and “CC2_GENC” contain the corresponding three-character GENC code to the “CC1” and “CC2” attributes. The code “QX2” is the three-character counterpart of the code “Q2,” which denotes a line in the LSIB representing a boundary associated with a geographic area not contained within the GENC standard. To allow for linkage between individual lines in the LSIB and World Polygons dataset, the “CC1_WPID” and “CC2_WPID” fields contain a Universally Unique Identifier (UUID), version 4, which provides a stable description of each geographic entity in a boundary pair relationship. Each UUID corresponds to a geographic entity listed in the World Polygons dataset. These fields allow for linkage between individual lines in the LSIB and the overall World Polygons dataset. Five additional fields in the LSIB expand on the UUID concept and either describe features that have changed across space and time or indicate relationships between previous versions of the feature. The “LSIB_ID” attribute is a UUID value that defines a specific instance of a feature. Any change to the feature in a lineset requires a new “LSIB_ID.” The “ANTECIDS,” or antecedent ID, is a UUID that references line geometries from which a given line is descended in time. It is used when there is a feature that is entirely new, not when there is a new version of a previous feature. This is generally used to reference countries that have dissolved. The “PREVIDS,” or Previous ID, is a UUID field that contains old versions of a line. This is an additive field, that houses all Previous IDs. A new version of a feature is defined by any change to the

Northeastern United States 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.)

The USGS Governmental Unit Boundaries dataset from The National Map (TNM) represents major civil areas for the Nation, including States or Territories, counties (or equivalents), Federal and Native American areas, congressional districts, minor civil divisions, incorporated places (such as cities and towns), and unincorporated places. Boundaries data are useful for understanding the extent of jurisdictional or administrative areas for a wide range of applications, including mapping or managing resources, and responding to natural disasters. Boundaries data also include extents of forest, grassland, park, wilderness, wildlife, and other reserve areas useful for recreational activities, such as hiking and backpacking. Boundaries data are acquired from a variety of government sources. The data represents the source data with minimal editing or review by USGS. Please refer to the feature-level metadata ...

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

(Link to Metadata) The BNDHASH dataset depicts Vermont village, town, county, and Regional Planning Commission (RPC) boundaries. It is a composite of generally 'best available' boundaries from various data sources (refer to ARC_SRC and SRC_NOTES attributes). However, this dataset DOES NOT attempt to provide a legally definitive boundary. The layer was originally developed from TBHASH, which was the master VGIS town boundary layer prior to the development and release of BNDHASH. By integrating village, town, county, RPC, and state boundaries into a single layer, VCGI has assured vertical integration of these boundaries and simplified maintenance. BNDHASH also includes annotation text for town, county, and RPC names. BNDHASH includes the following feature classes: 1) BNDHASH_POLY_VILLAGES = Vermont villages 2) BNDHASH_POLY_TOWNS = Vermont towns 3) BNDHASH_POLY_COUNTIES = Vermont counties 4) BNDHASH_POLY_RPCS = Vermont's Regional Planning Commissions 5) BNDHASH_POLY_VTBND = Vermont's state boundary 6) BNDHASH_LINE = Lines on which all POLY feature classes are built The master BNDHASH data is managed as an ESRI geodatabase feature dataset by VCGI. The dataset stores village, town, county, RPC, and state boundaries as seperate feature classes with a set of topology rules which binds the features. This arrangement assures vertical integration of the various boundaries. VCGI will update this layer on an annual basis by reviewing records housed in the VT State Archives - Secretary of State's Office. VCGI also welcomes documented information from VGIS users which identify boundary errors. NOTE - VCGI has NOT attempted to create a legally definitive boundary layer. Instead the idea is to maintain an integrated village/town/county/RPC/state boundary layer which provides for a reasonably accurate representation of these boundaries (refer to ARC_SRC and SRC_NOTES). BNDHASH includes all counties, towns, and villages listed in "Population and Local Government - State of Vermont - 2000" published by the Secretary of State. BNDHASH may include changes endorsed by the Legislature since the publication of this document in 2000 (eg: villages merged with towns). Utlimately the Vermont Secratary of State's Office and the VT Legislature are responsible for maintaining information which accurately describes the locations of these boundaries. BNDHASH should be used for general mapping purposes only. * Users who wish to determine which boundaries are different from the original TBHASH boundaries should refer to the ORIG_ARC field in the BOUNDARY_BNDHASH_LINE (line feature with attributes). Also, updates to BNDHASH are tracked by version number (ex: 2003A). The UPDACT field is used to track changes between versions. The UPDACT field is flushed between versions.

Offshore state lateral boundaries define part of the geographic extent of the submerged lands that a state holds and manages in the public trust. Well-defined boundaries help a state manage its natural resources and statutory obligations with a measured amount of certainty. However, state lateral boundaries, both on land and at sea, have not always been stable and well defined. The historic rec...

Cartographic Boundary Map provided the State of Texas Open Data Portal here: https://data.texas.gov/dataset/Texas-Counties-Cartographic-Boundary-Map/sw7f-2kkd/about_data

Terms of Use This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. It does not represent an on-the-ground survey and represents only the approximate relative location of property boundaries. This product has been provided by the City of Austin via the US Census Bureau for the sole purpose of geographic reference. No warranty is made by the City of Austin regarding specific accuracy or completeness.

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

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.

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.

This shapefile was derived from a predecessor coverage named "IN_LANDSURVEY." IN_LANDSURVEY is a digital representation of land survey features as represented on the USGS 1:24,000 digital raster graphic (DRG) series. ESRI ArcEdit 8.1 and ESRI ArcView 3.2 were used to extract the following shapefiles from IN_LANDSURVEY: LANDSURVEY_COUNTY_LINE_IN, LANDSURVEY_COUNTY_POLY_IN, LANDSURVEY_SECTIONS_LINE_IN, LANDSURVEY_SECTIONS_POLY_IN, LANDSURVEY_STATE_LINE_IN, LANDSURVEY_STATE_POLY_IN, LANDSURVEY_TOWNSHIPS_LINE_IN, and LANDSURVEY_TOWNSHIPS_POLY_IN.NOTE -- This shapefile is identical to a version named "INDIANA_STATEBDY_24K_IGS_L". This metadata file is a copy of the metadata for "INDIANA_STATEBDY_24K_IGS_L" that has had minor edits. The shapefile and metadata were renamed to conform to a file-naming convention for a project funded outside the IGS.

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. 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 generalized boundaries for counties and equivalent entities are based on those as of January 1, 2022, primarily as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

This coverage is of the state boundaries of the conterminous United States. It was derived from the Digital Line Graph (DLG) files representing the 1:2,000,000-scale map in the National Atlas of the United States. Boundaries United States