|
Prior to the start ofthis project, it was discovered that some ofuu key uataseto would be available
<br />for use in this mork-, After discussing the mo�juu with cwcu partners a was clear that some entities had
<br />data that could hu useful w their duumo were acquired, These duumowent through u Quality c^ntr^|
<br />(Vc) process m determine issues such uo the usability ^cthu data, verifying the data completeness, and
<br />reviewing the spatial uuuuvmributimu^omnp|umnss^m`duoomuriomeo,
<br />After the QC process was completed, the data was organized into folders and assembled into the
<br />GIS, The CWCB is using ArcGIS.R' Version 9, so the data was assembled in ArcMap.R', Naming
<br />conventions for the ohupumuo and attributes were developed mmake future cus query / identification
<br />/
<br />analysis hr the cwcu staff easier, Parcel polygons and easement polygons that existed in the spatial data
<br />were matched to scans of the paperwork that documents these features, and the spatial data was attributed
<br />with their appropriate information,
<br />In the case where there were paper documents but n^ spatial data the documents needed mhu
<br />converted into spatial representations inucusformat, This was accomplished hr using Coordinate
<br />Geometry (cocm)^entering the bearings and distances that are found in the description m create the
<br />easement polygons, The Assessor's parcel data was pretty much current m`do^mp|uu^wn^pmxaohudm
<br />be created, The easement data that was cono`dhr Planet nmIR'� was tied m the Arapahoe County parcel
<br />data m ensure u match m the parcel data,
<br />Data from TsT Infrastructures were converted from xomcxo.R' drawing files mssa| R'ohupumuo
<br />and were not adjusted spatially mmatch the parcel data,
<br />Task 3 — Linkin2 Pamir Records to the Soatial Data
<br />The third task of this pro�ject involved linking the scanned documents with their spatial
<br />representations and attributed the parcel measement polygons with necessary information,xrcMap.R)
<br />utilizes u process called '4mu1inaing` that will link u file mucusfeature. In this project the scans were
<br />stored as PDF files, so these PDF files were linked to their appropriate polygons, Certain pieces of data
<br />were extracted from the scans and were entered uo attributes within the easements, These attributes
<br />included the date ^c the document, the cost ^c the easement (if u,muh|u)^ the date ^c the recording, the
<br />reception or book and page information, the expiration date, and who the easement was with,
<br />After this process was completed there were still some easements without scans, and a list of these
<br />easements were provided m the cwcustaff, Likewise, there were parcels from the Arapahoe County
<br />Assessor's data that did not have links m scanned documents, In some cases the parcel geometry did not
<br />match the descriptions and in other cases the scans were not complete for all ofthe parcels, The missing
<br />easement and parcel polygon data were addressed in Task 5,
<br />Task 4 — In-Depth Data Analvsis and Data Review
<br />After all of the parcels and easements were created and linked with the documents in hand, and after
<br />all ^cthu attributes that were created were checked, an in-depth analysis ofthe data was performed mmake
<br />sure that the data w represented was correct and complete, xu part ^c this task, any missing information
<br />(scans ofpaper documents or spatial representations ofparcels or easements) were identified, TsT
<br />Infrastructures had most, ifnot all, ofthis missing information so the CWCB staffasked TST Infrastructures
<br />for this information mhu used in Task 5.
<br />����
<br />Task 5 — Fill in Missing Information
<br />After the list of missing information was generated a was determined that the TsT Infrastructures
<br />data should help mbring the database vrm-dam, This data came m Planet msIR'wxomcxo.R'Drawing
<br />files (DWG files), Planet GISIR' created ESRI.R' shapefiles ofthis data and incorporated them into the
<br />project, Each easement polygon created by Planet GISIR' was matched to the TST Infrastructures data and
<br />vice-versa, If any data was missing it was created and attributed, After all of the missing easement
<br />polygons were created and attributed, they were linked m their scans w was done in Task s
<br />When the missing information was completed, ufinm| review was performed mu all ^cuu data m
<br />help m ensure that the database io current and complete, uu"ouu was created for the duuouo created hr
<br />Planet cusIR' (Easement Polygons, Pro.juot Line Features, Project Point Features, and Pro.juotPolygon
<br />This docummupresentouusndingsaepouuvehisproject. This report and live demonstrations
<br />of the GIS environment will be given m audiences identified by the CWmotaff.
<br />As the CWCB moves forward with this project and data, the maintenance and upkeep of the
<br />documents and data will need to be addressed, The simplest way to keep the data current is to require any
<br />new easement requests to contain an AutoCAD.R' Digital Exchange File (DXF) or an ESRI.R' shapefile of
<br />the easement, This spatial data should huin State Plane Coordinates, Colorado Central Zone, mxom
<br />Coordinates, and os Survey Feet, This io the predominant coordinate system ^cthuduuouo used inthe
<br />project, uu"ouu should hu created for all ^c the submitted data, To keep the scanned documents similar,
<br />they should hu provided uoueoFfile, Upon approval ^c the easement the documents will hu recorded u
<br />the County Clerk and Recorder's ocoou, This recorded document should hu the one contained in the eoF
<br />and whose geometry io represented in the ozF file mohupumu,
<br />To make the attribute maintenance easier, each spatial feature contains only a unique identification
<br />number (ID), This |oio used m link the feature mu spreadsheet omumningun^cthuuo*hominfo,mutimu,
<br />This way a will »u easy for the nvcu staff m keep the tabular information current.
<br />The parcels owned by the CWCB were easily identified in the Assessor's parcel data and seems to
<br />hu pretty complete, There io still m` issue linking these parcel polygons m scans ^c their deeds, In some
<br />cases the parcel geometry did not match the descriptions and in other cases the scans were not complete for
<br />all ofthe parcels, The Assessor's parcel maps were downloaded (and included in the deliverables) for use
<br />in helping midentify them, but the boundary lines ^c individual parcels and tracts were not included in the
<br />spatial parcel data — only their outer boundaries are represented,
<br />
|