1 / 12

Overview of FEMA’s Multihazard Mapping Initiative

Overview of FEMA’s Multihazard Mapping Initiative. Scott McAfee January 22, 2001. Origin of Project. Disaster Mitigation Act 2000; Section 203 Develop multihazard advisory maps Identify applicable natural hazards Be developed in consultation with primary users

katell-potts
Télécharger la présentation

Overview of FEMA’s Multihazard Mapping Initiative

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Overview of FEMA’sMultihazard Mapping Initiative Scott McAfee January 22, 2001

  2. Origin of Project Disaster Mitigation Act 2000; Section 203 • Develop multihazard advisory maps • Identify applicable natural hazards • Be developed in consultation with primary users • Utilize cost effective and efficient technology • Should not affect existing policies • 5 communities in different states • Mitigation zones • No funding

  3. MMI Strategy • Build off of existing FEMA initiatives • GIS Atlas/Clearinghouse (Web GIS) • Modified deliverables to ramp up a working system quickly • Open GIS Consortium – MMI-1 Pilot • Develop a prototype interoperable hazard map network • Avoid duplication and keep costs down • Develop policy through a users group • Mostly state and local government but federal participants welcome

  4. Atlas/Clearinghouse • Atlas • For public, emergency managers, planners, decision makers, etc. • Provides high contrast option for 508 • ArcIMS map viewer • Clearinghouse • Upload and download of hazard data and metadata

  5. Why Open GIS? • Natural hazard data exist • in many formats • at all levels of government • FEMA primarily responsible for flood maps • Too much data and too dynamic to maintain in one place • Many hazard maps are designed to have DOQQ or topographic base

  6. Open GIS Conceptual Architecture Hazard Map Discovery and Visualization Hazard Map Sources Applications Publish O G C W E B S E R V I C E S Federal Discover University NGO Visualize Web-Based Thin Clients & GIS Applications State Value- Add Local MMI-1 Framework Service/Data Registries Web Mapping - Data Servers Web Mapping - Portrayal Services = Web Server

  7. MMI Support • Harvard Design and Mapping • Michael Baker Jr. Corp. • OGC and participants • Compusult • Cubeworks • Intergraph • Ionic • MapInfo • SAIC/ESRI

  8. Phase I – Current Status Develop a national web-based map server Establish links to, or incorporate external databases Recruit and coordinate with federal, state, and local partners Develop interoperability standards for hazard data exchange Goes Public January 28 In progress Current partners include NOAA, USGS In progress MMI Status

  9. Future plans Phase II & III • Continue to develop and enhance the multi-hazard mapping network • Identify, develop, and implement required specs • Increase capabilities • Add Web Map Servers (esp. for base data) • Add more federal, state, and local databases

  10. Policy issues • Not for disaster response (yet) • Not for homeland security (yet) • What are the incentives for other agencies to make their data available • Credit where credit is due: Logos? • How easy will it be for participants to set up services? • Use CAG to address these issues

  11. Who are we building this for? • Federal agencies • NGO’s • State agencies • Emergency managers • Local government • GIS people • Politicians • General public

  12. Conclusions • Quick ramp up with proprietary system • Make a part of NSDI; GS 1 stop; FEMA e-gov • Phase in interoperability with little or no interruption to existing system • Build partnerships and encourage data submittal and WMS development • Continue funding to enhance the network

More Related