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>Executive Summaryresources to the coordinating organization. The partner organizations listed in theResource Directory (Appendix A) <strong>of</strong> the City <strong>of</strong> <strong>Glendale</strong>’s Local Natural <strong>Hazard</strong>s<strong>Mitigation</strong> Plan are potential partners recommended by the <strong>Hazard</strong> <strong>Mitigation</strong> AdvisoryBoard. These organizations, however, were not contacted during the development <strong>of</strong> the<strong>Mitigation</strong> Plan, and should therefore be contacted by the coordinating organization toestablish their commitment <strong>of</strong> time and resources to action items.C onstraintsConstraints may apply to some <strong>of</strong> the action items. These constraints may be a lack <strong>of</strong> Citystaff, lack <strong>of</strong> funds, or vested property rights, which might expose the City <strong>of</strong> <strong>Glendale</strong> tolegal action as a result <strong>of</strong> adverse impacts on private property.How Will the Plan be Implemented, Monitored,and Evaluated?The Plan Maintenance Section <strong>of</strong> this document details the formal process that will ensure thatthe <strong>Glendale</strong> Local Natural <strong>Hazard</strong>s <strong>Mitigation</strong> Plan remains an active and relevant document.The plan maintenance process includes a schedule for monitoring and evaluating the Planannually and producing a Plan revision every five years. This section describes how the Citywill integrate public participation throughout the plan maintenance process. Finally, thissection includes an explanation <strong>of</strong> how the City’s government intends to incorporate themitigation strategies outlined in this Plan into existing planning mechanisms such as the City’sGeneral Plan, Building and Safety Codes, and community development plans.Plan AdoptionAdoption <strong>of</strong> the Local <strong>Hazard</strong> <strong>Mitigation</strong> Plan by the local jurisdiction’s governing body is one<strong>of</strong> the prime requirements for approval <strong>of</strong> the Plan. Once the Plan is completed, the CityCouncil will be responsible for adopting the City <strong>of</strong> <strong>Glendale</strong>’s Local <strong>Hazard</strong>s <strong>Mitigation</strong> Plan.The local agency governing body has the responsibility and authority to promote sound publicpolicy regarding natural hazards. The City Council will periodically need to re-adopt the Planas it is revised to meet changes in the natural hazard risks and exposures in the community.The approved Local Natural <strong>Hazard</strong> <strong>Mitigation</strong> Plan will be significant in the future growthand development and redevelopment <strong>of</strong> the community.Coordinating BodyThe City <strong>of</strong> <strong>Glendale</strong> <strong>Hazard</strong> <strong>Mitigation</strong> Strategic Committee will be responsible forcoordinating implementation <strong>of</strong> Plan action items and undertaking the formal review process.The City’s Manager, or his or her designee, can and will assign representatives from Cityagencies and other organizations to serve in this committee, as appropriate, including, but notlimited to, the current <strong>Hazard</strong> <strong>Mitigation</strong> Advisory Committee members.ConvenerTheCity Council will adopt the City <strong>of</strong> <strong>Glendale</strong> Local Natural <strong>Hazard</strong> <strong>Mitigation</strong> Plan, and the2006 PAGE ES - 5

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

Saved successfully!

Ooh no, something went wrong!