Presentation on theme: "Final UVA Internship Presentation Abby Frazier, Brendan Mold, Marc Kavy, Burton Putrah, Scott Gilbert & Michael Oldham Spring 2008."— Presentation transcript:
Final UVA Internship Presentation Abby Frazier, Brendan Mold, Marc Kavy, Burton Putrah, Scott Gilbert & Michael Oldham Spring 2008
Overview Over the course of the semester, we were able to complete the parcels from five towns: Bakersfield, Berkshire, Fairfield, Fletcher and Sheldon: 434 parcels total We were able to establish common problems and solutions while transferring these paper maps into a digital geodatabase
ENTERING COORDINATES While georeferencing, right click on the tick mark to bring up the XY coordinate input menu. ENTERING COORDINATES Each tick mark requires the easting and northing data to be manually entered into ArcMap. Clear handwriting and accurate coordinate information helps eliminate error in this respect.
USING THE EDITOR TOOL After successfully georeferencing four tick marks for each parcel, the pencil tool in the Editor toolbar is used to digitally draw in the parcel boundaries. Upon completion, successful parcel boundaries are saved into the shapefile/database.
Problems ArcMap turns tiff files into white noise
Colored in orthophotos and multiple maps taped together…
All 4 east or north coordinates are the same, or barely any coordinates at all! Some also have no ground features to line up or even names on the map… Also, any map with a false easting (East coordinate in the 100,000s) had to be adjusted with the figure of 347,599.695
Not to scale? Split up parcels?
A: False easting shift B: Crosses town boundary
Recommendations Establish a higher minimum standard for accepting maps –Only accept maps in NAD83 –Make sure each map has at least 4 reference coordinates (that make sense) –Consistency linking spatial and attribute data –High resolution scanning or digital copy
The Next Step… Reconciling the overlap issues using geodatabase topology –Collaborating with county forester to determine actual boundaries