22. Level 3 Geotechnical Aualvsis has been submitted because <br />either of the required Level 1 or Level 2 reports identified <br />potential stability issues that necessitate design-specific <br />geotechnical recommendations. The report includes all of the <br />requirements of Levels 1 and above; design recommendations for <br />❑ <br />❑ <br />❑ <br />❑ <br />structures. foundations, compacted fill, cut/fill lines. earthwork, and <br />streets, mitigation measures for seismic hazards, landslides, and <br />constraints that cannot be removed, construction measures for <br />back-l311, compaction, drainage, weather limitations. access across <br />slope easements; inspection requirements during and following <br />construction, and graphical representation of slope easements and <br />design details for foundations and structures. <br />Comments: <br />Hazardous Materials Review , <br />1 es No <br />L] ® <br />23. Is a Hazardous Materials Review application required? <br />Comments: <br />Street and Public Access Way Requirements <br />Submitted <br />Missing <br />Incomplete <br />N/A <br />0 <br />❑ <br />❑ <br />❑ <br />24. Show street names for all existing and proposed streets (public and <br />private) and identity the street classification. <br />❑ <br />❑ <br />❑ <br />❑ <br />25. Indicate potential slope easements. <br />❑ <br />El <br />❑ <br />❑ <br />26. Delineate any street segments where grade exceeds 15° 0 percent. where <br />driveways are prohibited. <br />❑ <br />El <br />❑ <br />❑ <br />27. Provide a street center profile using ground elevations of proposed streets <br />at or exceeding 15% grade. <br />23. Show location and widths (right-of-way and paving width) of all existing <br />© <br />❑ <br />❑ <br />❑ <br />and proposed streets, intersections, and bike and pedestrian access ways, <br />both within the plat and adjacent to the plat <br />❑ <br />❑ <br />❑ <br />29. Show existing and proposed curbs and sidewalks on site and adjacent to <br />ro em• involved. <br />❑ <br />❑ <br />❑ <br />30. Address EC 9.0315 Street Connectivity and provide supporting narrative <br />or if requesting an exception, provide justifications. <br />❑ <br />El <br />❑ <br />0 <br />31. Show that the proposal is consistent with Eugene Code Section 9 6730, <br />Vision Clearance Area. <br />❑ <br />❑ <br />❑ <br />❑ <br />32. Indicate radii of all street curves on the plans. <br />0 <br />❑ <br />❑ I <br />❑ <br />33. Show location and type of existing and proposed transit-related facilities. <br />❑ <br />❑ <br />❑ <br />34. Show existing and proposed special setbacks, in accordance with Eugene <br />Code Section 9.6750. <br />❑ <br />❑ <br />❑ <br />0 <br />35. Submit an Alternative Traffic Safetv Study (ATSS) if an adjustment is <br />requested to the required internal vehicle stacking at EC 9.67030)(a). <br />36. Show all existing and proposed access driveways to the propem when <br />❑ <br />❑ <br />❑ <br />the propem• fronts a street under Lane County jurisdiction, show <br />drivewav locations for adjacent properties also. <br />© <br />❑ <br />❑ <br />❑ <br />37. Demonstrate that existing and proposed access connections to the <br />development site are compliant with EC 7.420. <br />Please indicate any potential slope easements. <br />Comments: <br />Please show the radii of all street curves on the plans. <br />Traffic 'Lm actAnalvsis <br />Yes No <br />❑ © 3 3. Is a Traffic Impact Analysis required? <br />Comments: <br />For Staff Use Only - Referral Information <br />Fo..•un„ -rn .Hv~ L'..: lir W."L. i-.~mnL•~rr l`-e~+v ~.nm R- ~.ii. . <br />