1. Flood Map Library MD. M. HAQUE DWR-HYDROLOGY

2. Building a Flood Map Library Indexing existing flood maps and geospatial data for search and retrieval Separate geospatial and relational data components – Geodatabase feeds map services for map-based access – Relational database feeds web pages for web-based access Oracle Database Attribute Tables Documents Map links PDF Maps Geodatabase Shapefiles Images FERIS Viewer Java Backend

3. Contents of Flood Map Library Current datasets Tsunami Inundation Maps Dam-break Inundation Maps Historical Inundation maps Compiled DWR Best Available Maps (BAM) http://cdec4gov.water.ca.gov/floodER/data_apps.html http://gis.bam.water.ca.gov/bam/

4. Data Summary Data typePDF MapsShapefilesImagesGeodatabase Tsunami2611 polygon file Dam-break743231 point 603 polylines 560 polygons 3402 (OES, Tiff) 104 (Mokelumne) 13 (Jpeg) Historical Events 234 layers Data Volume 2.09 Gb0.386 Gb6.42 Gb0.01 Gb Images take up the most space Conversing images to PDF could reduce data volume by ~ 60%

5. Tsunami Inundation Maps Each map covers a 1:24,000 USGS quad sheet Based on finite difference analysis with Methods of Splitting Tsunamis (MOST) model Variable ocean grid and nearest coast cells for propagating wave from quake epicenter

6. Dam-break Inundation Maps By relative map grid downstream of dam eg A9 Each map extent determined by shape of inundation zone Based on dam-break analysis for a single source dam May overlap other dam-break inundation extents Include Normal Flow (rapid) and PMF (slower) failure modes Fair Weather simulation mode (No inflow)

7. Variable Depth Dam-break Inundation

8. Variable Time Dam-break Inundation

9. Implementation Historic Inundation Map

10. Historical Inundation Map Layers Data originally stored as a separate layer for each disaster Results in multiple feature layers for any incident type eg Delta inundation polygons are in 4 different feature layers Makes it impossible to search by characteristics such as feature type, location or event date

11. Historical Inundation Map Attributes Different attributes depending on who assembled the data

12. Historical Inundation Geodatabase Data now transformed into a standardized geodatabase with all ‘like’ incidents grouped into 20 feature datasets eg all Delta Flood incidents are stored in the Delta Flood feature layer. Standard attributes for all features datasets are stored in a ‘featuretype’ table. Each feature has its own unique attributes.

13. Historical Inundation Database All historical data of incidents such as boils and levee breaks have been aggregated into an incident table. Attributes such as county and year ensure the database is searchable.

14. Implementing Data Update Procedures: Historical Inundation Maps Attributes features by location and link to levee infrastructure Transfer attribute into relational database to allow searches Link geodatabase to FERIS to facilitate web-based mapping Event GIS data analysis Geodatabase Quadsheets County Maps Oracle Database Attribute Tables Source Dams Stage, Timing DWR GIS Staff State, county and local users Incident reporting DWR Field Teams AccessDB

15. MS Access Database Application for Updates An MS Access application for users to collect incident reports Intended for use by field teams collecting flood incident and damage reports for use in updating the historical event database

16. Forms to Define a Disaster Name Disaster Id is automatically updated Enter disaster name is used to associate all incidents from a disaster ‘Geometry’ and ‘Metafile’ are legacy attributes from existing databases

17. Forms to Report a New Incident Incident ID is automatically updated ‘Disaster name’ and ‘Incident Type’ are selected from existing list List of field names updates based on ‘Incident Type’ selected Standards enforced to ensure easy data transfer from Access to Oracle

18. Initial Design of Web Page Displays Secure Log-in page Search forms for querying database by attributes such as county, year and incident type Results pages to display table of database contents matching search parameters. The results pages will also be accessible through the FERIS Map Server. Hyperlinks of search results allowing user to access preexisting Adobe PDF format maps if available Initial demo prepared with historical event database

19. Secure log-in page with user names and passwords stored on server to avoid tampering Allow verified users to view, upload and download data

20. Web Interface to Oracle Database Multi-criteria search form Customizable report form with choice of fields reported Buffered display with maximum of 25 results per page Next pageLast pageRefresh

21. Multi-criteria Search Drop down selection dynamically retrieves and lists all unique entries in the database Check box on the left identifies which search criteria are active

22. Report Generation Output can be customized by specifying which data columns to be included in search results

23. Hyperlink to PDF content Metadata files and flood maps in Adobe PDF format can also be linked in results to provide click access for data downloads

24. Next in Line: Dam-break Inundation in Geodatabase Each dam-break of the 1000+ inundation extents is in a different map layer Differences in map projection and field names hence the database is not easily searchable Differences must be resolved before data can be used effectively in FERIS Geodatabase Major Dams with OES Dams

25. Next Steps Transition other flood maps with PDFs to Oracle databases – Dam-break Inundation PDF maps – Tsunami Inundation PDF maps – Best Available Maps BAM Inundation PDF maps – Others Clean up disparate feature layers and attribute with common location features (such as county layer) in geodatabase Setup Oracle interface linking PDF in Oracle and feature datasets in Geodatabase through a map interface Initiate, training and user feedback and documentation Geodatabase Shapefiles PDF maps Images Oracle Database Attribute Tables Sources, Event Data EAP, Other Documents

26. Dynamic Inundation Maps