Publication Date: APR 2018. A vector polygon GIS file of all city and town boundaries in New York State. The file was originally a compilation of U.S. Geological Survey 1:100,000-scale digital vector files and NYS Department of Transportation 1:24,000-scale and 1:75,000-scale digital vector files. Boundaries were revised to 1:24,000-scale positional accuracy and selectively updated based on municipal boundary reviews, court decisions and NYS Department of State Local Law filings for annexations, dissolutions, and incorporations. Currently, boundary changes are made based on NYS Department of State Local Law filings (http://locallaws.dos.ny.gov/). Additional updates and corrections are made as needed in partnership with municipalities. Additional metadata, including field descriptions, can be found at the NYS GIS Clearinghouse: http://gis.ny.gov/gisdata/inventories/details.cfm?DSID=927.

© NYS Office of Information Technology Services GIS Program Office (GPO)

The Commonwealth of Virginia grants certain powers to incorporated municipalities. There are seven towns in the County. Washington Dulles International Airport is also included due to its jurisdictional authority.

Purpose: Town boundaries can define the limits of zoning, and other police powers, and the provision of services by both the towns and the County. Jurisdictional authority is represented for each of the seven towns and Washington Dulles International Airport.

Supplemental Information: Data are stored in the corporate ArcSDE Geodatabase as a feature class. The coordinate system is Virginia State Plane (North), Zone 4501, datum NAD83 HARN. The first town to be incorporated in Loudoun was Leesburg in 1757.

Maintenance and Update Frequency: As Needed

Town boundaries are updated within 1-2 weeks of the date of receipt of recorded documents associated with annexations. Recorded documents are generally received from the Department of Financial Services within 4-6 weeks of the date of recordation. Town boundaries are checked for coincidence with parcel boundaries approximately once every six months.

Completeness Report: Features may have been eliminated or generalized due to scale and intended use. To assist Loudoun County, Virginia in the maintenance of the data, please provide any information concerning discovered errors, omissions, or other discrepancies found in the data.

Data Owner:

Office of Mapping and Geographic Information

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

A vector polygon GIS file of all city and town boundaries in New York State. The file was originally a compilation of U.S. Geological Survey 1:100,000-scale digital vector files and NYS Department of Transportation 1:24,000-scale and 1:75,000-scale digital vector files. Boundaries were revised to 1:24,000-scale positional accuracy and selectively updated based on municipal boundary reviews, court decisions and NYS Department of State Local Law filings for annexations, dissolutions, or incorporations. Currently, boundary changes are made based on NYS Department of State Local Law filings (http://locallaws.dos.ny.gov/). Additional updates and corrections are made as needed in partnership with municipalities.

Polygon feature of the fifteen towns of Cape Cod.

This political boundary layer is the most accurate representing the city and town boundaries in the Commonwealth of Massachusetts.

This datalayer has been created from latitude and longitude coordinates found in the 68-volume Harbor and Lands Commission Town Boundary Atlas. This Atlas series, and updates since it was published, describes the legal boundary for each of the 351 municipalities in Massachusetts. These coordinates were recorded from surveys of the location of each boundary marker around the periphery of each community. Each survey was tied into higher order monumented survey control points. The Atlases also include detailed descriptions of each community's boundary and location maps for each of the original boundary marker locations. The original surveys were conducted in the 1890s. The Atlas series was published in the early 1900s and has since been updated by the Survey Section of the Massachusetts Highway Department with changes as they are approved by the legislature. MassGIS staff collaborated closely with staff from the Survey Section during the development of this data layer. MassGIS staff keyed the coordinates into a database; that data entry was double-checked by staff from the Survey Section. Staff from the Survey Section then converted the latitude/longitude coordinates to the NAD83 datum and also created a version of the coordinates in state plane coordinates with units of meters. MassGIS used the state plane coordinates to "generate" points in ArcGIS. Boundary arcs from the existing USGS-derived municipal boundary data layer were then snapped to the survey-derived points. The differences between the municipal boundary arcs digitized from those on the USGS quads and those created by snapping to the survey-derived coordinates are typically plus or minus 12 feet, although these differences are sometimes less and sometimes more. Some municipal boundary arcs (about 15% of the total) follow the edge of a road or rail right-of-way or a stream or river channel. In these cases, the new boundary arcs were "heads up" digitized based on features visible on the statewide 1:5,000 color orthos from imagery flown in 2001.

For communities with a coastal boundary, MassGIS collaborated with the Massachusetts Water Resources Authority and the Department of Environmental Protection to complete a 1:12,000 scale coastline.

City/Town names' labels are included in this service.

(This service was published from a map document using the Web Mercator projection for the data frame.)

For full metadata please see http://www.mass.gov/itd/townsurvey.

Loudoun County, Virginia Boundary

This map service is provided by NC Department of Transportation and represents Municipal Boundaries defined through the Powell Bill 2023.This data was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System. Municipal boundaries are recognized as a base cartographic layer for location analysis. The data are current for fiscal year 2023.These Municipal Boundaries data are based on the Powell Bill Program maps for the 2023 fiscal year. Municipalities in North Carolina that participate in the Powell Bill Program are required to submit to NCDOT on a regular basis. These data include incorporated municipalities in North Carolina that participate in the Powell Bill Program. Boundaries of municipalities which do not participate in the Powell Bill Program are also included in this data. Sources for the boundaries vary in scale and format as provided by the Municipalities.Additional metadata: GIS Data Layers (ncdot.gov)

Incorporated Places are those reported to the Census Bureau as legally in existence as of January 1, 2019, under the laws of their respective states. An incorporated place provides governmental functions for a concentration of people, as opposed to a minor civil division (MCD), which generally provides services or administers an area without regard, necessarily, to population. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions.CDPs are the statistical counterparts of incorporated places. CDPs are settled concentrations of population that are identifiable by name but not legally incorporated under the laws of the state in which the CDPs are located. The Census Bureau defines CDP boundaries in cooperation with local partners as part of the PSAP. CDP boundaries usually coincide with visible features or the boundary of an adjacent Incorporated Place or another legal entity boundary. CDPs have no legal status and do not have officials elected to serve traditional municipal functions. CDP boundaries may change from one decennial census to the next with changes in the settlement pattern; a CDP with the same name as in an earlier census does not necessarily have the same boundary.

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

The 2020 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. A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any other place. The generalized boundaries of the consolidated cities in this file are based on those as of January 1, 2020, as reported through the Census Bureau's Boundary and Annexation Survey (BAS).

KML file of boundary for the city of Chicago. To view or use these files, special GIS software, such as Google Earth, is required.

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

This service provides visual representation of North Carolina Municipal Boundaries defined through the 2021-2022 Powell Bill.This service was created to assist governmental agencies and others in making resource management decisions through use of a Geographic Information System (GIS). Municipal boundaries are recognized as a base cartographic layer for location analysis. This data is current for the fiscal year 2021 - 2022. Municipal boundaries updated this year were based on towns that reported annexation changes to the NC Office of Secretary of State. This may not be representative of all towns with boundary changes this year.The Municipal Boundaries service is based on the Powell Bill Program maps for the 2021-2022 fiscal year. Municipalities in North Carolina participating in the Powell Bill Program are required to submit to NCDOT on a regular basis. These datasets include incorporated municipalities in North Carolina that participate in the Powell Bill Program. Boundaries of municipalities which do not participate in the Powell Bill Program are also included in this data. Sources for the boundaries vary in scale and format as provided by the individual Municipalities.For more detailed information about the Powell Bill Program: https://connect.ncdot.gov/municipalities/State-Street-Aid/pages/default.aspxThe Spatial Data Operations Group at the North Carolina Department of Information Technology-Transportation, GIS Unit serves as the data steward of this service, on behalf of the North Carolina Department of Transportation, Powell Bill (State Street-Aid) Program Unit. This data is updated annually, first quarter (usually in February).MetadataThe metadata for the contained layer of the NCDOT City Boundaries Service is available through the following link:Municipal BoundariesPoint of ContactNorth Carolina Department of Information Technology -Transportation, GIS UnitGIS Data and Services ConsultantContact information:gishelp@ncdot.govCentury Center – Building B1020 Birch Ridge DriveRaleigh, NC 27610Hours of service: 9:00am - 5:00pm Monday – FridayContact instructions: Please send an email with any issues, questions, or comments regarding the City Boundaries data. If it is an immediate need, please indicate as such in the subject line in an email.NCDOT GIS Unit GO! NC Product Team

description: This file contains boundaries for each Town in the state, including the DCF Region and Area Office responsible for providing services to each Town. This data is as of 7/1/2014, is unlikely to change frequently, and will be updated with any change to the catchment zones.; abstract: This file contains boundaries for each Town in the state, including the DCF Region and Area Office responsible for providing services to each Town. This data is as of 7/1/2014, is unlikely to change frequently, and will be updated with any change to the catchment zones.

This layer identifies corporate boundaries for all 43 municipal jurisdictions in Westchester County. Coverage originally obtained from New York State Office for Real Property Services (ORPS), and has been substantially modified to better align with current municipal tax parcel boundaries (WCparcels) based on a compilation of 2012 municipal tax parcel datasets. As all of Westchester's town's and cities compile their tax parcel databases independent of one another, there are situations were the tax parcels do not line up at the municipal borders, often resulting in gaps or overlaps of tax parcels at the border areas. This update sought to re-align boundaries to best follow the municipal boundaries as defined by the tax parcels, and often involved making the best possible spatial compromise where there were gaps or overlaps in tax map jurisdictions. It also reflects the 2011 municipal boundary change that resluted from the annexation of a tax parcel from the Town of Mount Pleasant to the Town of New Castle.

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

The VA_TOWN dataset is a feature class component of the Virginia Administrative Boundaries dataset from the Virginia Geographic Information Network (VGIN). VA_COUNTY represents the best available city and county boundary information to VGIN.VGIN initially sought to develop an improved locality and town boundary dataset in late 2013, spurred by response of the Virginia Administrative Boundaries Workgroup community. The feature class initially started from the locality boundaries from the Census TIGER dataset for Virginia. VGIN solicited input from localities in Virginia through the Road Centerlines data submission process as well as through public forums such as the Virginia Administrative Boundaries Workgroup and VGIN listservs. Data received were analyzed and incorporated into the VA_COUNTY feature class where locality data were a superior representation of the city or county boundary.

© Virginia Geographic Information Network (VGIN), and the Census and Localities and Towns submitting data to the project

This layer is a component of Feature classes representing locality (county, city, and town) boundaries in the Commonwealth of Virginia..

Download In State Plane Projection Here. Municipal boundaries are based on annexations, court orders and other legal documents filed in the office of the Recorder of Deeds. Mapping is based on the legal descriptions from those documents, which relate to existing parcel boundaries or to the underlying PLSS. Important attributes include "Type" which contains an "I" if the polygon represents an incorporated area, and a "U" if unincorporated. The municipality name for "I" type polygons is included in the attribute "NAME1." Update Frequency: This dataset is updated on a weekly basis.