ArcGIS REST Services Directory
JSON

Layer: Town Boundaries (ID:1)

View In:   Map Viewer

Name: Town Boundaries

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Is View: true

Is Updatable View: true

Source Schema Changes Allowed: true

Sources

Description: <p>This layer is a modified version of the 1:24K USGS DLG-derived political boundaries datalayer provided by NH Granit. &nbsp;Subtle deviations in the linework between this layer and Granit's reflect, 1) NRPC's adoption MassGIS's representation of the state boundary between New Hampshire and Massachusetts using survey points, and, 2) areas where town-originated digital parcel data overlapped, in which case the placement of the town boundary is at the estimated midpoint of the overlap, and the digital parcels were then edge-matched accordingly. &nbsp;</p><p>More significant discrepancies reflect NRPC's corrections of the town boundaries along two key areas:&nbsp;<br>•&nbsp;&nbsp;&nbsp;&nbsp;The northern border between Pelham and Hudson: NRPC's depiction agrees with local perambulation records and was reaffirmed through the Towns' joint submission to the U.S. Census Boundary Annexation Survey in 2017. &nbsp;<br>•&nbsp;&nbsp;&nbsp;&nbsp;The Summer Street area between Milford and Amherst: &nbsp;NRPC's data reflects the outcome of NH Legislation, HB 1248 (2006), which transferred a portion of territory from Amherst to Milford. &nbsp;</p><p>Lastly, it should be noted that NRPC's mapping of the entire western border of Lyndeborough along Greenfield and Temple reflects the definition of the town line according to the town's digital parcels provided to NRPC by Cartographic Associates in 2015. &nbsp; It diverges profoundly from the border representation in NH Granit and also U.S.Census (which also differ from each other).&nbsp;</p><p>Disclaimer: This dataset is an NRPC interpretation of original source material and maps. It is appropriate for mapping and planning purposes; it should not be utilized where legal and surveyed boundaries are required. NRPC does not make any warranty, representation, or guarantee as to the content, sequence, accuracy, timeliness, or completeness of this information. The user should not rely on these data without verifying its accuracy independently. NRPC and its member communities, respectively, explicitly, disclaim any representations and warranties including, without limitation, the implied warranties of merchantability and fitness for a particular purpose. NRPC and its member communities shall assume no liability for errors, omissions, inaccuracies in the information provided regardless of how caused and for any decision made or action take or not taken by the user in reliance upon any information or data furnished hereunder.</p>

Copyright Text: Users please cite, "NRPC GIS Program."

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 10/26/2025 7:51:36 PM

Schema Last Edit Date: 11/18/2025 11:04:25 PM

Data Last Edit Date: 11/18/2025 11:04:58 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat