12.07.2015 Views

Glendale (PDF) - Hazard Mitigation Web Portal - State of California

Glendale (PDF) - Hazard Mitigation Web Portal - State of California

Glendale (PDF) - Hazard Mitigation Web Portal - State of California

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Natural <strong>Hazard</strong>s <strong>Mitigation</strong> PlanCity <strong>of</strong> <strong>Glendale</strong>, <strong>California</strong>Section 1 - IntroductionOrdinance, the Building Codes, and other pertinent documents.The following components must be part <strong>of</strong> the planning process:♦ Complete documentation <strong>of</strong> the planning process;♦♦♦♦♦A detailed risk assessment on hazard exposures in the community;A comprehensive mitigation strategy, which describes the goals and objectives,including proposed strategies, programs and actions to avoid long-term vulnerabilities;A plan maintenance process, which describes the method and schedule <strong>of</strong> monitoring,evaluating and updating the Plan and integration <strong>of</strong> the All <strong>Hazard</strong> <strong>Mitigation</strong> Planinto other planning mechanisms;Formal adoption by the City Council; andPlan review by both FEMA and <strong>State</strong> OES.These requirements are spelled out in greater detail in the following sections <strong>of</strong> the Plan andsupporting documentation.A minimum <strong>of</strong> two public workshops (or other public forums) is recommended to meet therequirement for public participation, in addition to the inclusion <strong>of</strong> representatives from outsideorganizations on the planning committee itself. The timing and scheduling <strong>of</strong> the workshopsmay vary from one community to another depending on how each city’s committee organizes itswork and the particular needs <strong>of</strong> the community.<strong>Glendale</strong>’s consultant and City staff examined existing mitigation plans from around thecountry, current FEMA hazard mitigation planning standards (386 series) and the <strong>State</strong> <strong>of</strong><strong>California</strong> Natural <strong>Hazard</strong>s <strong>Mitigation</strong> Plan Guidance.Other reference materials consisted <strong>of</strong> county and city mitigation plans, including:♦ Clackamas County (Oregon) Natural <strong>Hazard</strong>s <strong>Mitigation</strong> Plan♦ City <strong>of</strong> Long Beach Natural <strong>Hazard</strong>s <strong>Mitigation</strong> Plan♦ Upper Arkansas Area Risk Assessment and <strong>Hazard</strong> <strong>Mitigation</strong> Plan♦ <strong>State</strong> <strong>of</strong> Arkansas <strong>Hazard</strong> <strong>Mitigation</strong> Plan♦ City <strong>of</strong> Pasadena Natural <strong>Hazard</strong>s <strong>Mitigation</strong> Plan♦ City <strong>of</strong> Torrance <strong>Hazard</strong>s <strong>Mitigation</strong> Plan♦ Los Angeles Specific Planning Guidebook provided by the DMACs <strong>of</strong> Area C<strong>Hazard</strong> Specific Research<strong>Glendale</strong>’s consultant and staff collected data and compiled research on four hazards:earthquakes, wildfires, flooding, and landslides. Research materials used include publications byfederal agencies such as FEMA and the U.S. Geological Survey; state agencies such as CGS,OES and CDF; the City <strong>of</strong> <strong>Glendale</strong>’s Safety Element, and other sources. The City’s consultantconducted research by referencing historical local sources, interviewing long-time City <strong>of</strong><strong>Glendale</strong> employees, who provided invaluable data regarding past local disasters, and locatinginformation specific to the city <strong>of</strong> <strong>Glendale</strong> in historical documents.City <strong>of</strong> <strong>Glendale</strong>’s staff evaluated the feasibility and potential effectiveness<strong>of</strong> the proposed2006 PAGE 1 - 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!