31.07.2014 Views

Coastal Construction Manual - National Ready Mixed Concrete ...

Coastal Construction Manual - National Ready Mixed Concrete ...

Coastal Construction Manual - National Ready Mixed Concrete ...

SHOW MORE
SHOW LESS

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

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

IDENTIFYING HAZARDS 3<br />

A USACE Engineering Circular (USACE 2009a) provides guidance on sources of sea level change data and<br />

projections, and discusses how the data and projections can be used for planning purposes. The guidance is<br />

useful for planning and designing coastal residential buildings.<br />

3.7.2 Updating or Revising Flood Hazard Assessments<br />

Updating or revising an existing flood hazard assessment—<br />

for siting and design purposes—can be fairly simple or highly<br />

complex, depending upon the situation. A simple change may<br />

involve shifting a Zone A or Zone X boundary, based upon<br />

topographic data that is better than those used to generate<br />

the FIRM. A complex change may involve a detailed erosion<br />

assessment and significant changes to mapped flood hazard<br />

zones.<br />

If an assessment requires recalculating local flood depths and<br />

wave conditions on a site, FEMA models (Erosion, Runup,<br />

and WHAFIS) can be used for the site (bearing in mind the<br />

recommended change to the required dune reservoir to prevent<br />

dune loss, described in 3.5.8).<br />

NOTE<br />

<strong>Coastal</strong> hazard analysis models<br />

(Erosion, Runup, WHAFIS) used<br />

by FEMA’s FIS contractors are<br />

available for use by others.<br />

However, those performing<br />

updates or revising flood hazard<br />

assessments are advised to<br />

obtain the assistance of an<br />

experienced coastal professional.<br />

FEMA has also issued its <strong>Coastal</strong><br />

Hazard Modeling Program<br />

(CHAMP) to facilitate the use of<br />

standard FEMA models for flood<br />

hazard mapping.<br />

If an assessment requires careful consideration of shore erosion,<br />

the checklist, flowchart, and diagram shown in Chapter 4 can be<br />

a guide, but a qualified coastal professional should be consulted.<br />

Much of the information and analyses described in the checklist and flowchart is likely to have already been<br />

developed and carried out previously by others, and should be available in reports about the area; designers<br />

are advised to check with the community. Cases for which information is unavailable and basic analyses have<br />

not been completed are rare.<br />

The final result of the assessment should be a determination of the greatest flood hazards resulting from a<br />

1-percent-annual-chance coastal flood event that the site will be exposed to over the anticipated life of a<br />

building or development. The determination should account for short- and long-term erosion, bluff stability,<br />

sea level rise, and storm-induced erosion; in other words, both chronic and catastrophic flood and erosion<br />

hazards, along with future water level conditions, should be considered.<br />

3.8 Milestones of FEMA <strong>Coastal</strong> Flood Hazard Mapping Procedures<br />

and FIRMs<br />

Designers are reminded that FEMA’s flood hazard mapping procedures have evolved over the years (the<br />

coastal mapping site, http://www.fema.gov/plan/prevent/fhm/dl_vzn.shtm, provides links to current coastal<br />

mapping guidance and highlights many of these changes). Thus, a FIRM produced today might differ from<br />

an earlier FIRM, not only because of physical changes at the site, but also because of changes in FEMA<br />

hazard zone definitions, revised models, and updated storm data. Major milestones in the evolution of<br />

FEMA flood hazard mapping procedures, which can render early FIRMs obsolete, include:<br />

COASTAL CONSTRUCTION MANUAL<br />

3-67

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

Saved successfully!

Ooh no, something went wrong!