My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
75E - PH - 2525 N. MAIN ST._ADJOURNED
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2019
>
02/19/2019
>
75E - PH - 2525 N. MAIN ST._ADJOURNED
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/12/2020 3:12:32 PM
Creation date
2/14/2019 2:23:50 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Planning & Building
Item #
75E
Date
2/19/2019
Destruction Year
2024
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
378
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
EXHIBIT A <br />9.4.3 Wetlands <br />Threshold: Would the Project have a substantial adverse effect on federally protected wetlands as <br />defined by Section 404 of the Clean Water Act (including, but not limited to, marsh, vernal pool, coastal, <br />etc.) through direct removal, filling, hydrological interruption, or other means? <br />Finding: No Impact. (DEIR, p. 2-5; Initial Study, p. 24.) <br />Facts in Support of Finding: Wetlands are defined under the federal Clean Water Act as land that is <br />flooded or saturated by surface water or groundwater at a frequency and duration sufficient to support, <br />and that normally does support, a prevalence of vegetation adapted to life in saturated soils. Wetlands <br />include areas such as swamps, marshes, and bogs. The Project area is developed and does not contain <br />natural wetlands. While Santiago Creek is located approximately 130 feet to the north of the Project site, <br />the creek area is separated from the Project site by a roadway within Santiago Park, and the Project would <br />not extend into the park area. Therefore, the Project would not result in impacts to wetlands. (Initial Study, <br />p. 24.) <br />9.4.4 Local Policies and Ordinances Protecting Biological Resources <br />Threshold: Would the Project conflict with any local policies or ordinances protecting biological <br />resources, such as a tree preservation policy or ordinance? <br />Finding: No Impact. (DEIR, p. 2-5; Initial Study, p. 24) <br />Facts in Support of Finding: The Project would not conflict with any local policies or ordinances <br />protecting biological resources. Trees in the public right-of-way in Santa Ana are protected under Chapter <br />33, Article VII of the Municipal Code, which regulates the planting, maintenance, and removal of trees in <br />public locations in Santa Ana. The Project would not remove any existing healthy street trees, and the <br />additional street trees installed by the Project would be planted in compliance with the Municipal Code <br />regulations. Moreover, the existing ornamental trees on the Project site are on private property and are not <br />subject to the Municipal Code regulation. Therefore, implementation of the Project would not conflict <br />with local polices or ordinances protecting trees and no impact would occur. (Initial Study, p. 24) <br />9.4.5 Adopted Habitat Conservation Plans <br />Threshold: Would the Project conflict with the provisions of an adopted Habitat Conservation <br />Plan, Natural Community Conservation Plan, or other approved local, regional, or state habitat <br />conservation plan? <br />Finding: No Impact. (DEIR, p. 2-5; Initial Study, p. 25) <br />Facts in Support of Finding: The Project site does not contain any lands that are subject to an adopted <br />Habitat Conservation Plan, Natural Community Conservation Plan, or other approved local, regional, or <br />state habitat conservation plan. Therefore, the Project would not result in impacts to biological habitat <br />plans. <br />Resolution No. <br />Certification of the Magnolia at the Park EIR <br />75E-62 <br />Page 24 of 71 <br />
The URL can be used to link to this page
Your browser does not support the video tag.