My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
DLCD Notice
>
OnTrack
>
CA
>
2022
>
CA 22-1
>
DLCD Notice
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/2/2022 4:04:01 PM
Creation date
2/1/2022 11:52:07 AM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
CA
File Year
22
File Sequence Number
1
Application Name
Willamette River Greenway Code Amendments
Document Type
Application Materials
Document_Date
2/1/2022
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
80
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
DRAFT WILLAMETTE RIVER GREENWAY DESIGN PLAN <br />APPENDIX A. FIELD INVESTIGATION <br />OVERVIEW <br />This section discusses the methodology used to conduct the field investigation, the findings from the <br />investigation, and the process used to establish mapped Willamette River top of bank JOB) and Willamette <br />Greenway setback (WGS) lines as components of the updated regulations. <br />METHODOLOGY <br />City staff estimated the Willamette River TOB in GIS using 2-foot contours, slope, and hillshade layer <br />sets derived from the 2009 LiDAR data. The City provided the GIS dataset to Cameron McCarthy for use <br />on the project and consultants conducted a field investigation on October 12, 2021, to test the accuracy <br />of the mapped Willamette River TOB line. City and consultants agreed upon six test sites for the field <br />investigation. Test sites were labeled with a directional identifier (W, E) based which side of the river the <br />site was located, and nearest street name or geographical feature: <br />• W1 Hatten <br />• W2 Briarcliff <br />• W3 Millrace <br />• E1 Riverplace <br />• E2 Valley River Center (VRC) <br />• E3 Frohnmeyer <br />Exhibit A to the Top of Bank Determination contains a map of the full extent of the Willamette Greenway <br />boundary within Eugene and the location six test sites, as well as field map enlargements of each test site. <br />Consultants collected GPS survey points in the field using a Trimble Geo7x centimeter kit comprised of a <br />handheld rangefinder module connected to a Zephyr mobile antenna mounted to the top of a 6-foot tall <br />surveyor's range pole. At least 12 Global Navigation Satellite System (GNSS) satellites were acquired for <br />use by the handheld GPS unit prior to point collection. This method of collection provides a sub-centimeter <br />radius of accuracy. The high level of accuracy of both LiDAR data and field collected GPS data is designed to <br />rule out data collection and digital processing as contributing factors of error. Consultants collected field <br />GPS points within the six sample sites along the Willamette River. Point Feature Data collected and filed <br />on the GPS handheld was converted to ESRI shapefile format using the handheld internal Windows OS and <br />Trimble's TerraSync application standard process. GIS compatible shapefiles (points) were then transferred <br />to a memory card for processing in Autodesk Civil 3D 2021. <br />GPS field point data was overlayed in Civil 3D with the mapped TOB line, previously generated using LiDAR <br />data. The TOB line and field-collected points were then assessed at each test site for consistency. Where <br />less than 1 meter of difference occurred on average, the mapped TOB line from LIDAR data is considered <br />to be accurate to field conditions. For test sites where field-collected data points varied from the mapped <br />TOB line greater than 1 meter of difference, the mapped TOB line was considered not accurate to field <br />conditions and modified based on field conditions and GPS field point data. Primary methods used for <br />M WILLAMETTE RIVER GREENWAY CODE AMENDMENTS I CITY OF EUGENE 38 <br />
The URL can be used to link to this page
Your browser does not support the video tag.