This feature service includes change areas for city boundaries and county line adjustments filed in accordance with Government Code 54900. The boundaries in this map are based on the State Board of Equalization's tax rate area maps for the assessment roll year specified in the COFILE field. The information is updated regularly within 10 business days of the most recent BOE acknowledgement date. Some differences may occur between actual recorded boundaries and boundary placement in the tax rate area GIS map. Tax rate area boundaries are representations of taxing jurisdictions for the purpose of determining property tax assessments and should not be used to determine precise city or county boundary line locations. BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number; CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance; RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES: additional clarifying information about the action. BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the BOE's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

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 for information on the data source. The National Map boundaries data is commonly combined with other data themes, such as elevation, hydrography, structures, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain boundaries data in either Esri File Geodatabase or Shapefile formats. For additional information on the boundaries data model, go to https://nationalmap.gov/boundaries.html.

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

This map includes change areas for city and county boundaries filed in accordance with Government Code 54900. The initial dataset was first published on October 20, 2021, and was based on the State Board of Equalization's tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax jurisdictions. The boundaries are continuously being revised when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions and should not be used to determine precise city or county boundary line locations.The data is updated within 10 business days of the CDTFA receiving a copy of the Board of Equalization's acknowledgement letter.BOE_CityAnx Data Dictionary: COFILE = county number - assessment roll year - file number (see note*); CHANGE = affected city, unincorporated county, or boundary correction; EFFECTIVE = date the change was effective by resolution or ordinance (see note*); RECEIVED = date the change was received at the BOE; ACKNOWLEDGED = date the BOE accepted the filing for inclusion into the tax rate area system; NOTES = additional clarifying information about the action.*Note: A COFILE number ending in "000" is a boundary correction and the effective date used is the date the map was corrected.BOE_CityCounty Data Dictionary: COUNTY = county name; CITY = city name or unincorporated territory; COPRI = county number followed by the 3-digit city primary number used in the Board of Equalization's 6-digit tax rate area numbering system (for the purpose of this map, unincorporated areas are assigned 000 to indicate that the area is not within a city).

This map service contains the most current version of the USGS Watershed Boundary Dataset (WBD) from The National Map (TNM). The WBD defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. These drainage areas or Hydrologic Unit (HU) polygon boundaries are available for the United States, Puerto Rico, and the U.S. Virgin Islands. The drainage areas are nested within each other so that a large drainage area, such as the Upper Mississippi River, will be composed of multiple smaller drainage areas, such as the Wisconsin River. Each of these smaller areas can further be subdivided into smaller and smaller drainage areas. The WBD uses six different levels in this hierarchy, with the smallest averaging about 30,000 acres. The WBD is made up of polygons nested into six levels of data respectively defined by Regions, Subregions, Basins, Subbasins, Watersheds, and Subwatersheds.The data is a seamless National representation of HU boundaries from 2 to 14 digits compiled from U.S. Geological Survey (USGS) National Hydrography Dataset (NHD) and U.S. Department of Agriculture (USDA) National Resources Conservation Service (NRCS) Watershed Boundary Dataset (WBD) sources. Purpose: This data is intended primarily for geographic display and analysis of regional and national data, and can also be used for illustration purposes at intermediate or small scales (1:250,000 to 1:2,000,000). For additional information on the WBD, go to https://nhd.usgs.gov/wbd.html.

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

This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.

This layer contains Legal City boundaries within Los Angeles County. The Los Angeles County Department of Public Works provides the most current shape file of these city boundaries for download at its Spatial Information Library.Note: This boundary layer will not line up with the Thomas Brothers city layer. Principal attributes include:CITY_NAME: represents the city's name.CITY_TYPE: may be used for definition queries; "Unincorporated" or "City".FEAT_TYPE: contains the type of feature each polygon represents:Land - Use this value for your definition query if you want to see only land features on your map.Pier - One example is the Santa Monica Pier. Man-made features may be regarded as extensions of the coastline.Breakwater - Examples include the breakwater barriers that protect the Los Angeles Harbor.Water - Polygons with this attribute value represent internal navigable waters. Examples of internal waters are found in the Long Beach Harbor and in Marina del Rey.3NM Buffer - Per the Submerged Lands Act, the seaward boundaries of coastal cities and unincorporated county areas are three nautical miles (a nautical mile is 1852 meters) from the coastline.

In late 1996, the Dept of Conservation (DOC) surveyed state and federal agencies about the county boundary coverage they used. As a result, DOC adopted the 1:24,000 (24K) scale U.S. Bureau of Reclamation (USBR) dataset (USGS source) for their Farmland Mapping and Monitoring Program (FMMP) but with several modifications. Detailed documentation of these changes is provided by FMMP and included in the lineage section of the metadata.A dataset was made available (approximately 2004) through CALFIRE - FRAP and the California Spatial Information Library (CaSIL), with additional updates throughout subsequent years. More recently, an effort was made to improve the coastal linework by using the previous interior linework from the 24k data, but replacing the coastal linework based on NOAA's ERMA coastal dataset (which used NAIP 2010). In this dataset, all bays (plus bay islands and constructed features) are merged into the mainland, and coastal features (such as islands and constructed features) are not included, with the exception of the Channel Islands which ARE included.This service represents the latest released version, and is updated when new versions are released. As of June, 2019 it represents cnty19_1.

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.

This city boundary shapefile was extracted from Esri Data and Maps for ArcGIS 2014 - U.S. Populated Place Areas. This shapefile can be joined to 500 Cities city-level Data (GIS Friendly Format) in a geographic information system (GIS) to make city-level maps.

Polygon vector map data covering boundaries for the City of Los Angeles containing 4 features.

Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features. This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.

Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.

Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.

​

Publication Date: May 2025. Updated as needed. Current as of the Publication Date. The data can be downloaded here: https://gis.ny.gov/civil-boundaries#about-civil-boundaries. This feature service has polygon layers for the following boundary types: State, Counties, Cites, Towns, Cities and Towns combined, Villages, and Indian Territories. In addition, there are separate shoreline layers for the State layer and the County layer. Boundaries are at 1:24,000-scale positional accuracy except for the shoreline in State Shoreline and Counties Shoreline which is being adjusted to 1:24,000-scale positional accuracy as part of ongoing work. Boundary changes are made as needed and based on authoritative sources. See metadata for each layer for additional information. This map service is available to the public. The State of New York, acting through the New York State Office of Information Technology Services, makes no representations or warranties, express or implied, with respect to the use of or reliance on the Data provided. The User accepts the Data provided “as is” with no guarantees that it is error free, complete, accurate, current or fit for any particular purpose and assumes all risks associated with its use. The State disclaims any responsibility or legal liability to Users for damages of any kind, relating to the providing of the Data or the use of it. Users should be aware that temporal changes may have occurred since this Data was created.

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.

Village (township) boundaries of each county and city

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

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 Watershed Boundary Dataset (WBD) from The National Map (TNM) defines the perimeter of drainage areas formed by the terrain and other landscape characteristics. The drainage areas are nested within each other so that a large drainage area, such as the Upper Mississippi River, will be composed of multiple smaller drainage areas, such as the Wisconsin River. Each of these smaller areas can further be subdivided into smaller and smaller drainage areas. The WBD uses six different levels in this hierarchy, with the smallest averaging about 30,000 acres. The WBD is made up of polygons nested into six levels of data respectively defined by Regions, Subregions, Basins, Subbasins, Watersheds, and Subwatersheds. For additional information on the WBD, go to https://nhd.usgs.gov/wbd.html. The USGS National Hydrography Dataset (NHD) service is a companion dataset to the WBD. The NHD is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of surface water (lakes, ponds, and reservoirs), paths through which water flows (canals, ditches, streams, and rivers), and related entities such as point features (springs, wells, stream gages, and dams). The information encoded about these features includes classification and other characteristics, delineation, geographic name, position and related measures, a "reach code" through which other information can be related to the NHD, and the direction of water flow. The network of reach codes delineating water and transported material flow allows users to trace movement in upstream and downstream directions. In addition to this geographic information, the dataset contains metadata that supports the exchange of future updates and improvements to the data. The NHD is available nationwide in two seamless datasets, one based on 1:24,000-scale maps and referred to as high resolution NHD, and the other based on 1:100,000-scale maps and referred to as medium resolution NHD. Additional selected areas in the United States are available based on larger scales, such as 1:5,000-scale or greater, and referred to as local resolution NHD. For more information on the NHD, go to https://nhd.usgs.gov/index.html. Hydrography data from The National Map supports many applications, such as making maps, geocoding observations, flow modeling, data maintenance, and stewardship. Hydrography data is commonly combined with other data themes, such as boundaries, elevation, structures, and transportation, to produce general reference base maps. The National Map viewer allows free downloads of public domain WBD and NHD data in either Esri File or Personal Geodatabase, or Shapefile formats.

MSBSD Elementary School boundaries and their related schools. The boundary data was provided by MSBSD and the school locations come from the MSB public facilities dataset.

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