M.9 Coastal Submittal Standards

Summary of questions/comments received for the Coastal section on DHS Interactive and responses provided through October 10, 2008

Topic Comment Response
Data Files BFEs in the S_BFE file are listed as required spatial files. However, in many cases, only static BFEs will be developed in the coastal analysis. S_BFE should be "if applicable." Static BFEs should be captured in the S_Fld_Haz_Ar spatial file per Section M.9.2.1. The table has a field for STATIC_BFE and refers to BFEs in "lakes and coastal zones."

The following changes will be made to the DCS in the next revision:

Spatial Files

–Floodplain Mapping submittal information (S_Submittal_Info described in Section M.11)

–BFEs lines where applicable (S_BFE spatial file described in Section M.11) Static BFEs must be recorded in S_Fld_Haz_Ar spatial file

–Flood hazard zone map boundary delineations; including static BFEs (S_Fld_Haz_Ar spatial file described in Section M.11)
Directory Structure Recommend clarifying where back-up data should be submitted. Would supplemental coastal data in a PGDB that contains spatial and non-spatial data go in the Spatial Files or Coastal Databases directory? Personal geodatabases with both spatial and non-spatial data should be submitted in the Coastal Databases directory.

The DCS will be updated to reflect this clarification.
Requirements Check spelling of "envelope"

Should surge station locations be a required GIS data layer if a location map is required?
The spelling of envelope was updated in the revised version of DCS posted in late September.

The surge station location map is included in the FIS text. For readability, the Mapping Partner may have to generalize the storm surge output. The GIS data layer should include all output stations from the model. For this reason, both are required.

Last Modified: Wednesday, 29-Oct-2008 10:14:09 EDT