Name: Marlborough

Display Field: STNAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The approach and process to create the regional, standardized parcel data for the project involved the following steps. First convert the collected parcel data from its current format into the required Esri Geodatabase format, and the CT Cadastral Standard file Geodatabase template. All pre-existing parcel polygon attributes and parcel line attributes (including any feature level metadata) that were both part of the standard and also those that are not part of the standard attributes, were preserved as appended fields in the attribute tables. Next the GIS Link currently employed by the town was determined and if there was not an existing link, then AppGeo created one. If necessary, an Intersection table was created to establish the “many-to-one” relationship of condos and these special types of parcels. Analyze the data and report the mismatches for parcels with no CAMA as well as CAMA with no parcels. Analyze the parcels data for duplicate IDs. Document and submit to the towns, the analyses results and a map depicting the parcels that do not have a matching CAMA record, and work with the town to resolve the issues found. Goal was to accurately resolve as many of the mismatches as possible in order to meet at least the minimum required match rate of 90% per the CT Cadastral Standard. Incorporate necessary changes to resolve mismatches into the GIS data. In some cases this involved completely redrawing new parcel boundaries from recorded plans that were located during the resolution step, for changes such as lot splits or merges that will resolve a mismatch. The Coordinate Geometry (COGO) method was employed for creating or updating parcels lines when a recorded plan with the bearings or angles and distances are provided.The next step in the process was to assess the overall quality of the linework, flag areas of major concern with Errata Points, and attempt to acquire additional plans or other input from the town to address these areas. AppGeo adjusted the parcel linework using the more accurate boundaries depicted on plans that were made available. The surrounding (less accurate) parcels were then adjusted to the new (more accurate) parcels. The remaining parcels were visually inspected for alignment to the orthophotos. If determined necessary, the right of way lines and interior lot lines for each block of parcels were adjusted to visually match base map features on a block by block basis. If a town had, and provided to AppGeo, a dimension text layer, then the parcel lines were adjusted while maintaining parcel line lengths as defined by the dimension text per the best fit. If any of the original parcels had been created or maintained using Coordinate Geometry (COGO) and are identified as such in the existing parcel attributes, those parcels’ boundaries were held firmly as is and were not modified during the alignment process. Feature level metadata for all parcels edited during this process were updated in the parcel layers’ attributes according to the CT Cadastral Standard attribution guidelines. Internal QA/QC was done by AppGeo and then the data were reviewed by CRCOG.

Copyright Text: These data were processed by Applied Geographics, Inc. as part of a regional performance incentive grant to the CRCOG (Capitol Region Council of Governments). These metadata were created as part of this project by AppGeo.

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -8071287.276162225
YMin: 5098808.733515233
XMax: -8060369.151528245
YMax: 5114454.310986977
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [104, 104, 104, 255]
Width: 1
Label:
Description:
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: FID )
• STNAME ( type: esriFieldTypeString, alias: STNAME, length: 2 )
• STFIPS ( type: esriFieldTypeString, alias: STFIPS, length: 2 )
• CNTYNAME ( type: esriFieldTypeString, alias: CNTYNAME, length: 50 )
• CNTYFIPS ( type: esriFieldTypeString, alias: CNTYFIPS, length: 3 )
• STCNTYFIPS ( type: esriFieldTypeString, alias: STCNTYFIPS, length: 5 )
• MUNINAME ( type: esriFieldTypeString, alias: MUNINAME, length: 50 )
• MUNICIPALI ( type: esriFieldTypeString, alias: MUNICIPALI, length: 3 )
• GNIS ( type: esriFieldTypeInteger, alias: GNIS )
• SOURCEAGEN ( type: esriFieldTypeString, alias: SOURCEAGEN, length: 50 )
• PARNO ( type: esriFieldTypeString, alias: PARNO, length: 40 )
• SHAPE_Leng ( type: esriFieldTypeDouble, alias: SHAPE_Leng )
• Map ( type: esriFieldTypeString, alias: Map, length: 10 )
• Block ( type: esriFieldTypeString, alias: Block, length: 10 )
• Lot ( type: esriFieldTypeString, alias: Lot, length: 10 )
• Sublot ( type: esriFieldTypeString, alias: Sublot, length: 10 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

Supported Operations:   Query   Query Attachments   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata