ArcGIS REST Services Directory
JSON

Layer: Merrimack CAMA Lookup (ID:8)

Name: Merrimack CAMA Lookup

Display Field: ownername

Type: Table

Is View: true

Is Updatable View: true

Source Schema Changes Allowed: true

Sources

Description: <div style="text-align:Left;"><div><div><p style="margin:0;"><span style="font-size:12pt;">Around late August each year, NRPC requests an updated report of data from each of our 13 communities that contains the parcel ownership and assessing attributes. NRPC compiles the disparate information into a uniform schema which is then loaded into </span><a target="_blank" href="https://nrpcnh.mapgeo.io"><span style="font-size:12pt;"><u>MapGeo</u></span></a><span style="font-size:12pt;">, NRPC's parcel viewer, for display and query. In the February timeframe, NRPC makes another request to communities for data, the goal being that each community's MapGeo information is refreshed at least once and up to two times per year. NRPC does not regularly update the data outside of these two windows.</span></p><p style="margin:0;">&nbsp;</p><p style="margin:0;"><span style="font-size:12pt;">Attributes:</span></p><ul><li><span style="font-size:12pt;">entityID: unique numeric ID for each of 13 towns.</span></li><li><span style="font-size:12pt;">account: assessing system ID; for Patriot systems it is the account ID, for Vision it reflects AV_PID, and for Avitar it is the MBLU. The value is unique within each town but not across towns.</span></li><li><span style="font-size:12pt;">accountunique: concatenation of entity and account; unique across the dataset.</span></li><li><span style="font-size:12pt;">propertyidmunicipal: "plain language" property identifier, typically MBL with a unit or other suffix in the case of multi-property parcels (e.g. condos).</span></li><li><span style="font-size:12pt;">composite_pid: the GIS id of the parcel associated with the assessing record</span></li><li><span style="font-size:12pt;">site_address: situs address of the parcel associated with the assessing record.</span></li><li><span style="font-size:12pt;">site_city: situs city of the parcel associated with the assessing record.</span></li><li><span style="font-size:12pt;">owner: owner of record, current as of the community's last provided report to NRPC.</span></li><li><span style="font-size:12pt;">url3: web link to facilitate integration with MapGeo.</span></li><li><span style="font-size:12pt;">Lat_DD: latitude of the centroid of the parcel associated with the assessing record, in decimal degrees (NAD83).</span></li><li><span style="font-size:12pt;">Lon_DD: longitude of the centroid of the parcel associated with the assessing record, in decimal degrees (NAD83).</span></li></ul><p style="margin:0;">&nbsp;</p><p style="margin:0;"><span style="font-size:12pt;">The cardinality between NRPC’s parcels and CAMA is 1:M; the normalized data herein is therefore published in an ESRI relationship class.</span></p><p>&nbsp;</p><p><span style="font-size:12pt;">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.</span></p></div></div></div>

Copyright Text: Nashua Regional Planning Commission

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field: GlobalID

Type ID Field:

Fields:
Templates:

Relationships: Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 11/12/2025 1:40:03 PM

Schema Last Edit Date: 11/12/2025 1:40:03 PM

Data Last Edit Date: 11/12/2025 1:40:03 PM

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