My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Application Completeness Review
>
OnTrack
>
MA
>
2020
>
MA 20-2
>
Application Completeness Review
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2020 4:00:34 PM
Creation date
8/21/2020 11:12:09 AM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
MA
File Year
20
File Sequence Number
2
Application Name
1400 Cross Street LLC
Document Type
Application Completeness Review
Document_Date
8/14/2020
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
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
application. In this case, the proposal appears to trigger the requirement for a concurrent refinement plan <br />application. Staff interpret EC 9.7730(5)(b) as not requiring a separate ordinance. Staff do not interpret EC <br />9.7730(5)(b) as a procedural pass on the refinement plan amendment. Please submit the required refinement <br />plan amendment or otherwise provide additional findings to support waiving a concurrent or subsequent <br />refinement plan amendment. <br />Written Statement Required for a Proposed Text Change <br />Submiitted <br />Missing <br />Incompiete <br />N/A <br />❑ <br />❑ <br />❑ <br />® <br />3. Submitted a written example of the proposed text change. This should <br />be specific page(s) the change applies to should be cited. <br />Information Required for a Proposed Diagram Change <br />Submitted <br />Missing <br />Incomplete <br />N/A <br />® <br />❑ <br />❑ <br />❑ <br />4. Submitted a map indicating the property included in the request and <br />adjacent streets and alleys. <br />® <br />❑ <br />❑ <br />❑ <br />5. Submitted a vicinity map indicating the general area of the amendment <br />that allows easy identification of the property. <br />® <br />❑ <br />❑ <br />❑ <br />6. Submitted a map indicating the existing plan diagram boundaries and <br />the proposed plan diagram boundaries. <br />Comments <br />Required Neighborhood/Applicant Meeting per EC 9.7007 & 9.7010 <br />Submitted <br />Missing <br />Incomplete <br />® <br />❑ <br />❑ <br />7. Submitted the list of persons who were mailed notice pursuant to EC 9.7007(5) & <br />a signed statement that notice was posted & mailed to those on the list. <br />® <br />❑ <br />❑ <br />8. Submitted a copy of the notice(see EC 9.7007(5)) <br />® <br />❑ <br />❑ <br />9. Submitted a copy of the meeting notes and sign-in sheet described at EC <br />9.7007(9); <br />® <br />❑ <br />❑ <br />10. Submitted copy of the site plan presented at the meeting. <br />® <br />❑ <br />❑ <br />11. Verify if site plan submitted with application substantially conforms to site plan <br />presented at neighborhood/applicant meeting (see EC 9.7007(12)). If not, new <br />meeting is required. <br />Comments: <br />It appears that the application is consistent with the neighborhood meeting proposal. <br />Referral Information <br />Yes <br />No <br />❑ <br />® <br />12. Is the right-of-way county maintained? <br />❑ <br />® <br />13. Does Parks Planning require a referral for this application? <br />ZONE CHANGE <br />Written Statement <br />Submitted <br />Missing <br />Incomplete <br />N/A <br />14. Provided a written statement demonstrating how the requested change <br />❑ <br />❑ <br />® <br />❑ <br />satisfies the criteria in Eugene Code Section 9.8865. <br />15. Provided a written statement and other evidence, if necessary, <br />❑ <br />❑ <br />® <br />❑ <br />demonstrating how the requested change satisfies the applicable <br />provisions of OAR 660-012-0060 (the Transportation Planning Rule). <br />Comments: <br />1. The written statement confuses base zones, overlay zones, and plan designations. For example, there is no <br />such "Whiteaker Special Area" overlay zone. <br />2. The response at EC 9.8855 is incorrect. The concurrent zone change will be processed as a Type I Metro Plan <br />Amendment, not a Type IV application. Staff are also confused with the conclusory statement that the proposal <br />will "comply with the criteria in EC 9.8855(3) and (4). These are not approval criteria, but application process <br />requirements. <br />3. The response at EC 9.8865(2) contains multiple inaccuracies. An approved MA will not revise the Envision <br />Refinement Plan Amendment Completeness Review Form Page 2 of 3 <br />
The URL can be used to link to this page
Your browser does not support the video tag.