3. GIS consulting-tax parcel migration
Laserfiche
>
Public
>
County Commission
>
2014
>
07-21-2014
>
Regular agenda
>
3. GIS consulting-tax parcel migration
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
7/16/2014 2:06:50 PM
Creation date
7/16/2014 2:06:49 PM
Metadata
Fields
Template:
Commission
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
This step includes the creation and updating of the Source to Target document that <br /> provides both PWA and the County a record of where the data started and where it <br /> ended up and what happened along the way. <br /> • Determine workable units for processing and staging environments <br /> Based on the estimated number of existing parcels listed for the County and City, only <br /> one working unit is necessary. This will be confirmed during review of the existing <br /> data. <br /> • Use COTS tools to optimize curves and lines <br /> PWA will utilize tools native to the ArcGIS environment and checks in the Data <br /> Reviewer extension to ensure the lines associated with the original data's polygons <br /> have their curves and segmentation optimized prior to loading into the parcel fabric. <br /> If the original data does not have line data, the lines will first be created from the <br /> polygons via native ArcGIS tools. <br /> • Recreate and reattribute polygons from the edited lines <br /> During the previous step, the lines are edited to optimize curve data and may no <br /> longer match the edges of the polygons. The polygons are then re-created with these <br /> newly edited lines to take advantage of the optimized curve and segmentation <br /> alignments. <br /> • Perform data checks including creating and applying topology <br /> Within the staging environment, many checks are performed prior to loading. These <br /> checks include topologic checks on the individual feature types, spatial reference <br /> checks of the staging to final geodatabase environments, geometry checks, field and <br /> attribute checks, and an inventory of all the data be to loaded is created. <br /> Topology checks happen many times in the staging environment. To ensure the new <br /> lines and polygons are in agreement, topology validation will be performed with rules <br /> used that ensure line to polygon alignment. <br /> Additional topology checks are performed prior to loading the staging data into the <br /> fabric that ensure the data meets the needs of the parcel fabric itself. There are six <br /> published rules that need to be validated. <br /> <Line>Must be Covered by Boundary Of<Polygon> <br /> <Line>Must Not Self-Overlap <br /> <Line>Must Not Self-Intersect <br /> <Line>Must Be Single Part <br /> <Line>Must Not Intersect or Touch Interior <br /> <Polygon>Boundary Must Be Covered By<Line> <br /> 6 <br />
The URL can be used to link to this page
Your browser does not support the video tag.