# Presentation: 756938

## Flood Forecast Mapping in AHPSOctober 28, 2003

## Outline

- Definition
- Requirements
- Processing Tasks
- One-time
- Routine
- Test Area
- Presentation Methods
- What next?

## Definition

- Provide areal extent of flooding referenced against well-understood markings (streets, structures, landmarks) for water elevation forecasts
- At multiple locations along river reach

## Requirements

- Water Surface Profile
- FLDWAV, SHRT, other
- DEM Data
- Processing Tools
- Presentation Methods

## Requirements

- Water surface profile
- NWS FLDWAV
- Data collection
- Calibration
- Verification
- Routine generation
- deterministic
- probabilistic

## Requirements

- Digital Elevation Data
- High-resolution most effective
- Reference Overlays
- Orthophoto (geo-referenced images)
- USGS Quad Sheets
- TIGER Data
- Utility Plans

## Requirements

- Processing Tools
- Process static data
- Create ground grid
- Process dynamic data
- Create water surface grid
- FLDVIEW
- Arcview based

## Test Area

## Test Area

## Test Area

## Test Area

## Processing – Ground Grid

## Processing – Ground Grid

## Processing – Water Surface Grid

## Processing – Water Surface Grid

## Samples (Jan ‘96)

## Samples (Jan ‘96 Zoom)

## Highwater Comparison (‘84)

## Samples (4 layer zoom)

## Presentation

- Water surface profile
- Water surface grid
- Shapefile
- Static web images
- Web-based image generation
- Policy issues for new product category

## Web-based Image Generation

- Internet map service
- User interaction
- User selectable layers
- Zoom
- Prototype site:
- http://nwshqfld.nws.noaa.gov
- Autodesk plug-in required

## Prototype Map Service

## Prototype Map Service

## Prototype Map Service

## Prototype Map Service

## Prototype Map Service

## Prototype Map Service

## Prototype Map Service

## Prototype Map Service

## Status

- Single location
- Lewistown on Juniata River
- Daily Background processing
- After routine operations
- Cron initiated
- FLDWAV on Linux
- FLDVIEW on HP WS

## Stats

- Space Requirements
- On AWIPS, Lewistown - ~1 GB
- On FLDIMS - ???
- FLDWAV performance - Linux
- Deterministic, entire Susq. – few seconds
- Probabilistic, 7 day PQPF – 35+ seconds
- Probabilistic, 30 day - ~ 3 minutes

## Stats (cont’d)

- FLDVIEW performance – HP WS
- Fully automated
- 7+ minutes deterministic (one layer)
- 35+ minutes, 5 layer probabilistic (5 layers)
- FLDVIEW performance – P3, 1 GHz, 512 MB
- ~1’ 10” per layer

## Stats (cont’d)

- Automated process
- Within Linux scripts
- OFS, PQPF, ESPADP, FLDVIEW, FTP
- MARFC-developed queuing system
- MARFC-developed auto-X-Display
- Expect-based FTP transfer of modified shapefiles

## What next?

- Sequencing
- From peak value to 6 hour values
- Animation?
- New location
- Coding and structure changes
- Other Susq. FLDWAV calibrated reach
- OHD prepared
- Resources and methodology for entirely new location
- Data, software, code, training, documentation
- In-house vs. AHPS funded

## What next? (cont’d)

- Simplified Hydraulic Routing Technique (SHRT)
- Mapping for locations without backwater, without junctions
- NWS Policy
- Products
- Water surface profiles, shapefiles, images, internet mapping services
- Official communications methods
- PC-based FLDVIEW execution
- Currently coded for either HP-UX or PC

## What next? (cont’d)

- Internet map service selection
- User feedback
- Design
- Performance
- User-friendliness

## The End