My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Ordinance No. 20351
COE
>
City of Eugene
>
Ordinances
>
2005 No. 20333-20356
>
Ordinance No. 20351
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/10/2010 4:45:43 PM
Creation date
11/18/2005 5:00:44 PM
Metadata
Fields
Template:
City Recorder
CMO_Document_Type
Ordinances
Document_Date
11/18/2005
Document_Number
20351
CMO_Effective_Date
1/1/2006
Author
Kitty Piercy
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
34
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
<br />3. For allegations of error on the Eugene Overlay Zone Map: a list of <br />the tax lots and a description of any right-of-way alleged to have <br />been incorrectly included in the /WR Water Resources <br />Conservation Overlay Zone. <br />4. A description of the alleged error and the proposed correction. <br />(b) Approval Criteria Based Solely on Aerial Photoqraphy and Geoqraphic <br />Information System Data. <br />1. For allegations of error on the Goal 5 Water Resources <br />Conservation Plan Map: it is clear that, at the time the city adopted <br />the Goal 5 Water Resources Conservation Plan Map, that Map <br />showed an incorrect location of the identified Goal 5 Water <br />Resource Site. <br />2. For allegations of error on the Eugene Overlay Zone map: it is clear <br />that, at the time the city applied the /WR Water Resources <br />Conservation Overlay Zone to the subject lot(s), the city was <br />incorrect in its determination that the lot(s) contained a Goal 5 Water <br />Resource Site or a /WR Water Resources Conservation Area. <br />(3) Correction Based on Additional Information. An application submitted <br />pursuant to this subsection (3) shall be processed under the Type II application <br />procedure (EC 9.7200 - 9.7230). <br />(a) Application requirements. <br />1. The materials required under subsection (2)(a). <br />2. If the alleged error is in the city's measurement of the conservation <br />setback (as opposed to the location of the resource itself), a site <br />plan drawn to scale, showing all of the following: <br />a. The location of the boundary of the resource as mapped by <br />the city in the Goal 5 Water Resources Conservation Plan; <br />b. The alleged correct location of the boundary of the /WR <br />conservation area for the resource in question based on EC <br />9.4920; <br />c. The distance in feet from the nearest point of the alleged <br />correct location of the boundary of the /WR conservation area <br />of the resource in question to the subject property. <br />3. If the alleged error is in the mapping of an upland wildlife habitat <br />site or a riparian site (as opposed to the measurement of the site's <br />conservation setback): <br />a. A detailed written description of the mapped area claimed to <br />be incorrectly included within the resource site in question, <br />including an inventory list of plant species and the relative <br />frequency of plant species listed; <br />b. The location of the boundary of the resource as mapped by <br />the city in the Goal 5 Water Resources Conservation Plan; <br />c. The alleged correct location of the boundary of the /WR <br />conservation area for the resource in question; and\ <br />d. Color photographs of the area claimed to be incorrectly <br />included within the resource site in question. <br />4. If the alleged error is in the mapping of a wetland site (as opposed <br />to the measurement of the conservation setback area), a wetland <br />determination or a wetland delineation report and map, and a <br />signed concurrence letter from the Oregon Department of State <br />Lands, indicating that the determination or report is consistent with <br /> <br />Ordinance - 13 <br />
The URL can be used to link to this page
Your browser does not support the video tag.