Appendix M

Data Capture Standards

September 2008

![](media/image1.png){width="2.8513888888888888in"
height="0.9166666666666666in"}

Table of Contents

[M.1 Overview 1](#overview)

[M.1.1 Introduction 1](#introduction)

[M.1.2 Scoping 1](#scoping)

[M.1.3 Base Map 1](#base-map)

[M.1.4 Terrain 1](#terrain)

[M.1.5 Survey 2](#survey)

[M.1.6 Hydrology 2](#hydrology)

[M.1.7 Hydraulics 2](#hydraulics)

[M.1.8 Alluvial Fan 2](#alluvial-fan)

[M.1.9 Coastal 2](#coastal)

[M.1.10 Floodplain Mapping 2](#floodplain-mapping)

[M.1.11 Post-Preliminary Data 3](#post-preliminary-data)

[M.1.12 GIS Spatial Requirements 3](#gis-spatial-requirements)

[M.2 Scoping Assessment and Submittal Standards
5](#scoping-assessment-and-submittal-standards)

[M.2.1 Overview 5](#overview-1)

[M.2.2 Requirements 5](#requirements)

[M.2.2.1 Data Files 5](#data-files)

[M.2.2.2 Accepted File Formats 17](#accepted-file-formats)

[M.2.2.3 Metadata 18](#metadata)

[M.2.2.4 Transfer Methodology 18](#transfer-methodology)

[M.2.2.5 Directory Structure and Folder Naming Conventions
19](#directory-structure-and-folder-naming-conventions)

[M.2.2.6 Data Identification Requirements
20](#data-identification-requirements)

[M.3 Base Map Submittal Standards 21](#base-map-submittal-standards)

[M.3.1 Overview 21](#overview-2)

[M.3.2 Requirements 21](#requirements-1)

[M.3.2.1 Data Files 21](#data-files-1)

[M.3.2.2 General Correspondence 22](#general-correspondence)

[M.3.2.3 Certification of Work 22](#certification-of-work)

[M.3.2.4 Accepted File Formats 22](#accepted-file-formats-1)

[M.3.2.5 Metadata 22](#metadata-1)

[M.3.2.6 Transfer Media 23](#transfer-media)

[M.3.2.7 Transfer Methodology 23](#transfer-methodology-1)

[M.3.2.8 Directory Structure and Folder Naming Conventions
23](#directory-structure-and-folder-naming-conventions-1)

[M.4 Terrain Submittal Standards 25](#terrain-submittal-standards)

[M.4.1 Overview 25](#overview-3)

[M.4.2 Requirements 25](#requirements-2)

[M.4.2.1 Data Files 25](#data-files-2)

[M.4.2.2 General Correspondence 26](#general-correspondence-1)

[M.4.2.3 Certification of Work 26](#certification-of-work-1)

[M.4.2.4 Accepted File Formats 26](#accepted-file-formats-2)

[M.4.2.5 Metadata 27](#metadata-2)

[M.4.2.6 Transfer Media 27](#transfer-media-1)

[M.4.2.7 Transfer Methodology 27](#transfer-methodology-2)

[M.4.2.8 Directory Structure and Folder Naming Conventions
27](#directory-structure-and-folder-naming-conventions-2)

[M.5 Survey Submittal Standards 31](#survey-submittal-standards)

[M.5.1 Overview 31](#overview-4)

[M.5.2 Requirements 32](#requirements-3)

[M.5.2.1 Data Files 32](#data-files-3)

[M.5.2.2 General Correspondence 44](#general-correspondence-2)

[M.5.2.3 Certification of Work 44](#certification-of-work-2)

[M.5.2.4 Acceptable File Formats 44](#acceptable-file-formats)

[M.5.2.5 Metadata 44](#metadata-3)

[M.5.2.6 Transfer Media 45](#transfer-media-2)

[M.5.2.7 Transfer Methodology 45](#transfer-methodology-3)

[M.5.2.8 Directory Structure and Folder Naming Conventions
45](#directory-structure-and-folder-naming-conventions-3)

[M.6 Hydrology Submittal Standards 47](#hydrology-submittal-standards)

[M.6.1 Overview 47](#overview-5)

[M.6.2 Requirements 47](#requirements-4)

[M.6.2.1 Data Files 47](#data-files-4)

[M.6.2.2 General Correspondence 50](#general-correspondence-3)

[M.6.2.3 Certification of Work 50](#certification-of-work-3)

[M.6.2.4 Acceptable File Formats 50](#acceptable-file-formats-1)

[M.6.2.5 Metadata 50](#metadata-4)

[M.6.2.6 Transfer Media 51](#transfer-media-3)

[M.6.2.7 Transfer Methodology 51](#transfer-methodology-4)

[M.6.2.8 Directory Structure and Folder Naming Conventions
51](#directory-structure-and-folder-naming-conventions-4)

[M.7 Hydraulics Submittal Standards 53](#hydraulics-submittal-standards)

[M.7.1 Overview 53](#overview-6)

[M.7.2 Requirements 53](#requirements-5)

[M.7.2.1 Data Files 53](#data-files-5)

[M.7.2.2 General Correspondence 55](#general-correspondence-4)

[M.7.2.3 Certification of Work 56](#certification-of-work-4)

[M.7.2.4 Acceptable File Formats 56](#acceptable-file-formats-2)

[M.7.2.5 Metadata 56](#metadata-5)

[M.7.2.6 Transfer Media 56](#transfer-media-4)

[M.7.2.7 Transfer Methodology 57](#transfer-methodology-5)

[M.7.2.8 Directory Structure and Folder Naming Conventions
57](#directory-structure-and-folder-naming-conventions-5)

[M.8 Alluvial Fan Submittal Standards
59](#alluvial-fan-submittal-standards)

[M.8.1 Overview 59](#overview-7)

[M.8.2 Requirements 60](#requirements-6)

[M.8.2.1 Data Files 60](#data-files-6)

[M.8.2.2 General Correspondence 60](#general-correspondence-5)

[M.8.2.3 Certification of Work 61](#certification-of-work-5)

[M.8.2.4 Accepted File Formats 61](#accepted-file-formats-3)

[M.8.2.5 Metadata 61](#metadata-6)

[M.8.2.6 Transfer Media 61](#transfer-media-5)

[M.8.2.7 Transfer Methodology 62](#transfer-methodology-6)

[M.8.2.8 Directory Structure and Folder Naming Conventions
62](#directory-structure-and-folder-naming-conventions-6)

[M.9 Coastal Submittal Standards 65](#coastal-submittal-standards)

[M.9.1 Overview 65](#overview-8)

[M.9.2 Requirements 65](#requirements-7)

[M.9.2.1 Data Files 65](#data-files-7)

[M.9.2.2 1-Percent-Annual-Chance Wave Envelope
67](#percent-annual-chance-wave-envelope)

[M.9.2.3 0.2-Percent-Annual-Chance Wave Envelope
67](#percent-annual-chance-wave-envelope-1)

[M.9.2.4 Summary of Coastal Stillwater Elevations
67](#summary-of-coastal-stillwater-elevations)

[M.9.2.5 Surge Station Location Map 68](#surge-station-location-map)

[M.9.2.6 Transect Location Map 68](#transect-location-map)

[M.9.2.7 Transect Description Table 69](#transect-description-table)

[M.9.2.8 Transect Data Table 69](#transect-data-table)

[M.9.2.9 General Correspondence 69](#general-correspondence-6)

[M.9.2.10 Certification of Work 69](#certification-of-work-6)

[M.9.2.11 Acceptable File Formats 70](#acceptable-file-formats-3)

[M.9.2.12 Metadata 70](#metadata-7)

[M.9.2.13 Transfer Media 70](#transfer-media-6)

[M.9.2.14 Transfer Methodology 70](#transfer-methodology-7)

[M.9.2.15 Directory Structure and Folder Naming Conventions
71](#directory-structure-and-folder-naming-conventions-7)

[M.10 Floodplain Mapping Submittal Standards
73](#floodplain-mapping-submittal-standards)

[M.10.1 Overview 73](#overview-9)

[M.10.2 Requirements 73](#requirements-8)

[M.10.2.1 Data Files 73](#data-files-8)

[M.10.2.2 Draft FIS 73](#draft-fis)

[M.10.2.3 Redelineation 74](#redelineation)

[M.10.2.4 Digital Conversion 74](#digital-conversion)

[M.10.2.5 General Correspondence 75](#general-correspondence-7)

[M.10.2.6 Certification of Work 75](#certification-of-work-7)

[M.10.2.7 Floodplain Boundary Standard Self-Certification
76](#floodplain-boundary-standard-self-certification)

[M.10.2.8 Acceptable File Formats 76](#acceptable-file-formats-4)

[M.10.2.9 Metadata 77](#metadata-8)

[M.10.2.10 Transfer Media 77](#transfer-media-7)

[M.10.2.11 Transfer Methodology 80](#transfer-methodology-8)

[M.10.2.12 Directory Structure and Folder Naming Conventions
80](#directory-structure-and-folder-naming-conventions-8)

[M.11 Post-Preliminary Data Submittal Standards
81](#post-preliminary-data-submittal-standards)

[M.11.1 Overview 81](#overview-10)

[M.11.2 Requirements 81](#requirements-9)

[M.11.2.1 Data Files 81](#data-files-9)

[M.11.2.2 Certification of Work 82](#certification-of-work-8)

[M.11.2.3 Acceptable File Formats 82](#acceptable-file-formats-5)

[M.11.2.4 Metadata 82](#metadata-9)

[M.11.2.5 Transfer Media 83](#transfer-media-8)

[M.11.2.6 Transfer Methodology 83](#transfer-methodology-9)

[M.11.2.7 Directory Structure and Folder Naming Conventions
83](#directory-structure-and-folder-naming-conventions-9)

[M.11.2.8 Data Identification Requirements
84](#data-identification-requirements-1)

[M.12 GIS Spatial Requirements 87](#gis-spatial-requirements-1)

[M.12.1 Floodplain Mapping Spatial Files - General
92](#floodplain-mapping-spatial-files---general)

[M.12.1.1 Submittal Information 92](#submittal-information)

[M.12.2 Floodplain Mapping Spatial Files -- Riverine Studies
93](#floodplain-mapping-spatial-files-riverine-studies)

[M.12.2.1 Sub-Basins 94](#sub-basins)

[M.12.2.2 Nodes 94](#nodes)

[M.12.2.3 Profile Baseline 98](#profile-baseline)

[M.12.2.4 Cross Sections 99](#cross-sections)

[M.12.2.5 Base Flood Elevations (BFEs) 101](#base-flood-elevations-bfes)

[M.12.2.6 Alluvial Fan Spatial File 102](#alluvial-fan-spatial-file)

[M.12.2.7 Flood Hazard Area Spatial File
103](#flood-hazard-area-spatial-file)

[M.12.2.8 General Structures Spatial File
106](#general-structures-spatial-file)

[M.12.3 Required Floodplain Mapping Spatial Files -- Coastal Studies
107](#required-floodplain-mapping-spatial-files-coastal-studies)

[M.12.3.1 Coastal Transects 107](#coastal-transects)

[M.12.3.2 Coastal Model 112](#coastal-model)

[M.12.3.3 Coastal Gage Data 113](#coastal-gage-data)

[M.12.3.4 Shoreline 117](#shoreline)

[M.12.3.5 CBRS and Otherwise Protected Areas (OPAs)
118](#cbrs-and-otherwise-protected-areas-opas)

[M.12.3.6 Primary Frontal Dunes 119](#primary-frontal-dunes)

[M.12.3.7 Limit of Moderate Wave Action (LiMWA)
120](#limit-of-moderate-wave-action-limwa)

[M.12.3.8 Coastal Structures 120](#coastal-structures)

[M.13 Domain Tables 123](#domain-tables)

[References 139](#references)

**Tables**

[Table M.2-1. S_Needs_Ar Spatial Files 6](#__RefHeading___Toc210064169)

[Table M.2-2. S_Requests (polygons/points) Spatial Files
8](#__RefHeading___Toc210064170)

[Table M.2-3. Specific_Needs_Info Tabular File
9](#__RefHeading___Toc210064171)

[Table M.2-4. Contact_Info Tabular File
10](#__RefHeading___Toc210064172)

[Table M.2-5. S_Polbnd Spatial File 11](#__RefHeading___Toc210064173)

[Table M.2-6. S_Trnsport Spatial File 12](#__RefHeading___Toc210064174)

[Table M.2-7. S_Hydro_LN and/or S_Hydro_Ar Spatial File
12](#__RefHeading___Toc210064175)

[Table M.2-8. S_HUC Spatial File 12](#__RefHeading___Toc210064176)

[Table M.2-9. S_Fin_Study_Ln Spatial File
14](#__RefHeading___Toc210064177)

[Table M.2-10. S_Fin_Study_Ar Spatial File
15](#__RefHeading___Toc210064178)

[Table M.2-11. S_Prp_FirmPan Spatial File
16](#__RefHeading___Toc210064179)

[Table M.2-12. NatMetrics_Info Tabular File
17](#__RefHeading___Toc210064180)

[Table M.5-1. Survey Data File Example 33](#__RefHeading___Toc210064181)

[Table M.5-2. Survey Codes 34](#__RefHeading___Toc210064182)

[Table M.12-1. S_Submittal_Info Spatial File
92](#__RefHeading___Toc210064183)

[Table M.12-2. S_Subbasins Spatial File
93](#__RefHeading___Toc210064184)

[Table M.12-3. S_Nodes Spatial File 96](#__RefHeading___Toc210064185)

[Table M.12-4. S_Profil_Basln Spatial File
98](#__RefHeading___Toc210064186)

[Table M.12-5. S_XS Spatial File 100](#__RefHeading___Toc210064187)

[Table M.12-6. S_BFE Spatial File 101](#__RefHeading___Toc210064188)

[Table M.12-7. S_Alluvial Spatial File
102](#__RefHeading___Toc210064189)

[Table M.12-8. S_Fld_Haz_Ar Spatial File
104](#__RefHeading___Toc210064190)

[Table M.12-9. S_Gen_Struct Spatial File
106](#__RefHeading___Toc210064191)

[Table M.12-10. S_Cst_Tsct_Ln Spatial File
110](#__RefHeading___Toc210064192)

[Table M.12-11. L_Cst_Model Table 112](#__RefHeading___Toc210064193)

[Table M.12-12. S_Cst_Gage Spatial File
116](#__RefHeading___Toc210064194)

[Table M.12-13. S_Shore_Ln Spatial File
117](#__RefHeading___Toc210064195)

[Table M.12-14. S_CBRS Spatial File 118](#__RefHeading___Toc210064196)

[Table M.12-15. S_PFD_Ln Spatial File 119](#__RefHeading___Toc210064197)

[Table M.12-16. S_LIMWA Spatial File 119](#__RefHeading___Toc210064198)

[Table M.12-17. L_Cst_Struct Table File
120](#__RefHeading___Toc210064199)

**Figures**

[Figure M-1. Typical Cross-section Photograph: Indian Creek IND-6600
(Displays Survey Code Locations) 37](#__RefHeading___Toc209951117)

[Figure M-2. Typical Cross-section Sketch: Indian Creek IND-6600
38](#__RefHeading___Toc209951118)

[Figure M-3. Typical Bridge Photograph: White Creek WHI-1800 (Displays
Survey Code Locations) 39](#__RefHeading___Toc209951119)

[Figure M-4. Typical Bridge Sketch: White Creek WHI-1800
40](#__RefHeading___Toc209951120)

[Figure M-5. Typical Culvert Photograph: Sanderson Creek SAN-0880
(Displays Survey Code Locations) 41](#__RefHeading___Toc209951121)

[Figure M-6. Typical Culvert Sketch: Sanderson Creek SAN-0880
42](#__RefHeading___Toc209951122)

[Figure M-7. Typical Dam Data (Displays Survey Code Locations)
43](#__RefHeading___Toc209951123)

[Figure M-8 Certification of Compliance Form
79](#__RefHeading___Toc209951124)

[Figure M-9. Figure with Nodes, Stream Centerlines, and Basins
98](#__RefHeading___Toc209951125)

# Overview 

## Introduction

The purpose of the Data Capture Standards (DCS) in this Appendix is to
provide a consistent framework for submittal, storage, and retrieval of
the technical and administrative data needed for a Flood Insurance Study
(FIS) or Flood Insurance Rate Map (FIRM) revision. This framework is
intended to make the study assessment process more efficient; provide
easier retrieval of study data; and preserve the investment made in the
data.

The data standards are provided in subsequent sections. Each section
corresponds to major production data capture points in the Mapping
Information Platform (MIP) workflow and includes guidance on submitting
the following deliverables: scoping, base map, terrain, survey,
hydrologic, hydraulic, alluvial fan, coastal, floodplain mapping, and
post-preliminary data for studies. These sections describe the minimum
dataset of deliverables established by the Federal Emergency Management
Agency (FEMA) for floodplain mapping submittals. This Appendix replaces
the previously published *Appendix M: Guidance for Preparing and
Maintaining Technical and Administrative Support Data*; *Appendix N:
Data Capture Standards*; and *Appendix N: Data Capture Guidelines*.

This guidance applies to FEMA-funded studies and restudies conducted by
FEMA's Mapping Partners, including contractors, as well as those studies
performed by communities, regional agencies, and State agencies
participating in the Cooperating Technical Partners (CTP) program. The
information specified in this Appendix must be used for all data uploads
to the MIP.

## Scoping

The Scoping section describes the specifications (e.g., type, naming,
and format) of the Scoping Assessment and scoping data required to be
submitted to FEMA for FISs. This information includes validated flood
data, community mapping needs, and requests identified during the
Scoping Assessment process in a geospatial format.

## Base Map 

The Base Map section describes data needed for the FISs. This
information includes aerial photographs, community boundaries, bench
marks, transportation, and other data to aid in the study process.

## Terrain 

The Terrain section describes the information needed to capture the
digital topographic data used for the FIS. For coastal studies,
bathymetric data used for the analysis of offshore areas and coastal
waters are needed for submission. Certification of the digital
topographic data is required for those datasets funded by FEMA (see
Appendix A of these *Guidelines*).

## Survey 

The Survey section describes the data necessary to digitally represent
information collected in the survey phase of the study. These standards
describe how the survey data for features such as dams, culverts,
bridges, transects, structures, and channels must be submitted. If
funded by FEMA, a certification of the survey data is required. If a
study uses survey data previously collected but not funded by FEMA, the
information does not need to be translated to the deliverable format
listed in this appendix.

## Hydrology 

The Hydrology section describes the data necessary to document the
hydrologic procedures for estimating flood discharges for the FIS. The
goal of this section is to describe the format and type of hydrologic
data expected by FEMA for new and updated studies for rivers, lakes,
closed basins and ponds. The hydrologic data must be certified.

## Hydraulics 

The Hydraulics section describes the format and type of hydraulic data
to be provided to FEMA for FISs. This section also provides standards
for FIS report components including Floodway Data Tables (FDTs),
profiles, and FIS narrative text. The hydraulic data must be certified.

## Alluvial Fan 

The Alluvial Fan section describes data submittal requirements when a
study includes an alluvial fan analysis. This section also includes FIS
elements and certification. The type of data deliverables and formats
required are described in this section.

## Coastal 

The Coastal section outlines data and certification submittal
requirements for coastal studies. This data must be submitted at the end
of the study process once the contractual requirements regarding quality
control reviews have been completed. The type of data deliverables and
formats required are described in this section.

## Floodplain Mapping 

The Floodplain Mapping section describes types of deliverables and
formats for floodplains and associated mapping products that are created
by redelineating floodplains using updated topographic data and
conversion of non-revised effective FIRM information to digital format.

## Post-Preliminary Data

This section presents data generated during the post-preliminary phase
of the mapping process that must be submitted to FEMA. This information
includes data artifacts generated for studies throughout the
post-preliminary processing such as the flood elevation determination
notices, preliminary and final Summary of Map Actions (SOMAs),
Revalidation letters, etc. Data in this section also includes submittal
of Floodplain Boundary Standard (FBS) self-certification information for
all types of study methods.

## GIS Spatial Requirements

This section details the components required in the geospatial
submittals referenced throughout this appendix. This section covers the
field names, size, and type for the attribute information to be
delivered to FEMA. The required items are listed in the subsequent
sections with the specifics of the deliverable listed in section M.12.

# Scoping Assessment and Submittal Standards

## Overview

The purpose of this section is to describe the specifications (e.g.,
type, naming, and format) of the Scoping Assessment and scoping data
required to be submitted to FEMA for FISs. All data must be submitted in
digital format. A Mapping Partner with responsibility for performing the
scoping assessment is required to submit the data specified in this
section to FEMA for inclusion in the needs management system. A Mapping
Partner assigned with the task for "Scoping" per the Statement of Work
(SOW) or Mapping Activity Statement (MAS) is required to submit the data
in this section as part of the upload process in the MIP workflow.
Appendix I of these Guidelines (an updated version to be issued soon)
provides a detailed description and guidance for each of the data
requirements outlined in this section.

The purpose of the Scoping Assessment deliverables is to capture
validated flood data, community mapping needs, and requests identified
during the Scoping Assessment process in a geospatial format. These data
will be stored and updated in FEMA's needs management tracking system.

The Scoping Process is organized into the following main phases:

-   Project Scoping Initiation;

-   Scoping Meeting; and

-   Post-scoping Meeting Activities.

Information regarding the Scoping Assessment and Scoping processes are
provided in Volume 1 and Appendix I of these Guidelines (which are
currently being updated and will be issued soon). The requirements and
deliverables associated with the Scoping Assessment and each phase of
the scoping process are described in this section.

## Requirements

### Data Files 

The Scoping Assessment and Scoping deliverables listed below are
categorized into two types: "Required" and "Required if Applicable."
"Required" indicates a deliverable item that must be delivered for every
scoping submittal, regardless of the circumstances of the individual
study. "Required if Applicable" indicates a deliverable that is required
to be submitted for all scoping submittals unless the deliverable is not
applicable to or required to be produced for the study.

#### Scoping Assessment Data Requirement {#scoping-assessment-data-requirement .unnumbered}

-   Community Mapping Needs (S_Needs_Ar) (Required, if applicable):

This table contains all existing community flood hazard data that will
be evaluated and identified as validated or as an unmet need during the
validation process.

[]{#__RefHeading___Toc210064169 .anchor}Table M.2-1. S_Needs_Ar Spatial
Files

  ----------------------------------------------------------------------------------------
  **Field**             **Type**   **Length**   **Required**   **Description**
  --------------------- ---------- ------------ -------------- ---------------------------
  Need_id               Text       12           Yes            Primary key for table.
                                                               Assigned by table creator

  CID                   Text       10           Yes            Digital Flood Insurance
                                                               Rate Map (DFIRM) Study ID

  MIP_CASE              Text       20           Yes            FEMA MIP Case Number
                                                               assigned to all new studies
                                                               initiated by FEMA

  Reach                 Text       50           Yes            Name of flooding source

  Pop_By                Text       50           Yes            Person or entity populating
                                                               entry

  Rqstr_type            Text       20           Yes            Type of person or entity
                                                               requesting need. Acceptable
                                                               values for this field are
                                                               listed in the D_Rqstr_Type
                                                               table.

  Date_Rqst             Date       8            Yes            Date need is requested

  Date_Resol            Date       8            Yes            Date need is resolved

  Date_Effct            Date       8            Yes            Date of effective analysis

  HdroMod               Text       50           Yes            Hydrologic model used.
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Hydro table.

  hdramod               Text       50           Yes            Hydraulic model used.
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Hydra table.

  digfmt                Short      2            Yes            Is the model in digital
                                                               format? Acceptable values
                                                               for this field are listed
                                                               in the D_Element table.

  runMod                Short      2            Yes            Can the digital model be
                                                               run? Acceptable values for
                                                               this field are listed in
                                                               the D_Element table.

  need_cat              Text       20           Yes            New, Validated, or Updated
                                                               Engineering (NVUE) Category
                                                               Lookup Identification.
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Need_Cat table.

  c1_Gage               Short      2            Yes            Critical Element 1, Change
                                                               in gage record. Major
                                                               change in gage record since
                                                               effective analysis that
                                                               includes major flood
                                                               events? Acceptable values
                                                               for this field are listed
                                                               in the D_Element table.

  c2_disch              Short      2            Yes            Critical Element 2, Change
                                                               in Discharge. Updated and
                                                               effective peak discharges
                                                               differ significantly based
                                                               on confidence limits
                                                               criteria in FEMA\'s G&S?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  c3_model              Short      2            Yes            Critical Element 3, Model
                                                               methodology. Model
                                                               methodology no longer
                                                               appropriate based on
                                                               Guidelines and
                                                               Specifications (i.e.,
                                                               one-dimensional vs.
                                                               two-dimensional modeling;
                                                               Coastal Guidelines)?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  c4_fcstr              Short      2            Yes            Critical Element 4,
                                                               Hydraulic Change.
                                                               Addition/removal of a major
                                                               flood control structure
                                                               (i.e., certified levee or
                                                               seawall, reservoir with
                                                               more than 50 acre-ft
                                                               storage per square mile)?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  c5_chann              Short      2            Yes            Critical Element 5, Channel
                                                               Reconfiguration. Current
                                                               channel reconfiguration
                                                               outside effective Special
                                                               Flood Hazard Area (SFHA)?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  c6_hstr               Short      2            Yes            Critical Element 6,
                                                               Hydraulic Change. More than
                                                               5 new or removed hydraulic
                                                               structures (bridge/culvert)
                                                               that impact Base Flood
                                                               Elevations (BFEs)?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  c7_scour              Short      2            Yes            Critical Element 7, Channel
                                                               Area Change. Significant
                                                               channel fill or scour?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s1_regeq              Short      2            Yes            Secondary Element 1,
                                                               Regression Equation. Use of
                                                               rural regression equations
                                                               in urbanized areas?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s2_replo              Short      2            Yes            Secondary Element 2,
                                                               Repetitive Loss. Repetitive
                                                               losses outside the SFHA?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s3_impar              Short      2            Yes            Secondary Element 3,
                                                               Impervious Area. Increase
                                                               in impervious area in the
                                                               sub-basin of more than 50
                                                               percent (i.e., 10 percent
                                                               to 15 percent, 20 percent
                                                               to 30 percent, etc.)?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s4_hstr               Short      2            Yes            Secondary Element 4,
                                                               Hydraulic Structure. More
                                                               than 1 and less than 5 new
                                                               or removed hydraulic
                                                               structures (bridge/culvert)
                                                               impacting BFEs? Acceptable
                                                               values for this field are
                                                               listed in the D_Element
                                                               table.

  s5_chimp              Short      2            Yes            Secondary Element 5,
                                                               Channel Improvements.
                                                               Channel improvements /
                                                               Shoreline changes?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s6_topo               Short      2            Yes            Secondary Element 6,
                                                               Topography Data.
                                                               Availability of better
                                                               topography/bathymetry?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s7_vegLu              Short      2            Yes            Secondary Element 7,
                                                               Vegetation or Land Use.
                                                               Changes to vegetation or
                                                               land use? Acceptable values
                                                               for this field are listed
                                                               in the D_Element table.

  s8_dune               Short      2            Yes            Secondary Element 8,
                                                               Coastal Dune. Failure to
                                                               identify primary frontal
                                                               dune in coastal areas?
                                                               Acceptable values for this
                                                               field are listed in the
                                                               D_Element table.

  s9_hwms               Short      2            Yes            Secondary Element 9, High
                                                               Water Mark. Significant
                                                               storms with High Water
                                                               Marks. Acceptable values
                                                               for this field are listed
                                                               in the D_Element table.

  s10_reGeq             Short      2            Yes            Secondary Element 10,
                                                               Regression Equation. New
                                                               Regression Equations
                                                               Available? Acceptable
                                                               values for this field are
                                                               listed in the D_Element
                                                               table.

  CE_Total              Short      2            Yes            Total number of critical
                                                               elements

  se_total              Short      2            Yes            Total number of secondary
                                                               elements

  comment               Text       250          No             Additional comments
  ----------------------------------------------------------------------------------------

-   Community Mapping Requests (S_Requests) (Required, if applicable):

This table contains all community flood hazard and/or base data requests
that have been identified during the Scoping Assessment that cannot be
justified as a mapping need. There are two feature classes to capture
these requests as either a polygon or point. Submit either or both as
applicable.

[]{#__RefHeading___Toc210064170 .anchor}Table M.2-2. S_Requests
(polygons/points) Spatial Files

  -------------------------------------------------------------------------
  Field               Type   Length     Required   Description
  ------------------- ------ ---------- ---------- ------------------------
  NEED_ID             Text   12         Yes        Primary key for table.
                                                   Assigned by table
                                                   creator

  Reach               Text   50         Yes        Name of flooding source

  Pop_By              Text   50         Yes        Person or entity
                                                   populating entry

  Rqst_Cat            Text   20         Yes        Request category.
                                                   Acceptable values for
                                                   this field are listed in
                                                   the D_Rqst_Cat table.

  Rqst_Lvl            Text   20         Yes        Level of analysis
                                                   requested. Acceptable
                                                   values for this field
                                                   are listed in the
                                                   D_Rqst_Lvl table.

  Mthod_Type          Text   20         Yes        Method of request made.
                                                   Acceptable values for
                                                   this field are listed in
                                                   the D_Mthod_Type table.

  Rqstr_Type          Text   20         Yes        Type of person or entity
                                                   requesting need.
                                                   Acceptable values for
                                                   this field are listed in
                                                   the D_Rqstr_Type table.

  Date_Rqst           Date   8          No         Date request is made

  Date_Resol          Date   8          No         Date request is resolved

  Carto_Rqst          Text   20         Yes        Type of cartographic
                                                   change requested.
                                                   Acceptable values for
                                                   this field are listed in
                                                   the D_Carto_Rqst table.

  F_Data_Rqst         Text   20         Yes        Type of flood data
                                                   change requested.
                                                   Acceptable values for
                                                   this field are listed in
                                                   the D_Fld_Data_Rqst
                                                   table.

  Comment             Text   250        No         Description of request
  -------------------------------------------------------------------------

-   Specific Needs Information Table (Specific_Needs_Info) (Required, if
    applicable):

This table includes general information that will be associated, via the
Need_ID attribute, with every need or request that is identified during
the Scoping Assessment.

[]{#__RefHeading___Toc210064171 .anchor}Table M.2-3. Specific_Needs_Info
Tabular File

  ------------------- ------- ----------- ---------- ------------------------
  Field               Type    Length      Required   Description

  Need_ID             Text    12          Yes        Primary key for table.
                                                     Assigned by table
                                                     creator

  Cost_Share          Short   2           No         Is there cost share?
                                                     Acceptable values for
                                                     this field are listed in
                                                     the D_Element table.

  Disaster            Text    50          No         Associated disaster
                                                     number

  Mitig_Plan          Short   2           No         Is there a mitigation
                                                     plan identifying need?
                                                     Acceptable values for
                                                     this field are listed in
                                                     the D_Element table.

  Rsk_Assess          Short   2           No         Is there a risk
                                                     assessment? Acceptable
                                                     values for this field
                                                     are listed in the
                                                     D_Element table.

  HAZUS               Short   2           No         Is there a HAZUS run on
                                                     the stream? Acceptable
                                                     values for this field
                                                     are listed in the
                                                     D_Element table.

  HAZUS_LVL           Short   2           No         Level of HAZUS run.
                                                     Acceptable values for
                                                     this field are listed in
                                                     the D_HAZUS_Lvl table.

  Comment             Text    250         No         Additional comment
  ------------------- ------- ----------- ---------- ------------------------

#### Project Scoping Initiation Requirements {#project-scoping-initiation-requirements .unnumbered}

-   Project Management Team (STFIPS+PCOMM#\_ProjectTeam) (Required)

In written format, provide contact information of each member of the
flood map project management team. Each team member's organization,
phone number, fax number, e-mail, and role should be identified.

-   Community Contact List (Contact_Info) (Required):

This table contains contact information for the county and every
incorporated community in the study area that has the following
positions/roles occupied: Chief Executive Officer (CEO) (Mayor, City
Manager, County Judge, or other), State National Flood Insurance Program
(NFIP) Coordinator, local Floodplain Administrator (if community
participates in the NFIP), and data/GIS contact (name of person to
contact with regard to obtaining local data for use in the study).

[]{#__RefHeading___Toc210064172 .anchor}Table M.2-4. Contact_Info
Tabular File

  -----------------------------------------------------------------------
  Fields               Description
  -------------------- --------------------------------------------------
  ORGANIZATION         Community, Agency, or Organization Name

  CEO                  Is this the CEO (Yes/No)?

  FPA                  Is this the Floodplain Administrator (Yes/No)?

  GIS                  Is this the Primary GIS Contact (Yes/No)?

  FIRST NAME           Contact first name

  LAST NAME            Contact last name

  PHONE                Contact Primary Phone Number

  ADDRESS              Contact Address

  CITY                 Contact City

  STATE                Contact State Abbreviation

  ZIP                  Contact Zip Code

  E-MAIL               Contact e-mail address

  DATE                 Date the contact information was confirmed
  -----------------------------------------------------------------------

-   Project Scoping Initiation Report
    (STFIPS+PCOMM#\_ProjectInitiationReport) (Required if applicable):

This report should form a complete record of the Project Scoping
Initiation activities and deliverables completed prior to the Scoping
Meeting. These specifications represent only the framework and minimum
requirements. All information essential or helpful to the
understanding/interpretation of the submitted materials should be
included.

-   Political Area (S_Polbnd) (Required if applicable):

This spatial file contains the political boundaries that cover the
geographic extent of the flood map project.

[]{#__RefHeading___Toc210064173 .anchor}Table M.2-5. S_Polbnd Spatial
File

  ----------- -------- -------- ---------- ----------------------------------
  Field       Type     Length   Required   Description

  POL_NAME    Text     50       Y          Political Area Name 1. This is the
                                           primary name of the area shown.
                                           For areas that have more than one
                                           name, this would be the primary
                                           name with subsequent names shown
                                           in fields below. This would
                                           correspond to the official name of
                                           this jurisdiction used by FEMA
                                           within the NFIP. For
                                           unincorporated areas of a county,
                                           this should be the county name
                                           (e.g., Montgomery County).

  CO_FIPS     Text     3        Y          County FIPS Code. This is the
                                           three-digit county Federal
                                           Information Processing Standard
                                           (FIPS) code. This is a standard
                                           numbering system that is used by
                                           the Federal government. Defined in
                                           FIPS Pub 6-4.

  ST_FIPS     Text     2        Y          State FIPS. This is the two-digit
                                           code that corresponds to the State
                                           FIPS code. This is a standard
                                           numbering system that is used by
                                           the Federal government. Defined in
                                           FIPS Pub 6-4. These two numbers
                                           correspond to the first two digits
                                           of the panel number.

  COMM_NO     Text     4        Y          Community Number. This is the
                                           four-digit number assigned by FEMA
                                           to each community for tracking
                                           purposes under the NFIP. On newer
                                           DFIRMs the State FIPS and the
                                           community number appear below the
                                           community name.

  CID         Text     6        Y          Community Identification Number.
                                           This is the six-digit community
                                           identification number assigned by
                                           FEMA. It is created by combining
                                           the State FIPS code with the
                                           COMM_NO. If the jurisdiction does
                                           not have a community number
                                           assigned by FEMA, the CID is
                                           created by combining the State
                                           FIPS code with the abbreviation
                                           contained in the COMM_NO field
                                           (FED, ST, or OTHR).

  ANI_TF      Text     1        Y          Area Not Included. Acceptable
                                           values for this field are listed
                                           in the D_ANI_TF table.
  ----------- -------- -------- ---------- ----------------------------------

-   Transportation (S_Trnsport) (Required if applicable):

This spatial file provides transportation features that cover the
geographic extent of the flood map project.

[]{#__RefHeading___Toc210064174 .anchor}Table M.2-6. S_Trnsport Spatial
File

  ------------- ------- -------- ---------- ---------------------------------
  Field         Type    Length   Required   Description

  TRANS_LID     Text    50       Y          Transportation Feature Type.
                                            These line types indicate how the
                                            feature must be depicted on the
                                            hardcopy FIRM. Acceptable values
                                            for this field are listed in the
                                            D_Trans_Typ table.

  FEAT_NM1      Text    100      Y          Feature Name 1. This is the
                                            primary name of the feature. For
                                            areas that have more than one
                                            name, this would be the primary
                                            name with subsequent names shown
                                            in fields below. Route numbers
                                            and "Intercoastal Waterway" would
                                            also be included in this item.

  FEAT_NM2      Text    100      N          Feature Name 2. This is the
                                            secondary name of the feature.
  ------------- ------- -------- ---------- ---------------------------------

-   Hydrology (S_Hydro_Ln and/or S_Hydro_Ar) (Required if applicable):

This spatial file contains the stream centerlines for the study area
that extend beyond the community boundary by 1,000 to 2,000 feet. This
enables the capture of effective segments that may meander just outside
the community boundary.

[]{#__RefHeading___Toc210064175 .anchor}Table M.2-7. S_Hydro_LN and/or
S_Hydro_Ar Spatial File

  ------------- -------- -------- ---------- --------------------------------
  Field         Type     Length   Required   Description

  WTR_NM        Text     100      Y          Surface Water Feature Name. This
                                             is the formal name of the
                                             surface water feature, as it
                                             will appear on the DFIRM.
  ------------- -------- -------- ---------- --------------------------------

-   USGS HUCs (S_HUC) (Required if applicable):

This spatial file contains the HUCs for the study area that fall within
and also those that extend beyond the community boundary. This will
enable the capture of appropriate drainage basins, including those
outside the community boundary.

[]{#__RefHeading___Toc210064176 .anchor}Table M.2-8. S_HUC Spatial File

  ----------- -------- -------- ---------- ----------------------------------
  Field       Type     Length   Required   Description

  HUC_CODE    Text     8        Y          Unique hydrologic unit based on
                                           USGS levels of classification in
                                           the hydrologic unit system

  HUC_NAME    Text     39       Y          The primary name of the hydrologic
                                           unit
  ----------- -------- -------- ---------- ----------------------------------

#### Scoping Meeting Data Requirements {#scoping-meeting-data-requirements .unnumbered}

-   Scoping Meeting Invitation Letters (STFIPS+PCOMM#\_MeetingInvit)
    (Required): In written format, provide the Scoping Meeting
    invitation letters. These letters should: identify the time and
    place for the meeting; provide contact information for the Project
    Manager or Management Staff; and discuss the intended purpose of the
    meeting.

-   Scoping Meeting Agenda (STFIPS+PCOMM#\_MeetingAgda) (Required): In
    written format, provide the Scoping Meeting agenda which identifies
    date, time, location, FEMA participants, topics to be covered, and
    an estimated time for each.

-   Scoping Meeting Attendance Record (STFIPS+PCOMM#\_MeetingAttd)
    (Required): In written format, provide a Scoping Meeting attendance
    record containing contact information for all attendees at the
    Scoping Meeting.

-   Scoping Meeting Summary (STFIPS+PCOMM#\_MeetingSum) (Required): In
    written format, provide a Scoping Meeting summary, summarizing
    pertinent meeting information including key topics and community map
    update requests.

-   Memorandum of Agreement Forms (STFIPS+PCOMM#\_MOA) (Required): In
    written format, provide the Memorandum of Agreement (MOA) Form(s).
    FEMA has developed MOA forms that are signed by FEMA and the
    participating communities as an acknowledgement of the Flood Study
    project and an agreement to work together toward a common goal.

#### Post-Scoping Meeting Data Requirements {#post-scoping-meeting-data-requirements .unnumbered}

-   Mapping Activity Statement (STFIPS+PCOMM#\_MAS) (Required if
    Applicable): In written format, provide MAS forms. FEMA has
    developed MAS forms covering the tasks and standards for Flood Map
    Projects that are being undertaken under a CTP Program Partnership
    Agreement.

-   Statement of Work (STFIPS+PCOMM#\_SOW) (Required if Applicable): In
    written format, provide SOW forms. FEMA has developed SOW forms
    covering the tasks and standards for FEMA-contracted Flood Map
    Projects.

-   Scoping Report (STFIPS+PCOMM#\_ScopingReport) (Required if
    Applicable): The Final Scope of the project. This may be documented
    in a Scoping Report, MAS, or SOW depending on the Region's
    preference and/or contract type.

-   Final Study Streams (S_Fin_Study_Ln) (Required): This spatial file
    contains each stream segment and/or coastline contained within
    either the DFIRM database or NHD 100k coverage for flood sources
    included in the SOW for the Flood Map Project update. This file
    should provide an inventory of stream mileage by effective and
    proposed zone and study type for the project area.

[]{#__RefHeading___Toc210064177 .anchor}Table M.2-9. S_Fin_Study_Ln
Spatial File

  ------------------- ------ -------- ---------- -----------------------------
  Field               Type   Length   Required   Description

  COUNTY              Text   100      Y          County Name

  Community           Text   100      Y          Community Name

  STATE               Text   50       Y          State Name

  CID                 Text   6        Y          Community Identification
                                                 Number. This is the six-digit
                                                 community identification
                                                 number assigned by FEMA. It
                                                 is created by combining the
                                                 State FIPS code with the
                                                 COMM_NO. If the jurisdiction
                                                 does not have a community
                                                 number assigned by FEMA, the
                                                 CID is created by combining
                                                 the State FIPS code with the
                                                 abbreviation contained in the
                                                 COMM_NO field (FED, ST, or
                                                 OTHR).

  sT_FIPS             Text   2        Y          State FIPS. This is the
                                                 two-digit code that
                                                 corresponds to the State FIPS
                                                 code. This is a standard
                                                 numbering system that is used
                                                 by the Federal government.
                                                 Defined in FIPS Pub 6-4,
                                                 these two numbers correspond
                                                 to the first two digits of
                                                 the panel number.

  Eff_Zone            Text   25       Y          From effective study.
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_Zone table.

  LEVEL_EFF           Text   25       Y          Effective Level of Study.
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_Study_Typ table.

  Flood_typ           Text   50       Y          Flooding type. Acceptable
                                                 values for this field are
                                                 listed in the D_Flooding Type
                                                 table.

  Strm_Name           Text   100      Y          Flooding Source Name

  Length              Text   25       Y          Length of stream associated
                                                 with a level of study

  FBS_TF              Text   1        Y          Are stream segments
                                                 anticipated to meet
                                                 Floodplain Boundary Standard
                                                 (FBS)? Acceptable values for
                                                 this field are listed in the
                                                 D_FBS_TF table.

  Ranking             Text   5        N          Forced Ranking based on
                                                 local/regional input

  LEVEL_FIN           Text   25       Y          Final Level of Study.
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_Study_Typ table.
  ------------------- ------ -------- ---------- -----------------------------

-   Final Study Areas (S_Fin_Study_Ar) (Required if applicable): This
    spatial file contains flood sources included in the SOW for the
    Flood Map Project update within either the DFIRM database or the
    NHD-delineated, 1-square mile subbasins for the project area. This
    file should provide an inventory of square miles by effective and
    proposed zone and study type for the project area.

[]{#__RefHeading___Toc210064178 .anchor}Table M.2-10. S_Fin_Study_Ar
Spatial File

  ------------------- ------ -------- ---------- -----------------------------
  Field               Type   Length   Required   Description

  COUNTY              Text   100      Y          County Name

  Community           Text   100      Y          Community Name

  STATE               Text   50       Y          State Name

  CID                 Text   6        Y          Community Identification
                                                 Number. This is the six-digit
                                                 community identification
                                                 number assigned by FEMA. It
                                                 is created by combining the
                                                 State FIPS code with the
                                                 COMM_NO. If the jurisdiction
                                                 does not have a community
                                                 number assigned by FEMA, the
                                                 CID is created by combining
                                                 the State FIPS code with the
                                                 abbreviation contained in the
                                                 COMM_NO field (FED, ST, or
                                                 OTHR).

  ST_FIPS             Text   2        Y          State FIPS. This is the
                                                 two-digit code that
                                                 corresponds to the State FIPS
                                                 code. This is a standard
                                                 numbering system that is used
                                                 by the Federal government.
                                                 Defined in FIPS Pub 6-4.
                                                 These two numbers correspond
                                                 to the first two digits of
                                                 the panel number.

  Eff_Zone            Text   25       Y          From effective study.
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_Zone table.

  LEVEL_EFF           Text   25       Y          Effective Level of Study.
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_Study_Typ table.

  Flood_typ           Text   50       Y          Flooding type. Acceptable
                                                 values for this field are
                                                 listed in the D_Flooding Type
                                                 table.

  Stream_Name         Text   100      Y          Flooding Source Name

  Area                Text   25       Y          Square mileage of subbasin
                                                 associated with a level of
                                                 study

  FBS_TF              Text   1        Y          Are stream segments
                                                 anticipated to meet FBS?
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_FBS_TF table.

  Ranking             Text   5        N          Forced Ranking based on
                                                 local/regional input

  LEVEL_FIN           Text   25       Y          Final Level of Study.
                                                 Acceptable values for this
                                                 field are listed in the
                                                 D_Study_Typ table.
  ------------------- ------ -------- ---------- -----------------------------

-   Community Mapping Needs (S_Needs_Ar) (Required, if applicable):
    **See Table M.2-1 for attribute table specifications.**

    This spatial file contains existing community mapping needs
    identified during Scoping Assessment that will be resolved by the
    SOW. Only the attribute table of records resolved will be submitted.
    This file also contains additional mapping needs that have been
    identified during project scoping that will either be resolved or
    unmet by the SOW. The geospatial files for the new records will be
    submitted and will adhere to the specifications in Table M.2-1 of
    these guidelines.

-   Community Mapping Requests (S_Requests) (Required, if applicable):
    **See Table M.2-2 for attribute table specifications.**

    This spatial file contains existing community requests identified
    during Scoping Assessment that will be resolved by the SOW. Only the
    attribute table for records resolved will be submitted. This file
    also contains community flood data requests that have been
    identified during project scoping that cannot be justified as needs
    or base map change requests identified during project scoping. The
    geospatial files for the new records will be submitted adhering to
    the specification in Table M.2-2 of these guidelines. There are two
    feature classes to capture these requests as either a polygon or
    point. Submit either one or both as applicable.

-   Specific Needs Information Table (Specific Needs_Info) (Required, if
    applicable): **See Table M.2-3 for attribute table specifications.**

    This table contains general information that will be associated, via
    the Need_ID attribute, with every new Need or Request that is
    identified during project scoping.

-   Proposed DFIRM Panel Index (S-Prp_FirmPan) (Required):

    This spatial file contains the proposed panel scheme for the study
    area.

[]{#__RefHeading___Toc210064179 .anchor}Table M.2-11. S_Prp_FirmPan
Spatial File

+----------+----+-----+--------+--------------------------------------+
| Field    | Ty | Len | Re     | Description                          |
|          | pe | gth | quired |                                      |
+==========+====+=====+========+======================================+
| ST_FIPS  | Te | 11  | Y      | State FIPS.                          |
|          | xt |     |        |                                      |
+----------+----+-----+--------+--------------------------------------+
| PCOMM    | Te | 4   | N      | Community or County Identification   |
|          | xt |     |        | Number. This is the 3rd through the  |
|          |    |     |        | 6th digits of the panel number. For  |
|          |    |     |        | community based maps this            |
|          |    |     |        | corresponds to the FEMA Community    |
|          |    |     |        | Identification number. For           |
|          |    |     |        | countywide maps, this is the county  |
|          |    |     |        | (or county equivalent) FIPS code     |
|          |    |     |        | with a "C".                          |
+----------+----+-----+--------+--------------------------------------+
| PANEL    | Te | 4   | Y      | Panel Number. This is the 7th        |
|          | xt |     |        | through the 10th digits in the       |
|          |    |     |        | complete panel number. This is       |
|          |    |     |        | assigned by the scale of the map and |
|          |    |     |        | the position within the community or |
|          |    |     |        | county. The panel number scheme is   |
|          |    |     |        | described in detail in Appendix K of |
|          |    |     |        | these Guidelines.                    |
|          |    |     |        |                                      |
|          |    |     |        | .                                    |
+----------+----+-----+--------+--------------------------------------+
| SUFFIX   | Te | 1   | N      | Map Suffix. This is the final digit  |
|          | xt |     |        | in the complete panel number. This   |
|          |    |     |        | is a letter suffix at the end of the |
|          |    |     |        | panel number.                        |
+----------+----+-----+--------+--------------------------------------+
| FIRM_PAN | Te | 11  | N      | DFIRM Panel Number. This is the      |
|          | xt |     |        | complete DFIRM panel number, which   |
|          |    |     |        | is made up of ST_FIPS, PCOMM, PANEL, |
|          |    |     |        | and SUFFIX. This is the 11-digit     |
|          |    |     |        | DFIRM panel number that is shown in  |
|          |    |     |        | the title block of the map.          |
+----------+----+-----+--------+--------------------------------------+
| PANEL    | Te | 35  | Y      | Panel Type. The type of DFIRM panel  |
|          | xt |     |        | that identifies whether the panel is |
|          |    |     |        | printed or not printed and whether   |
|          |    |     |        | it is community based or countywide  |
|          |    |     |        | mapping. Acceptable values for this  |
|          |    |     |        | field are listed in the D_Panel_Typ  |
|          |    |     |        | table.                               |
+----------+----+-----+--------+--------------------------------------+
| SCALE    | Te | 5   | Y      | Map Scale. This is the denominator   |
|          | xt |     |        | of the DFIRM scale as a ratio. For   |
|          |    |     |        | example, 24000 is the denominator    |
|          |    |     |        | for a 1" = 2000' map. Acceptable     |
|          |    |     |        | values for this field are listed in  |
|          |    |     |        | the D_Scale table.                   |
+----------+----+-----+--------+--------------------------------------+

-   Geospatial Data Summary (STFIPS+PCOMM#\_GeoSpatData) (Required): In
    written format, provide an inventory for all data covering the
    entire study area.

-   QC Plan (STFIPS+PCOMM#\_QCPlan) (Required): In written format,
    provide a Quality Control (QC) Plan. This plan documents the QC
    methods and steps to be performed for each task of the Flood Map
    Project.

-   National Metrics (NatMetrics_Info) (Required): This table contains
    the mileage that will meet the FBS and will be either New,
    Validated, or Updated Engineering (NVUE). This information will be
    used as the basis for projecting and reporting progress towards the
    national metrics for Flood Map Modernization.

[]{#__RefHeading___Toc210064180 .anchor}Table M.2-12. NatMetrics_Info
Tabular File

  ------------ ------ -------- ---------- -----------------------------------
  Field        Type   Length   Required   Description

  FBS_MI       Text   5        Y          Estimated number of stream miles
                                          that will meet Floodplain Boundary
                                          Standards for the new FIS

  NVUE_MI      Text   5        Y          Estimated number of stream miles
                                          that will meet NVUE requirements
                                          for the new FIS

  AREA         Text   5        Y          Area (in square miles) being mapped
                                          with new FIS

  TOT_MAP_MI   Text   5        Y          Total number of stream mile that
                                          will be mapped in the new FIS

  POPULATION   Text   10       Y          Population being mapped with new
                                          FIS
  ------------ ------ -------- ---------- -----------------------------------

###  {#section .unnumbered}

### Accepted File Formats

Scoping data must be submitted in one of the following digital formats
listed below:

-   SHP -- ESRI Shapefile format (for all spatial files)

```{=html}
<!-- -->
```
-   Community Mapping Needs -- S_Needs_Ar

-   Community Mapping Requests -- S_Requests

-   Political Area (S_Polbnd)

-   Transportation (S_Trnsport)

-   Hydrology (S_Hydro_Ln and/or S_Hydro_Ar)

-   USGS HUCs (S_HUC)

-   Final Study Streams (S_Fin_Study_Ln)

-   Final Study Areas (S_Fin_Study_Ar)

-   Proposed DFIRM Panel Index (S_Prp_FirmPan)

    -   DOC / PDF (for all text documents)

-   Project Management Team Contact Info (STFIPS+PCOMM#\_ProjectTeam)

-   Project Scoping Initiation Report
    (STFIPS+PCOMM#\_ProjectInitiationReport)

-   Scoping Meeting Invitation Letters (STFIPS+PCOMM#\_MeetingInvit)

-   Scoping Meeting Agenda (STFIPS+PCOMM#\_MeetingAgda)

-   Scoping Meeting Attendance Record (STFIPS+PCOMM#\_MeetingAttd)

-   Scoping Meeting Summary (STFIPS+PCOMM#\_MeetingSum)

-   Memorandum of Agreement Form(s) (STFIPS+PCOMM#\_MOA)

-   Mapping Activity Statement Form(s) (STFIPS+PCOMM#\_MAS)

-   Statement of Work Form(s) (STFIPS+PCOMM#\_SOW)

-   Scoping Report (STFIPS+PCOMM#\_ScopingReport)

-   Geospatial Data Summary (STFIPS+PCOMM#\_GeoSpatData)

-   QC Plan (STFIPS+PCOMM#\_QCPlan)

    -   XLS / MDB / DBF (for all tabular information files)

-   Specific Needs Information (Specific_Needs_Info)

-   Community Contact Info (Contact_Info)

-   National Metrics (NatMetrics_Info)

### Metadata

Metadata is not required for scoping.

### Transfer Methodology 

Scoping data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."
Mapping Partners can also submit files on one of the following
electronic media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

### Directory Structure and Folder Naming Conventions

Scoping Assessment deliverables will be uploaded, stored, and maintained
in FEMA's needs management system. If a Mapping Partner does not have
access to FEMA's needs management system, the data may be submitted to
the FEMA Lead.

-   Scoping Assessment

```{=html}
<!-- -->
```
-   Mapping Needs

-   Requests

-   Needs / Requests Submittal Information

The Project Scoping files in section M.2.2 -- Requirements, must be
submitted consistent with the following directory structure. The
following folders can be created either on a local work space (i.e., a
personal computer) or within the work space for the community on the
MIP. If the following folders are generated locally, these newly created
folders and their contents must be uploaded to the MIP.

The *Scoping* folder is located on the root directory for each community
submittal on the MIP (e.g., State/County_FIPS/MIP Project_ID). The
Scoping deliverables must be uploaded to the applicable subfolders
according the following directory structure:

-   Scoping/Project Scoping Initiation

-   Project Management Team

-   Community Contact List

-   Project Scoping Initiation Report

-   Political Area

-   Transportation

-   Hydrology -- Streams/Lakes/Ponds

-   HUC

-   Scoping/Scoping Meeting

-   Meeting Invitations

-   Meeting Agenda/Meeting Minutes

-   Meeting Attendance Record

-   Meeting Summary

-   MOA Forms

-   Scoping/Post-Scoping

-   Scoping Report, SOW, or MAS

-   Final Study Streams and/or Areas

-   Community Mapping Needs and/or Requests

-   Needs/Requests Submittal Information

-   Proposed DFIRM Panel Index

-   Geospatial Data Summary

-   QA/QC Plan

-   National Metrics

### Data Identification Requirements

When data are mailed to FEMA, all submitted digital media must be
labeled with at least the following information:

-   Mapping Partner's name;

-   Community name and State for which the FIS was prepared;

-   Scoping Data; and

-   Date of submission (formatted mm/dd/yyyy).

-   Disk \[*sequential number*\] of \[*number of disks*\] (if not
    uploaded through workflow). The media must be numbered sequentially,
    starting at Disk 1. \[Number of disks\] represents the total number
    of disks in the submission if the data is not uploaded through
    workflow on the MIP.

# Base Map Submittal Standards

## Overview 

The goal of this section is to describe the format and type of base map
data required to be submitted to FEMA for FISs. All data must be
submitted in digital format. The Mapping Partner performing "Acquire
Base Map" is required to submit the data in this section.

The submitting Mapping Partner must retain copies of all Project-related
data for a period of 3 years. The submitting Mapping Partner will need
these data for responding to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the new or revised FIS report and FIRM.

-   

## Requirements 

### Data Files 

The minimum required data for the basic mapping data submission are the
source mapping data and the base map files used in the study. These data
can be contained in a single file or in tiled files. These submissions
must be compliant with the base map files in Appendix L. The following
information must be submitted:

-   Orthophotos;

-   Road and railroad centerline data;

-   Political boundaries;

-   A narrative describing the scope of work, direction from FEMA,
    issues, information for next Mapping Partner, etc.;

-   Base map files;

-   Airport data;

-   River, stream, lakes, structures (levees), and shorelines;

-   Parks and forests;

-   Public land survey system (PLSS);

-   Feature names;

-   NGS Benchmarks;

-   USGS Quad index; and

-   DOQs or other imagery index.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner assigned to "Acquire Base Map." General correspondence
is the written correspondence generated or received by the Mapping
Partner assigned to fulfill the requirements of acquiring the base map.
Correspondence includes any documentation generated during this task
such as letters; transmittals; memorandums; general status reports and
queries; special problem reports (SPRs); technical issues that need to
be documented; direction given by FEMA; and internal communications,
routing slips, and notes that were relevant to the performance of this
task. Contractual documents, such as a signed SOW or MAS, are not to be
submitted as a part of the DCS.

### Certification of Work

FEMA-funded base map data development must be certified using the
Certification of Compliance Form provided in Figure M-8 in section M.10.
A PDF file of this form with the original signature, data, and seal
affixed to the form must be submitted digitally in the general directory
identified in section M.3.2.8. This form must be signed by a registered
or certified professional from the firm contracted to perform the work,
or by the responsible official of a government agency.

### Accepted File Formats 

Base map data must be submitted in a georeferenced, digital format.
These data can be contained in a single file or in a tiled set of files.
Any tiled data must have an accompanying index spatial file. The
following formats are acceptable for files:

-   BIL - Band Interleaved by Line (image format linked with satellite
    derived imagery);

-   ESRI Geodatabase;

-   ESRI Shapefile;

-   GeoTIFF - TIFF variant enriched with GIS-relevant metadata;

-   IMG - ERDAS IMAGINE image file format;

-   MrSID - Multi-Resolution Seamless Image Database;

-   PDF - For general correspondence and project narrative;

-   PNG and JPEG - georeferenced; and

-   JPEG2000.

### Metadata 

A metadata file that complies with the FEMA/FGDC Metadata Profiles
(available on the MIP via "Tools and Links") in XML format must be
included with the submittal. The profiles follow the FGDC Content
Standard for metadata and define additional domains and business rules
for some elements that are mandatory for FEMA, based on the specific
submittal type. For each spatial data source in the metadata file, the
Mapping Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to the
MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)) or by
mailing the files to FEMA on one or more of the following electronic
media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data are mailed to FEMA, all submitted electronic media must be
labeled with at least the following information:

-   Mapping Partner's name;

-   Community name and State for which the FIS was prepared;

-   Base Mapping Data;

-   Date of submission (formatted mm/dd/yyyy);

-   Disk \[*sequential number*\] of \[*number of disks*\]. The media
    must be numbered sequentially, starting at Disk 1. \[Number of
    disks\] represents the total number of disks in the submission.

### Transfer Methodology 

Base Map Data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."

### Directory Structure and Folder Naming Conventions

The files presented in section M.3.2 Requirements must be submitted to
the MIP or mailed to FEMA within the following directory structure. The
following folders can be created either on a local work space (i.e., a
personal computer) or within the work space for the community on the
MIP. If the following folders are generated locally, these newly created
folders and their contents must be uploaded to the MIP.

-   \\General

```{=html}
<!-- -->
```
-   XML_format metadata file

-   Project narrative

-   Certification

    -   \\Correspondence

```{=html}
<!-- -->
```
-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and notes.

    -   \\Base Map\\Spatial Files

-   Road and railroad centerline data

-   Airport data

-   River, stream, lakes, structures (levees), and shorelines

-   Parks and forests

-   PLSS

    -   Range, township, and section lines

-   Feature names

-   NGS Benchmarks

-   Political boundaries

-   USGS Quad index

-   DOQs or other imagery index

-   Orthophotos

-   Base map index

# Terrain Submittal Standards

## Overview 

This section describes the format and type of terrain data required to
be submitted to FEMA for FISs. All data must be submitted in digital
format. The Mapping Partner performing "Develop Topographic Data" is
required to submit the data in this section.

The Mapping Partner should refer to Appendix A of these Guidelines for
guidance on terrain data production. This section is not intended to
detail the specifications and procedures for coastal hydrographic
surveys. The reader is referred to the following sources for details on
coastal surveys:

-   National Oceanic and Atmospheric Administration (NOAA) NOS
    Hydrographic Survey Specifications and Deliverables (April 2007);

-   NOAA Office of Coast Survey Hydrographic Surveys Division Field
    Procedures Manual (March 2007); and

-   U.S. Army Corps of Engineers (USACE) National Coastal Mapping
    Program Joint LiDAR Bathymetry Technical Center for Expertise.

The submitting Mapping Partner must retain copies of all Project-related
data for a period of 3 years. The submitting Mapping Partner will need
these data for responding to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the new or revised FIS report and FIRM.

## Requirements 

### Data Files 

The minimum data required for the terrain data submission are the source
terrain and topographic maps from the terrain data used in the study.
These data can be contained in a single file or in tiled files. When
tiled files are submitted, they must be accompanied by a tiling index
file. If any processing has been performed, the original and final files
must be submitted as well. For instance, if terrain data were blended
from three different sources to create the final terrain data, the
original of the three sources and the final terrain file that results
from the blending process must be submitted. This information is
required to be a georeferenced, digital submittal. The following
information must be submitted when it is used to perform a study:

-   LiDAR data (bare earth and all returns);

-   Tiling index for data files;

-   Breaklines and Mass Points;

-   Contours;

-   Bathymetry;

-   Digital Elevation Models (DEMs);

-   Hydro-corrected DEMs;

-   Triangulated Irregular Networks (TINs);

-   Hydro-corrected TINs;

-   Topographic maps from the terrain data;

-   USGS topographic data;

-   All other terrain data; and

-   A narrative describing the SOW, direction from FEMA, issues,
    information for next Mapping Partner, etc.

-   LiDAR data generated as part of the project must be submitted as two
    separate files: one for bare earth only, and one for all returns if
    bare earth processing was performed as part of this project. For
    existing LiDAR data not processed as part of the project, the bare
    earth data must be submitted, and the submittal of the all returns
    data (if available) is optional.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner assigned to "Develop Topographic Data." General
correspondence is the written correspondence generated or received by
the Mapping Partner to fulfill the requirements of developing
topographic data. Correspondence includes any documentation generated
during this task such as letters; transmittals; memoranda; general
status reports and queries; SPRs; technical issues that need to be
documented; direction given by FEMA; and internal communications,
routing slips, and notes that were relevant to the performance of this
task. Contractual documents, such as a signed SOW or MAS, are not to be
submitted as a part of this appendix.

### Certification of Work

FEMA-funded terrain data development must be certified using the
Certification of Compliance Form provided in Figure M-8 in section M.10.
A PDF file of this form with the original signature, data, and seal
affixed to the form must be submitted digitally in the general directory
identified in section M.4.2.8. This form must be signed by a registered
or certified professional from the firm contracted to perform the work,
or by the responsible official of a government agency.

### Accepted File Formats 

Terrain data used to perform the study must be submitted in a
georeferenced, digital format as listed below. These data can be
contained in a single file or in a tiled set of files. Any tiled data
must have an accompanying index spatial file.

-   Contours, Masspoints, and breaklines --Personal geodatabase, DXF, or
    shapefile

-   DEMs -- ESRI grid, GeoTIFF, or ASCII grid

-   LiDAR - LAS file, ASCII x, y, z file

-   PDF for the project narrative, correspondence, and certification

### Metadata 

A metadata file that complies with the FEMA/FGDC Metadata Profiles
(available on the MIP via "Tools and Links") in XML format must be
included with the submittal. The profiles follow the FGDC Content
Standard for metadata and define additional domains and business rules
for some elements that are mandatory for FEMA, based on the specific
submittal type. For each spatial data source in the metadata file, the
Mapping Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to the
MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)) or by
mailing the files to FEMA on one or more of the following electronic
media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all submitted digital media must be labeled
with at least the following information:

-   Mapping Partner's name;

-   Community name and State for which the FIS was prepared;

-   Terrain Data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[*sequential number*\] of \[*number of disks*\]. The media
    must be numbered sequentially, starting at Disk 1. \[Number of
    disks\] represents the total number of disks in the submission.

### Transfer Methodology 

Base Map Data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care".

### Directory Structure and Folder Naming Conventions

The files presented in section M.4.2 Requirements must be submitted to
the MIP or mailed to FEMA within the following directory structure. The
following folders can be created either on a local work space (i.e., a
personal computer) or within the work space for the community on the
MIP. If the following folders are generated locally, these newly created
folders and their contents must be uploaded to the MIP. Terrain files
are arranged into appropriate directories based on data type.

-   \\General

```{=html}
<!-- -->
```
-   XML_format metadata file

-   Certification

-   Project narrative

    -   \\Correspondence

-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and notes.

    -   \\Terrain\\All_Returns

-   LIDAR data -- All Returns

-   LIDAR Tile Index spatial file (if used)

    -   \\Terrain\\Bare_Earth

-   LIDAR data -- Bare Earth Points

-   LIDAR Tile Index spatial file (if used)

    -   \\Terrain\\Breaklines

-   3D breakline spatial files

-   3D breakline Tile Index spatial file (if used)

-   2D breakline spatial files

-   2D breakline Tile Index spatial file (if used)

-   Mass Points

    -   \\Terrain\\Contours

-   Contour spatial files with a contour interval of xx_xx
    (i.e."Contour_5_ft")

-   Contour Tile Index spatial file (if used)

-   Bathymetric files

-   Bathymetric Tile Index spatial file (if used)

    -   \\Terrain\\DEM

-   Uncorrected DEM files with a minor cell spacing of xx_xx
    (i.e."DEM_50_ft")

-   Tile Index spatial file (if used)

    -   \\Terrain\\HDEM

-   Hydrologically correct DEM files with a minor cell spacing of xx_xx
    (i.e. "HDEM_50_ft")

-   Tile Index spatial file (if used)

    -   \\Terrain\\TIN

-   Uncorrected TIN files

-   Tile index spatial file (if used)

    -   \\Terrain\\HTIN

-   Hydrologically correct TIN files

-   Tile Index spatial file (if used)

    -   \\Terrain\\Final

-   Final terrain data

-   Final terrain Tile Index spatial file (if used)

# Survey Submittal Standards

## Overview 

The purpose of this section is to provide the type and format of survey
data that must be submitted to FEMA for FISs. All data must be submitted
in digital format. The Mapping Partner contracted to "Perform Field
Survey" is required to submit the data in this section.

This section is not intended to specify in-process compilation or
procedures, but rather to present the specifications and requirements
for output and deliverables. The Mapping Partner should refer to
Appendix A of these Guidelines for guidance on the performance of
surveying. The formats specified in this section are required for new
surveys for FEMA-funded studies. Surveys taken from previous studies, or
not associated with the current study, do not need to be translated to
the format specified in this section. This survey data must be uploaded
in the native data format.

This section will focus on the data that are obtained during the survey
of the following features:

-   Cross Sections;

-   Transects;

-   Temporary Bench Marks;

-   High Water Marks; and

-   Structures

```{=html}
<!-- -->
```
-   Bridges

-   Channels

-   Culverts

-   Dams

-   Levees

-   Coastal Structures

Survey data must be referenced to a standard coordinate system, employ a
standard projection, and specify the horizontal and the vertical datums
used. These positional references are established prior to the field
data collection and topographic mapping phase of the project. All
planimetric and topographic features must be collected and referenced to
this coordinate system and projection. A detailed discussion of aerial
mapping and surveying specifications, which includes horizontal and
vertical control for new mapping, is provided in Appendix A of these
Guidelines. A discussion of vertical datum selection and conversion is
provided in Appendix B of these Guidelines.

The submitting Mapping Partner must retain copies of all project-related
data for a period of 3 years. The submitting Mapping Partner will need
these data for responding to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files 

The following deliverables are required for survey submittals:

-   Survey Files;

-   Digital Photographs;

-   Digital Sketches; and

-   A narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

Survey notebooks can be included but are not required. Consistent data
collection methods must be followed for FEMA-funded survey data
collection in support of FISs. All survey data must be collected and
delivered in the appropriate coordinate system and vertical datum and
use standard description codes (data dictionary) and standard naming and
file types.

#### Naming Conventions

All structures and cross sections must have a unique alpha three
character ID as a feature name. A feature name (three character ID) must
have the abbreviated stream name followed by the number of the feature
on that stream. All numbers must start from the downstream limit and
increase upstream. Names must begin with an abbreviation consisting of
the first three letters of the stream name. For example, **Swi**ft Creek
would be **SWI**. In numbering structures and cross sections, it is
suggested to use a numbering system that allows for intermediate numbers
to be added later in cases where a structure or cross section is skipped
or added (e.g. 100, 200, 300, etc.). Some variation is allowable if
multiple streams in the same study area begin with the same three
letters.

For unnamed tributaries, a convention is to use the nearest named stream
that the unnamed stream flows into as part of the naming convention. For
example, an unnamed tributary that flows into Swift Creek would be
SWI_5_1 numbered sequentially from downstream to upstream.

As part of the reconnaissance process, Mapping Partners must review all
the stream names to determine the best way to name the files and
streams. Before collecting survey data, basic naming and location for
each hydraulic feature to be surveyed should be set and sketched out on
work sheets.

#### Survey Data File Naming Convention and Format

Survey data files must also be organized and named based on the stream
name (Swift Creek 3-15-07.txt). The date in the file name is the date
the deliverable file was created. Data files must be stored in a comma
delimited text file, spreadsheet, or database format and include all
hydraulic feature data and bench marks surveyed for that stream. The
file must be developed in a tabular format that includes columns for
point number, northing, easting, elevation, and description code.
Northing and easting column headings must include coordinate system and
units. The elevation column heading must include datum and units. The
description column must list the description code per the data
dictionary. An example file is shown in Table M.5-1. All point data
associated with structures or features may be listed in one table. As
needed, the easting and northing units can be converted into latitude
and longitude.

[]{#__RefHeading___Toc210064181 .anchor}Table M.5-1. Survey Data File
Example

(Hydraulic Feature SWI-32400 on Swift Creek)

  --------- ------------------ ------------------ -------------- ---------
  PT NO.    NORTHING WV SPC S  EASTING WV SPC S   ELEV NAVD 1988 CODE
            NAD 1983 (SFT)     NAD 1983 (SFT)     (FT)           

                                                                 

  32400     468854.208         1737859.314        607.66         GR

  32401     468865.357         1737850.764        602.14         GR

  32402     468875.480         1737842.719        597.75         GR

  32403     468881.852         1737838.918        593.52         TOBL

  32404     468887.119         1737835.142        591.86         TOSL

  32405     468897.284         1737830.623        581.12         CH

  32406     468900.368         1737828.459        581.48         CHCL

  32407     468905.686         1737824.840        581.16         CH

  32408     468912.298         1737821.658        583.91         TOSR

  32409     468917.314         1737816.902        592.42         TOBR

  32410     468926.152         1737809.303        596.96         GR

  32411     468931.695         1737804.390        598.74         GR

  32412     468942.672         1737796.103        605.24         GR
  --------- ------------------ ------------------ -------------- ---------

#### Survey Photos and Sketches

Every hydraulic feature must have a unique identification name that will
also be shared by the photos with additional suffixes to indicate
location. Five digital photos must be taken for each structure and two
digital photos taken for each cross section. For example, a structure on
Swift Creek identified as "SWI-100" would be as follows:

-   SWI-100-DSCH.jpg -- downstream channel (from the structure looking
    downstream)

-   SWI-100-DSFACE.jpg -- downstream face of the structure

-   SWI-100-OTXS.jpg -- overtopping cross section looking left to right

-   SWI-100-USFACE.jpg -- upstream face of the structure

-   SWI-100-USCH.jpg -- upstream channel

For example, a cross section on Swift Creek would be as follows:

-   SWI-100-DSCH.jpg -- downstream channel (from the structure looking
    downstream)

-   SWI-100-USCH.jpg -- upstream channel

The surveyor must keep a photo log for each stream surveyed so that
photo naming and completeness can be checked. The photo log does not
have to be submitted as a deliverable.

Photos must be limited to 1 megabyte in size and stored in .jpg (jpeg)
format for maximum compression. Photos are critical and are used to
determine Manning's roughness coefficient and hydraulic model
development. Photos must be taken with the clearest view and reviewed
for clarity, especially in low light conditions, before leaving the
site. In locations where obstructions may prevent a single picture from
being taken to represent the required view, multiple photos may be taken
and stitched together to form the final view.

A survey sketch must be prepared at all hydraulic features, including
cross sections (e.g., Figures M-3 and M-5). The sketch must include
notations and measurements representing the structural geometry and the
natural ground and show description codes and shot numbers from the
field survey so that the sketch can be related to the field survey. Each
sketch must include a planimetric and profile view (viewed looking
downstream left to right, upstream face of structures) and show the
following items: piers/piles, channel banks, channel, direction of flow,
rails, deck, footings, abutments, culvert inverts, shape and size of
opening, bench mark location, skew to flow, and north arrow.

Sketches must be scanned and named. Scans must be limited to 1 megabyte
(approximately 200 dpi) and stored in PDF or .jpg (jpeg) format. File
names must be based on stream and structure/cross-section number (e.g.,
SWI-100-SKETCH.jpg).

Digital deliverables including points, photos, and sketches must be
organized by stream name.

#### Survey Codes

Table M.5-2 lists the required survey codes and description that must be
used for new survey data submissions. Figure M-1 through figure M-7 show
specific examples for some of the field survey point locations and the
corresponding survey codes. Annotation of photographs, such as those
provided in figure M-1 and M-3, is not required. All annotated
photographs provided in this sub-section are for informational purposes
only and show the locations of data points with corresponding survey
codes for reference.

[]{#__RefHeading___Toc210064182 .anchor}Table M.5-2. Survey Codes

  --------------------------------------------------------------------------
  **CODE**    **DESCRIPTION**   **FIELD SURVEY LOCATION**
  ----------- ----------------- --------------------------------------------
  ABT         Abutment          face/foot of abutment of bridge

  ALPT1       Alignment Point   upstream left side of structure and combined
              One               with ALPT2 to determine skew

  ALPT2       Alignment Point   upstream right side of structure and
              Two               combined with ALPT1 to determine skew

  BOCEDS      Back Of Curb Edge where slope meets top of culvert or top of
              Down Stream       headwall above culvert centerline on
                                downstream end for determining outlet
                                projection

  BOCEUS      Back Of Curb Edge where slope meets top of culvert or top of
              Up Stream         headwall above culvert centerline on
                                upstream end for determining inlet
                                projection

  BRCL        Bridge Centerline centerline of bridge in overtopping section

  CH          Channel           stream bottom between TOS shots

  CHCL        Channel           center of the main flow area of the stream
              Centerline        

  CUL         Culvert Shape     multiple CUL codes can be used to define
                                shapes for culverts, especially irregular
                                shapes

  CULCL       Culvert           centerline of culvert in overtopping section
              Centerline        

  CULDSCR     Culvert Down      the highest point of the downstream end of a
              Stream Crown      culvert

  CULDSINV    Culvert Down      the lowest point of the downstream end of a
              Stream Invert     culvert

  CULUSCR     Culvert Up Stream the highest point of the upstream end of a
              Crown             culvert

  CULUSINV    Culvert Up Stream the lowest point of the upstream end of a
              Invert            culvert

  DAMCL       Dam Centerline    the high point of a dam

  EOB         End Of Bridge     end of the bridge deck at the road elevation

  ERM         Elevation         Permanent elevation monument. An ERM must be
              Reference Mark    set at every structure and at cross sections
                                if they are more than half a mile to the
                                nearest structure.

  FBCL        Foot Bridge       centerline of non-vehicular bridges in
              Centerline        overtopping section

  GDR         Guardrail         top of guardrail at ends to define limit and
                                height

  GDRBOT      Guardrail at      base of guardrail at ends to define and
              Bottom            height

  GR          Ground            on ground to show elevation changes, used
                                outside TOB shots, between TOB and TOS, and
                                to indicate islands or bars within the
                                channel. When used in channel cross-section
                                surveys, a GR point must be placed at least
                                15 feet past the top of bank or until there
                                is no overhead obstruction from foliage. If
                                overhead foliage is too thick for the entire
                                overbank area, full valley cross sections
                                should be a consideration for modeling.

  HWMARK      High Water Mark   historical high water marks-mud/stain lines,
                                drift lines, parole evidence, etc.

  INVDS       Invert Down       channel invert at downstream end of
              Stream            structure, used to define paved aprons

  INVUS       Invert Up Stream  channel invert at upstream end of structure,
                                used to define aprons

  LC          Low Chord         change in bridge deck thickness usually at
                                center of a pile row or pier. Multiple low
                                chord codes can be used to define irregular
                                shaped bridges such as arched bridges with
                                the explanation of the multiple LC shots
                                shown in the sketch for the structure.

  LCDSL       Low Chord Down    bottom of deck and beam at the downstream
              Stream Left       left corner of bridge¹

  LCDSR       Low Chord Down    bottom of deck and beam at the downstream
              Stream Right      right corner of bridge¹

  LCUSL       Low Chord Up      bottom of deck and beam at the upstream left
              Stream Left       corner of bridge¹

  LCUSR       Low Chord Up      bottom of deck and beam at the upstream
              Stream Right      right corner of bridge¹

  PIER        Pier              the up and downstream centerline of a pier

  PILE        Pile              the up and downstream centerline of a row of
                                piles

  RAIL        Rail              top of rail to define limits and height of
                                railing on structures

  RAILBOT     Rail Bottom       bottom of rail to define limits and height
                                of railing on structures

  RDCL        Road Centerline   the centerline on a crowned road or the high
                                side of a road with super elevation

  SFLOOR      Sea Floor         shots either direct or combination of
                                bathymetric and conventional/GPS survey of
                                coastal area

  TEMP        Temporary Control temporary control point used to for data
              Point             collection of cross sections and structures

  TOB         Top Of Bank       top of bank in a multiple channel scenario

  TOBL        Top Of Bank Left  break point from over bank to channel on the
                                left side when looking downstream

  TOBR        Top Of Bank Right break point from over bank to channel on the
                                right side when looking downstream

  TOD         Top Of Deck       to show an irregular arch or dip in a bridge
                                deck between the bridge corner shots

  TODDSL      Top Of Deck Down  downstream left corner of a bridge on the
              Stream Left       deck directly above the LCDSL shot to
                                measure deck thickness and width¹

  TODDSR      Top Of Deck Down  downstream right corner of a bridge on the
              Stream Right      deck directly above the LCDSR shot to
                                measure deck thickness and width¹

  TODUSL      Top Of Deck Up    upstream left corner of a bridge on the deck
              Stream Left       directly above the LCUSL shot to measure
                                deck thickness and width¹

  TODUSR      Top Of Deck Up    upstream right corner of a bridge on the
              Stream Right      deck directly above the LCUSR shot to
                                measure deck thickness and width¹

  TOS         Toe Of Slope      the toe in a multiple channel scenario

  TOSL        Toe Of Slope Left break point from channel bank to channel bed
                                on the left side when looking downstream

  TOSR        Toe Of Slope      break point from channel bank to channel bed
              Right             on the right side when looking downstream

  WALL        Wall              top of a retaining wall, also used outside
                                TOBL and TOBR when the stream banks are
                                vertical walls or rock cuts

  WALLBOT     Wall Bottom       bottom of a retaining wall, also used
                                outside TOBL and TOBR when the stream banks
                                are vertical walls or rock cuts

  WEIR        Weir              top of dam spillways and outlet structures.
                                Multiple weir codes may be used to collect
                                data for gates, flashboards, and other
                                operable structures. The explanation of the
                                multiple shots must be shown in the
                                structure sketch.

  WW          Wing Wall         top face of each end of a wing wall or
                                headwall on a structure to define height and
                                length

  WWBOT       Wing Wall Bottom  base of each end of a wing wall or head wall
                                on a structure to define height and length
  --------------------------------------------------------------------------

¹ The four bridge corner shots need to be taken outside of any rail to
accurately measure hydraulic length.

[]{#__RefHeading___Toc209951117 .anchor}Figure M-1. Typical
Cross-section Photograph: Indian Creek IND-6600 (Displays Survey Code
Locations)

![](media/image2.wmf){width="6.021527777777778in"
height="4.532638888888889in"}

[]{#__RefHeading___Toc209951118 .anchor}Figure M-2. Typical
Cross-section Sketch: Indian Creek IND-6600

![](media/image3.jpeg){width="5.840972222222222in"
height="7.717361111111111in"}

[]{#__RefHeading___Toc209951119 .anchor}Figure M-3. Typical Bridge
Photograph: White Creek WHI-1800 (Displays Survey Code Locations)

![](media/image4.wmf){width="6.040277777777778in"
height="4.560416666666667in"}

[]{#__RefHeading___Toc209951120 .anchor}Figure M-4. Typical Bridge
Sketch: White Creek WHI-1800

![](media/image5.jpeg){width="5.914583333333334in"
height="7.929166666666666in"}

[]{#__RefHeading___Toc209951121 .anchor}Figure M-5. Typical Culvert
Photograph: Sanderson Creek SAN-0880 (Displays Survey Code Locations)

![](media/image6.wmf){width="6.095833333333333in"
height="4.719444444444444in"}

[]{#__RefHeading___Toc209951122 .anchor}**Figure M-6. Typical Culvert
Sketch: Sanderson Creek SAN-0880**

![](media/image7.wmf){width="5.977777777777778in"
height="7.920833333333333in"}

[]{#__RefHeading___Toc209951123 .anchor}Figure M-7. Typical Dam Data
(Displays Survey Code Locations)

![](media/image8.wmf){width="6.052777777777778in"
height="8.121527777777779in"}

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner assigned to "Perform Field Survey." General
correspondence is the written correspondence generated or received by
the Mapping Partner assigned to fulfill the requirements of performing
field survey. Correspondence includes any documentation generated during
this task such as letters; transmittals; memoranda; general status
reports and queries; SPRs; technical issues that need to be documented;
direction given by FEMA; and internal communications, routing slips, and
notes that were relevant to the performance of this task. Contractual
documents, such as a signed SOW or MAS, are not to be submitted as a
part of the DCS.

### Certification of Work

FEMA-funded survey data development must be certified using the
Certification of Compliance Form provided in figure M-8 in section M.10.
A PDF file of this form with the original signature, data, and seal
affixed to the form must be submitted digitally in the general directory
identified in section M.5.2.8. This form must be signed by a registered
or certified professional from the firm contracted to perform the work,
or by the responsible official of a government agency.

### Acceptable File Formats

The spatial data submitted for survey must be in a georeferenced digital
format. The following formats are acceptable for files:

-   PDF (for correspondence, certification, etc.) or JPG image files
    (for sketches, photos, etc.);

-   MDB/GDB -- Microsoft Access / ESRI personal geodatabase or file
    geodatabase (for X, Y, Z points);

-   XLS -- Microsoft Excel (for X, Y, Z points);

-   DBF -- Microsoft Access Database (for X, Y, Z points); and

-   ASCII format (comma delimited for X, Y, Z points).

### Metadata

A metadata file in XML format that complies with the FEMA/FGDC Metadata
Profiles (available on the MIP via "Tools and Links") must be included
with the submittal. The profiles follow the FGDC Content Standard for
metadata and define additional domains and business rules for some
elements that are mandatory for FEMA based on the specific submittal
type. For each spatial data source in the metadata file, the Mapping
Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to the
MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/) ) or by
mailing the files to FEMA on one or more of the following electronic
media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all digital media submitted must be labeled
with at least the following information:

-   Mapping Partner name;

-   Community name and State for which the FIS was prepared;

-   Survey Data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[*sequential number*\] of \[*number of disks*\]. The media
    must be numbered sequentially, starting at Disk 1. \[Number of
    disks\] represents the total number of disks in the submission.

### Transfer Methodology 

Survey Data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care".

### Directory Structure and Folder Naming Conventions

-   The files presented in section M.5.2 Requirements must be submitted
    to the MIP or mailed to FEMA within the following directory
    structure. The following folders can be created either on a local
    work space (i.e., a personal computer) or within the work space for
    the community on the MIP. If the following folders are generated
    locally, these newly created folders and their contents must be
    uploaded to the MIP.

-   \\General

```{=html}
<!-- -->
```
-   XML-format metadata file

-   Certification

-   Project narrative

    -   \\Correspondence

-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and notes.

```{=html}
<!-- -->
```
-   \\Survey\\Photos

    -   All digital photographs

        -   \\Survey\\Sketches

    -   All digital sketches

        -   \\Survey\\Data

    -   All survey files

-   \\Survey\\As-built

    -   As-built data

# Hydrology Submittal Standards

## Overview 

This section describes the hydrologic data that must be submitted to
FEMA for FISs with respect to rivers, lakes, closed basins and ponds.
All data must be submitted in digital format. The Mapping Partner(s)
contracted to "Develop Hydrologic Data" is required to submit the data
described in this section.

Appendix C of the Guidelines describes three broad categories of
hydrologic procedures used in the NFIP:

-   Flood-frequency analyses for gaged streams using Bulletin 17B,
    "Guidelines For Determining Flood Flow Frequency" (Interagency
    Advisory Committee on Water Data, 1982);

-   Regional regression equations for ungaged streams, generally those
    developed by the USGS (<http://water.usgs.gov/software/nff.html>);
    and

-   Rainfall runoff models.

Within the category of rainfall runoff models, the HEC-HMS model (or its
predecessor HEC-1) developed by the USACE Hydrologic Engineering Center
(HEC) is used most frequently in the NFIP. In addition to the USACE
models, FEMA accepts hydrologic results from over a dozen other rainfall
runoff models (see <http://www.fema.gov/plan/prevent/fhm/en_hydro.shtm>
for a list of accepted models) and it is likely that new models will be
added in the future.

The submitting Mapping Partner must retain copies of all project-related
data for a period of 3 years. The submitting Mapping Partner will need
these data for responding to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files 

There are three levels of studies that are generally performed for flood
hazard identification: detailed, limited detailed, and approximate
studies. These study types are defined in Appendix C of these
Guidelines. For limited detailed and approximate studies, the flood
discharges are typically estimated using data from stream gages or
regional regression equations. The following data requirements are
predicated on this assumption. However, this does not preclude using an
existing rainfall-runoff model to estimate the flood discharges for
limited detailed and/or approximate studies.

The following data files are required for detailed, limited detailed,
and approximate studies:

[Detailed Studies]{.underline}

-   A geospatial file (S_Nodes described in section M.12) showing the
    locations of computed discharges for the 10-, 2-, 1-, and
    0.2-percent-annual-chance floods with their associated drainage area
    and the flood discharges used in the hydrologic analysis that can be
    converted to a FIS Discharge Summary Table;

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12) that describes the spatial extent of the study
    areas (there will be one S_Submittal_Info layer but possibly
    multiple polygons describing the areal extent of detailed, limited
    detailed and approximate studies for a given Mapping Partner);

-   Input and output files for the hydrologic model(s) used in the
    study;

-   A hydrology report that documents the methodology, assumptions, and
    data used in hydrologic analyses;

-   A draft text file that provides the required information for
    inclusion in Section 3.1 Hydrologic Analyses of the FIS report;

-   A geospatial file (S_Subbasins described in section M.12) of
    watershed or subwatershed areas contributing runoff to the discharge
    points in the S_Nodes file;

-   Files of backup data and analyses that are not described or included
    in the hydrology report. Some examples of backup data that could be
    included are as follows: computations for time of concentration,
    such as the National Resources Conservation Service (NRCS) travel
    time computations for sheet flow, shallow concentrated flow, and
    channel flow (could be excel spreadsheets or pdfs of worksheets in
    TR-55); runoff curve number computations that document the percent
    of the watershed with various land uses and NRCS hydrologic soil
    types (soil maps are not required); ancillary data for estimating
    infiltration parameters for the Green-Ampt equation; derivations of
    unit hydrographs or S-graphs or estimation of synthetic unit
    hydrographs like the Snyder's or NRCS unit hydrographs; hourly
    (unit) rainfall and discharge data used to calibrate the
    rainfall-runoff model; input and output files for frequency analyses
    of rainfall data; geospatial files and supporting data for the
    computation of watershed and climatic characteristics for regional
    regression equations such as drainage area, channel slope, soils
    data (e.g., percent D soils), impervious area, and mean annual
    precipitation. These files support and complement the input files
    for the hydrologic model; and

-   A project narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

    [Limited Detailed Studies]{.underline}

-   A geospatial file (S_Nodes described in section M.12) showing the
    locations of computed discharges for the 1-percent-annual-chance
    flood with their associated drainage area and the flood discharges
    used in the hydrologic analysis that can be converted to an FIS
    Discharge Summary Table;

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12) that describes the spatial extent of the study
    areas (there will be one S_Submittal_Info layer but possibly
    multiple polygons describing the areal extent of detailed, limited
    detailed and approximate studies for a given Mapping Partner);

-   A geospatial file file (S_Subbasins described in section M.12) of
    watershed or subwatershed areas contributing runoff to the discharge
    points in the S_Nodes file;

-   Input and output files for the hydrologic model(s) used in the
    study;

-   A hydrology report that documents the methodology, assumptions, and
    data used in hydrologic analyses;

-   A draft text file that provides the required information for
    inclusion in Section 3.1 Hydrologic Analyses in the FIS report;

-   Files of backup data and analyses that are not described or included
    in the hydrology report. Some examples of backup data that could be
    included are as follows: GIS files and supporting data for the
    computation of watershed and climatic characteristics for regional
    regression equations such as drainage area, channel slope, soils
    data (e.g., percent D soils), impervious area, rainfall intensity
    and mean annual precipitation; input and output files from the USGS
    NFF or NSS computer programs for implementing the USGS regression
    equations; and any computations for times of concentration, runoff
    curve numbers, infiltration parameters, or unit hydrographs as
    described under detailed studies (if an existing rainfall-runoff
    model was used); and

-   A project narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

    [Approximate Studies]{.underline}

-   A geospatial file (S_Nodes described in section M.12) showing the
    locations of computed discharges for the 1-percent-annual-chance
    flood with their associated drainage areas and the flood discharges
    used in the hydrologic analysis, if available;

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12) that describes the spatial extent of the study
    areas (there will be one S_Submittal_Info layer but possibly
    multiple polygons describing the areal extent of detailed, limited
    detailed and approximate studies for a given Mapping Partner);

-   A geospatial file (S_Subbasins described in section M.12) of
    watershed or subwatershed areas contributing runoff to the discharge
    points identified in the S_Nodes file, if available;

-   A project description outlining how the 1-percent-annual-chance
    flood discharges were determined;

-   A draft text file that provides the required information for
    inclusion in Section 3.1 Hydrologic Analyses in the FIS report;

-   Any files of backup data and supporting analyses that were not
    described or included in the hydrology report. These could include
    geospatial files and supporting data for the computation of
    watershed characteristics for regional regression equations such as
    drainage area, channel slope, soils data (e.g., percent D soils),
    impervious area, rainfall intensity and mean annual precipitation;
    and input and output files from the USGS NFF or NSS computer
    programs for implementing the USGS regression equations; and

-   A project narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner assigned to "Develop Hydrologic Data." General
correspondence is the written correspondence generated or received by
the Mapping Partner assigned to fulfill the requirements of developing
hydrologic data. Correspondence includes any documentation generated
during this task such as letters; transmittals; memoranda; general
status reports and queries; SPRs; technical issues that need to be
documented; direction given by FEMA; and internal communications,
routing slips, and notes that were relevant to the performance of this
task. A narrative should be prepared that describes the SOW, direction
from FEMA, assumptions and issues, and any information that may be
useful for the Mapping Partner performing the hydraulic analyses.
Contractual documents, such as a signed SOW or MAS, are not to be
submitted as part of this appendix.

### Certification of Work

FEMA-funded hydrologic data development must be certified using the form
provided in figure M‑8. A PDF of the form, which has the original
signature, data, and seal affixed to the form, must be submitted
digitally. This form must be signed by a registered or certified
professional from the firm contracted to perform the work, or by the
responsible official of a government agency.

### Acceptable File Formats

Any supporting documentation and data can be submitted in native format.
The following formats are accepted for files:

-   PDF and Word file for hydrology report, FIS text and project
    narrative in Word format and other supporting information;

-   Shapefiles for all hydrology spatial files;

-   Geography Markup Language (GML) for all hydrology spatial files;

-   Personal geodatabase for all hydrology spatial files; and

-   Native format for input and output files for hydrologic models.

### Metadata 

A metadata file that complies with the FEMA/FGDC metadata (available on
the MIP via "Tools and Links") profiles in XML-format must be included
with the submittal. The profiles follow the FGDC content standard for
metadata and define additional domains and business rules for those
elements that are mandatory for FEMA, based on the specific submittal
type. For each spatial data source in the metadata file, the Mapping
Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to MIP
([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)) or on one
of the following electronic media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all digital media submitted must be labeled
with the following information:

-   Mapping Partner name;

-   Community name and State for which the FIS was prepared;

-   Hydrologic Data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[sequential number\] of \[number of disks\]. Disk
    \[*sequential number*\] of \[*number of disks*\]. The media must be
    numbered sequentially, starting at Disk 1. \[Number of disks\]
    represents the total number of disks in the submission.

### Transfer Methodology 

Hydrology Data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."

### Directory Structure and Folder Naming Conventions

The files in section M.6.2 Requirements must be submitted within the
following directory structure. The following folders can be created
either on a local work space (i.e., a personal computer) or within the
work space for the community on the MIP. If the following folders are
generated locally, these newly created folders and their contents must
be uploaded to the MIP.

The Mapping Partner is required to submit the input and output files for
any study using detailed hydrologic models. If the data that were used
to estimate the hydrologic parameters are available, they must be
documented in the hydrology report and submitted in the database files.

Models must be organized by stream, with all model files in the
*Simulations* folder and supporting spatial files in the *Spatial Files*
folder. Database files are stored in a *Hydrology Data* folder. Data
must be located in the appropriate directory, as follows:

-   \\General

```{=html}
<!-- -->
```
-   XML_format metadata file

-   Hydrology report in PDF and Word format

-   Certification

-   Draft FIS Section 3.1

-   Project narrative

    -   \\Correspondence

-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and notes.

    -   \\Hydrology Data

-   Database file(s) such as data and analyses for stream and rainfall
    gages and computations for regional regression equations in native
    format such as USGS PeakFQ, NFF or NSS computer programs

    -   \\Hydrology Models\\"Stream Name"\\Simulations

-   Model input and output files

    -   \\Hydrology Models\\"Stream Name"\\Spatial Files

-   Spatial files

# Hydraulics Submittal Standards

## Overview 

This section describes the hydraulic data that must be submitted to FEMA
for FISs with respect to for rivers, lakes, closed basins and ponds. All
data must be submitted in digital format. The Mapping Partner(s)
contracted to "Develop Hydraulic Data" is required to submit the data
described in this section.

Hydraulic methods include normal depth computations and other simplified
methods, as well as a variety of steady and unsteady hydraulic models
representing one-dimensional (1-D) or two-dimensional (2-D) flow
conditions. The 1-D models utilize cross-sectional data while the 2-D
models utilize a grid of ground-elevation points. Information on the
procedures used to develop hydraulic models is provided in Appendix C of
these Guidelines. FEMA-accepted hydraulic models can be found at
<http://www.fema.gov/plan/prevent/fhm/en_hydro.shtm>.

The submitting Mapping Partner must retain copies of all Project-related
data for a period of 3 years. The submitting Partner will need these
data in order to respond to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files 

There are three levels of studies that are generally performed for flood
hazard identification: detailed, limited detailed, and approximate
studies. These study types are defined in Appendix C of these
Guidelines. For detailed studies, it is assumed that a 1-D or 2-D
hydraulic (steady or unsteady) model is used. For limited detailed
studies, it is assumed that a hydraulic steady-state model, such as
HEC-RAS, is used to estimate the BFE. For approximate studies, it is
assumed that a hydraulic model such as HEC-RAS is not used. However, if
a hydraulic model was used for approximate studies, it should be
submitted. For approximate studies, it is assumed that normal depth
computations or some comparable methodology is used and these files
should be submitted as described later. The following data requirements
are predicated on these assumptions, but are flexible enough to
accommodate whatever data are developed. The following data files are
required for detailed, limited detailed, and approximate studies:

[Detailed Studies]{.underline}

-   Geospatial file showing the flow path used for modeling
    (S_Profil_Basln spatial file described in section M.12) or a
    node-link GIS file (structure of the GIS file is based on the
    submitting Mapping Partner's discretion) for storm sewer or pond
    routing;

-   Geospatial file that shows the locations of cross sections used for
    the computation of water-surface profiles for simplified hydraulic
    methods or 1-D models (S_XS spatial file described in section M.12);

-   Geospatial file that shows the whole-foot water surface elevations
    for the 1-percent-annual-chance flood (S_BFE described in section
    M.12);

-   Geospatial files that show the regulatory floodway,
    1-percent-annual-chance floodplain boundaries, and
    0.2-percent-annual-chance floodplain boundaries (S_Fld_Haz_Ar
    spatial file described in section M.12);

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in Section M.12) that describes the spatial extent of the study
    areas (there will be one S_Submittal_Info layer but possibly
    multiple polygons describing the aerial extent of detailed, limited
    detailed, and approximate studies for a given Mapping Partner);

-   Input and output files for the hydraulic model used for the studied
    reaches that include data for the 10-, 2-, 1-,
    0.2-percent-annual-chance flood profiles if within the scope of the
    detailed study (if applicable, 1-percent-annual-chance profiles with
    and without levees) and the floodway analysis;

-   A hydraulics report that describes the hydraulic analyses and
    assumptions;

-   A draft text file that provides the required information for
    inclusion in Section 3.2 Hydraulic Analyses of the FIS report;

-   A file containing profiles for the 10-, 2-, 1-, and
    0.2-percent-annual-chance floods and FDTs (if within the scope of
    the detailed study) for inclusion in the FIS report;

-   Additional geospatial and database tables, if utilized (i.e.,
    overbank distances used in certain models such as HEC-RAS; hydraulic
    computations used as input to the hydraulic model such as
    stage-discharge relations at culverts for 2-D models; calibration
    information, such as high-water marks; maps of historical flooding;
    spatial files of n-value polygons used in model calibration). The
    structure of these tables is at the discretion of the submitting
    Mapping Partner; and

-   A project narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

    [Limited Detailed Studies]{.underline}

-   A geospatial file showing the flow path used for modeling
    (S_Profil_Basln spatial file described in section M.12);

-   A geospatial file that shows the cross sections used for the
    computation of water-surface profiles for simplified hydraulic
    methods or 1-D models (S_XS spatial file described in section M.12);

-   Geospatial file that shows the whole-foot water surface elevations
    for the 1-percent-annual-chance flood, if available (S_BFE described
    in section M.12);

-   A geospatial file that shows the 1-percent-annual-chance floodplain
    boundaries (S_Fld_Haz_Ar spatial file described in section M.12);

-   Input and output files for the hydraulic model used in the analysis
    that include data for the 1-percent-annual-chance flood profile;

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12) that describes the spatial extent of the study
    areas (there will be one S-Submittal_Info layer but possibly
    multiple polygons describing the aerial extent of detailed, limited
    detailed, and approximate studies for a given Mapping Partner);

-   A hydraulics report that describes the hydraulic analyses and
    assumptions;

-   A draft text file that provides the required information for
    inclusion in Section 3.2 Hydraulic Analyses of the FIS report;

-   A file containing profiles for the 1-percent-annual-chance flood;

-   A file containing Limited Detailed Flood Hazard Data table (as
    described in Appendix C), if applicable;

-   All backup data used in the analysis, such as overbank distances
    used in certain models such as HEC-RAS; any hydraulic computations
    used as input to the hydraulic model; maps of historical flooding;
    spatial files of n-value polygons; and

-   A project narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

[Approximate Studies]{.underline}

-   A geospatial file showing the flow path used for modeling
    (S_Profil_Basln spatial file described in section M.12);

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12) that describes the spatial extent of the study
    areas (there will be one S-Submittal_Info layer but possibly
    multiple polygons describing the aerial extent of detailed, limited
    detailed, and approximate studies for a given Mapping Partner);

-   A geospatial file that shows the 1-percent-annual-chance floodplain
    boundaries (S_Fld_Haz_Ar spatial file described in section M.12);

-   A file containing a description of how the floodplain boundaries
    were determined;

-   A draft text file that provides the required information for
    inclusion in Section 3.2 Hydraulic Analyses of the FIS report;

-   All backup data used in the analysis, such as the cross-sectional
    data, and the computations for the 1-percent-annual-chance
    elevations at the cross sections used in the analysis; maps of
    historical flooding; and

-   A project narrative describing the SOW, direction from FEMA, issues,
    information for the next Mapping Partner, etc.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner assigned to "Develop Hydraulic Data." General
correspondence is the written correspondence generated or received by
the Mapping Partner assigned to fulfill the requirements of developing
hydraulic data. Correspondence includes any documentation generated
during this task such as letters; transmittals; memoranda; general
status reports and queries; SPRs; technical issues that need to be
documented; direction given by FEMA; and internal communications,
routing slips, and notes that were relevant to the performance of this
task. A narrative should be prepared that describes the SOW, direction
from FEMA, assumptions and issues, and any information that may be
useful for the Mapping Partner preparing the preliminary DFIRM.
Contractual documents, such as a signed SOW or MAS, are not to be
submitted.

### Certification of Work

FEMA-funded hydraulic data development must be certified using the form
provided in figure M-8. A PDF of the form must be submitted digitally
and must have the original signature, data, and seal affixed to the
form. This form must be signed by a Registered Professional Engineer or
licensed land surveyor from the firm contracted to perform the work, or
by the appropriate government agency official. A digital version of this
form is available at www.fema.gov.

### Acceptable File Formats

Any supporting documentation can be submitted in native format. The
following formats are acceptable for files:

-   PDF and Word file for the hydraulics report, project narrative in
    Word format and other supporting information;

-   Shapefiles for all hydraulics spatial files;

-   GML for all hydraulics spatial files;

-   Personal geodatabase for all hydraulics spatial files;

-   Native format of input and output files for hydraulic models in
    native formats; and

-   DXF for profiles.

### Metadata

A metadata file that complies with the FEMA/FGDC Metadata Profiles
(available on the MIP via "Tools and Links") in XML format must be
included with the submittal. The profiles follow the FGDC Content
Standard for metadata and define the additional domains and business
rules for those elements mandatory for FEMA based on the specific
submittal type. For each spatial data source in the metadata file, the
Mapping Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to the
MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)) or
through one of the following electronic media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all submitted digital media must be labeled
with the following information:

-   Mapping Partner name;

-   Community name and State for which the FIS was prepared;

-   Hydraulic data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[sequential number\] of \[number of disks\]. Disk
    \[*sequential number*\] of \[*number of disks*\]. The media must be
    numbered sequentially, starting at Disk 1. \[Number of disks\]
    represents the total number of disks in the submission.

### Transfer Methodology 

Hydraulic Data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."

### Directory Structure and Folder Naming Conventions

The files under section M.7.2 Requirements must be submitted in the
following directory structure created by the contractor in their
workspace prior to upload. The following folders can be created either
on a local work space (i.e., a personal computer) or within the work
space for the community on the MIP. If the following folders are
generated locally, these newly created folders and their contents must
be uploaded to the MIP.

Models are organized by stream, with all model files in the
*Simulations* folder and all support spatial files in the *Spatial
Files* folder. Any additional data not described by these specifications
and used to assist in the modeling of this study must be submitted in
the *Hydraulic Databases* folder. Data must be located in the
appropriate directories as follows:

-   \\General

```{=html}
<!-- -->
```
-   Metadata file in XML format

-   Hydraulics report in PDF and Word format

-   Certification

-   Draft FIS Section 3.2

-   Project narrative

    -   \\Correspondence

-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and notes

    -   \\Hydraulic Models\\"Stream Name"\\Simulations

-   Model input and output files by stream for the 10-, 2-, 1-,
    0.2-percent-annual-chance floods and floodway analysis if within the
    scope of the detailed study

    -   \\Hydraulic Models\\"Stream Name"\\Spatial Files

-   Spatial files by stream

    -   \\Hydraulic Models\\"Stream Name"\\Profiles

-   Profiles in DXF format

    -   \\Hydraulic Models\\"Stream Name"\\FWDT

-   Floodway data tables

-   Limited Detailed Flood Hazard Risk table

    -   \\Hydraulic Models\\"Stream Name"\\Hydraulic Databases

-   Database file(s) such as high water mark data for model calibration

# Alluvial Fan Submittal Standards

## Overview 

This section describes the type and format of data needed to map the
1-percent-annual-chance flood associated with alluvial fans. All data
must be submitted in digital format. The Mapping Partner(s) contracted
to "Perform Alluvial Fan Analysis" is required to submit the data in
this section.

Appendix G of these Guidelines provides guidance for the identification
and mapping of flood hazards that occur on alluvial fans. As described
in Appendix G, the approach for the identification and mapping of
alluvial fan flooding can be divided into three stages:

> Stage 1 -- Recognizing and characterizing alluvial fan landforms;
>
> Stage 2 -- Defining the nature of the alluvial fan environment and
> identifying active and inactive areas of the fan; and
>
> Stage 3 -- Defining and characterizing the 1-percent-annual-chance
> flood within the defined areas.

Under Stage 3, there are several acceptable methods for defining the
base flood depending on the characteristics of the alluvial fan. These
methods are as follows, and are also described in Appendix G of these
Guidelines:

-   FAN computer program (FEMA, 1990
    http://www.fema.gov/plan/prevent/fhm/en_stat.shtm): used for highly
    active, conical fans -- definition of Zone AO areas with depths and
    velocities;

-   Sheetflow analysis: used for shallow flooding across uniformly
    sloping surfaces -- definition of Zone AO with depths;

-   Hydraulic Analytical Methods: used for entrenched channel networks
    or constructed channels (1-D model) or uncertain flow paths (2-D
    model) -- definition of Zone A, Zone AE, and/or Zone X;

-   Geomorphic Data, Post-Flood Hazard Verification, and Historical
    Information: used for alluvial fans with little or no urbanization
    -- definition of Zone X and/or Zone A areas;

-   Composite Methods: used for fans with unique physical features in
    some locations -- some combination of the above methods.

The submitting Mapping Partner must retain copies of all Project-related
data for a period of 3 years. The submitting Partner will need these
data for responding to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files

The following files and data must be submitted for alluvial fan
analysis:

-   Under Stage 1, materials such as geologic maps, field reconnaissance
    reports, topographic maps, and aerial photos used to identify the
    landform as an alluvial fan must be submitted;

-   Under Stage 2, historic records of flooding, photographs,
    time-sequence aerial photography, and geomorphic information must be
    submitted to illustrate either active or inactive alluvial fan
    flooding;

-   Under Stage 3, input and output files for the FAN program
    (FEMA, 1990) or 1-D or 2-D hydraulic programs must be submitted,
    including the following datasets:

```{=html}
<!-- -->
```
-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12);

-   A geospatial file showing the flow path used for floodplain mapping
    (S_Profil_Basln described in section M.12) if hydraulic models were
    utilized;

-   A geospatial file showing the locations of cross sections (if
    applicable) used for the computation of water-surface profiles for
    1-D models (S_XS spatial file described in section M.12);

-   Geospatial files showing the 1-percent-annual-chance flood
    boundaries with depths and velocities and BFEs for 1-D and 2-D
    models, if applicable (S_Alluvial described in section M.12);

-   A file containing profiles for the 1-percent-annual-chance flood.
    Profiles created as DXF files and edited for content;

-   Input and output files for the 1-percent-annual-chance flood for the
    hydraulic model used in the analysis; and

-   All geospatial datasets used for parameter calculation, if
    applicable, such as a spatial file of n-value polygons

    -   A draft text file that provides the required information for
        inclusion in Section 3.2 Hydraulic Analyses of the FIS report

    -   A technical report that describes the processes for identifying
        the alluvial fan, the areas of active and inactive alluvial fan
        flooding, and the procedures for determining the aerial extent
        and/or elevation of the base flood; and

    -   A project narrative describing the SOW, direction from FEMA,
        issues, information for the next Mapping Partner, etc.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner assigned to "Develop Alluvial Fan Data." General
correspondence is the written correspondence generated or received by
the Mapping Partner assigned to fulfill the requirements of performing
alluvial analysis. Correspondence includes any documentation generated
during this task such as letters; transmittals; memoranda; general
status reports and queries; SPRs; technical issues that need to be
documented; direction given by FEMA; and internal communications,
routing slips, and notes that were relevant to the performance of this
task. A narrative should be prepared that describes the scope of the
work, direction from FEMA, assumptions and issues, and any information
that may be useful for the Mapping Partner performing the mapping
analyses. Contractual documents, such as a signed SOW or MAS, are not to
be submitted as a part of the DCS.

### Certification of Work

FEMA-funded alluvial fan data development must be certified using the
form provided in figure M‑8. A PDF of the form must be submitted
digitally with the original signature, data, and seal affixed to the
form. This form must be signed by a Registered Professional Engineer or
licensed land surveyor from the firm contracted to perform the work or
by the appropriate government agency official. A digital version of this
form is available at www.fema.gov.

### Accepted File Formats

Any supporting documentation and data can be submitted in model or
native format. The following formats are acceptable for files:

-   PDF and Word files for the technical report, project narrative in
    Word format, and other supporting information;

-   Shapefiles for all alluvial fan spatial files;

-   GML for all alluvial fan spatial files;

-   Personal geodatabase for all alluvial fan spatial files;

-   Native formats for hydraulic model input and output files; and

-   DXF for profiles.

### Metadata 

A metadata file in XML format that complies with the FEMA/FGDC Metadata
Profiles (available on the MIP via "Tools and Links") must be included
with the submittal. The profiles follow the FGDC Content Standard for
metadata and define additional domains and business rules for some
elements that are mandatory for FEMA based on the specific submittal
type. For each spatial data source in the metadata file, the Mapping
Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files on one of the following electronic
media or via the internet by uploading to the MIP
([http://www.hazards.fema.gov](http://www.hazards.fema.gov/) ):

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all submitted digital media must be labeled
with the following information:

-   Mapping Partner's name;

-   Community name and State for which the FIS was prepared;

-   Alluvial Fan Data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[*sequential number*\] of \[*number of disks*\]. The media
    must be numbered sequentially, starting at Disk 1. \[Number of
    disks\] represents the total number of disks in the submission.

### Transfer Methodology 

Alluvial fan data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."

### Directory Structure and Folder Naming Conventions

The files in section M.8.2 Requirements must be submitted within the
following directory structure. The following folders can be created
either on a local work space (i.e., a personal computer) or within the
work space for the community on the MIP. If the following folders are
generated locally, these newly created folders and their contents must
be uploaded to the MIP.

Models are usually organized by stream, with all model files in the
*Simulations* folder and supporting spatial files in the *Spatial Files*
folder. Data must be located in the appropriate directories as follows:

-   \\General

```{=html}
<!-- -->
```
-   XML_format metadata file

-   Alluvial fan technical report in PDF and Word format

-   Draft FIS Section 3.2

-   Certification

-   Project narrative

    -   \\Correspondence

-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and notes

    -   \\Alluvial Fan\\Hydraulic Models\\"Stream Name"\\Simulations

-   Model input and output files in native format

    -   \\Alluvial Fan \\Hydraulic Models\\"Stream Name"\\Profiles

-   Profiles in DXF format

    -   \\Alluvial Fan \\Hydraulic Models\\"Stream Name"\\Spatial Files

-   Spatial files

    -   \\Alluvial Fan \\Hydraulic Databases

-   Database file(s)

    -   \\FAN program files\\"Stream Name"\\Simulations

-   Model input and output files in native format

# Coastal Submittal Standards

## Overview 

This section describes the type and format of data that must be
submitted to FEMA for coastal FISs. All data must be submitted in
digital format. The Mapping Partner(s) contracted to "Perform Coastal
Analysis" is required to submit the data in this section. Details on
FEMA guidance for coastal flood hazard analyses and mapping are provided
in Appendix D of these Guidelines, and additional guidance and Procedure
Memorandums published after Appendix D.

The submitting Mapping Partner must retain copies of all Project-related
data for a period of 3 years. The submitting Partner will need these
data for responding to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files 

The following data files must be submitted for coastal studies:

-   Storm climatology and meteorological event selection

```{=html}
<!-- -->
```
-   A text or spatially-compatible file containing the regional
    historical storm database

-   A text or spatially-compatible file containing storm events selected
    and their storm parameters

-   A report describing the technical approach for storm event selection

    -   Stillwater Elevations (SWELs)

-   Grid files of storm windfield and pressure field data for selected
    events (model input files -- if water levels are simulated/hindcast)

-   A report describing hydrodynamic models calibration and validation
    (if water levels are simulated/hindcast. If 2-D wave models were
    used for setup calculations, these should be included here as well.)

-   Model input files, in their native format, of calibrated
    hydrodynamic models (grid and parameter specifications -- if water
    levels are simulated/hindcast.) If setup is being calculated by 2-D
    wave models, wave model input files would also be included.

-   A text file, spreadsheet, or spatially-compatible file containing
    water level maxima at surge station locations for each storm event
    (if water levels are simulated/hindcast.) If statistics on
    stillwater and 2-D wave results are calculated separately, both sets
    of maxima for each storm event should be included.

-   A text file, spreadsheet, or spatially - compatible file containing
    water level maxima at available tide gage locations for each storm
    event (if historical data used for statistical analyses or model
    calibration)

-   A report describing the technical approach for flood frequency
    analyses

-   A report describing the approach adopted for sheltered water areas
    (if applicable)

-   A text file, spreadsheet, or spatially - compatible file containing
    the 10-percent, 2-percent, 1-percent and 0.2-percent-annual-chance
    stillwater levels at the surge station locations

    -   Offshore wave characteristics

-   Grid files of wave model windfield data (model input files -- if
    waves are simulated/hindcast)

-   A report describing the wave model calibration and validation (if
    waves are simulated/hindcast)

-   Model input files, in their native format, of the calibrated wave
    model (grid and parameter specifications -- if waves are
    simulated/hindcast)

-   A text file, spreadsheet, or spatially - compatible file containing
    the controlling wave height and peak wave period at surge station
    locations for each storm event (if waves are simulated/hindcast)

-   A text file, spreadsheet, or spatially - compatible file containing
    water heights and wave periods at available wave stations/buoys (if
    historical wave data were used or if used for model calibration)

-   A report describing the technical approach for wave simulation
    and/or statistical analyses

-   A report describing the approach adopted for sheltered water areas

-   A text file, spreadsheet, or spatially - compatible file containing
    the 1-percent-annual-chance controlling wave heights and wave
    periods (by transect)

    -   Nearshore hydraulics

-   Model input and output files from WHAFIS or CHAMP (if applicable)

-   A text file, spreadsheet, or spatially - compatible file containing
    pre- and post- eroded transect profiles (if applicable)

-   A report describing the technical approach adopted for wave-height,
    wave setup, wave run-up and wave-overtopping calculations

-   Input and output files for any other models used in coastal
    hydraulic analyses

    -   Spatial Files

-   Floodplain Mapping submittal information (S_Submittal_Info described
    in Section M.12)

-   BFEs (S_BFE spatial file described in section M.12)

-   Flood hazard zone map boundary delineations (S_Fld_Haz_Ar spatial
    file described in section M.12)

-   Primary frontal dune delineations (S_PFD_Ln spatial file described
    in section M.12)

-   Transects (S_Cst_Tsct_Ln spatial file described in section M.12)

-   Coastal Water Levels (L_Cst_WaterLv spatial file described in
    section M.12)

-   Coastal Gage Data (S_Cst_Gage spatial file described in section
    M.12)

-   Shoreline (S_Shore_Ln spatial file described in section M.12)

-   Coastal Barrier Resource System (CBRS) and Other Protected Areas
    (OPAs) (S_CBRS spatial file described in section M.12)

-   Coastal Structures (L_Cst_Struc spatial file described in section
    M.12)

-   Limit of Moderate Wave Action (S_LiMWA spatial file described in
    section M.12)

    -   A draft text for inclusion in the FIS report that provides the
        required information for Section 3.1 Hydrologic Analyses and
        Section 3.3 Coastal Analysis

    -   A project narrative describing the SOW, direction from FEMA,
        issues, information for the next Mapping Partner, etc.

### 1-Percent-Annual-Chance Wave Envelope

A 1-percent-annual-chance wave envelope profile for each transect must
be submitted showing the wave heights, wave runup elevation, SWELs, zone
gutter locations, and where applicable, the location of primary frontal
dunes, pre-and post eroded ground profile, and the location of coastal
structures included in analyses. If the modeled transect numbers differ
than those shown on the work map, then a transect key, correlating the
modeled transects to the mapped transects, should also be submitted.
These files must be submitted in PDF or DXF format and located in the
*Simulations Folder* of this submittal.

### 0.2-Percent-Annual-Chance Wave Envelope

Calculating the 0.2-percent-annual-chance wave height is an optional
coastal study task. When included as part of the coastal studies,
profiles showing the 0.2-percent-annual-chance wave envelope and ground
elevations are added to the end of the FIS. All profiles must be
submitted using a file name convention of "County_TransectNumber\*\*\*,"
in a DXF or a spatially-compatible file format, to allow for graphic
format changes, and as a PDF file for the FIS narrative report. These
files must be located in the simulations folder of this submittal.

### Summary of Coastal Stillwater Elevations

A Coastal Stillwater Elevation Table, which is a direct product of the
storm surge modeling, must be provided in the FIS report narrative. This
table must be submitted in a Microsoft Word format named
"Stillwater_Summary.doc". These files must be located in the coastal
database directory of the submittal. The Coastal Stillwater Elevation
Table must include mean sea level (MSL), tidal fluctuations about the
MSL and the storm surge and wave setup. It excludes wave heights. SWELs
may be defined by statistical analyses of tide gage records or by
numerical simulation methods such as ADCIRC or MIKE21. The Coastal
Stillwater Elevation Table must also include the following elements:

-   The El Nino component of the total water level (required when
    coastal analysis is performed on the Pacific Coast);

-   The type of extreme value distribution used to compute the
    1-percent-annual-chance SWEL;

-   The type of surge model used in the coastal analysis (not required
    for data that pertains to the Northeastern or Pacific Coasts.
    Acceptable surge models include DYNLET, FEMA Surge (1988), FLOW2D
    (1975), MIKE 21 HD/NHD, New England Tide Profile, Northeaster Model
    (1978), ODISTIM (1975), TABS RMA V.4.3 (October 1996), or USACE
    Great Lakes Tide Profile (1998).

-   The sea level rise used in analysis, shown in millimeters per year
    (mm/yr). This is required when the tide gage data is from an older
    epoch, and must be converted to the present; or when future sea
    level rise has been included in the analysis with the approval or
    direction of FEMA, and sea level rise data are available for the
    coastal study reach;

-   The method used to compute the combined effect of surge and runoff;
    acceptable methods include Independent methods, Correlation, or
    other methods; and

-   The method used to compute the combined effect of surge and tide;
    acceptable methods include linear combination, high/low, EST
    approach, 1-D Monte Carlo approach, or 2-D surge modeling.

Additionally, the following Coastal Stillwater information must be
included in the submittal:

-   A spreadsheet containing the 10-percent, 2-percent, 1-percent, and
    0.2-percent SWELs and locations (in latitude and longitude). This
    file should include the total levels when surge and setup are added;

-   The unit of measure for the Coastal SWEL (normally in feet);

-   The vertical datum from which the elevations were measured (normally
    North American Vertical Datum of 1988 (NAVD88));

-   Whether wind setup was used in the coastal analysis; and

-   A spreadsheet of the storm surge component of total water level, if
    available. If surge and setup are calculated independently, then the
    storm surge added to values associated with wind setup will equal
    the SWEL at a specific location. If wind setup is not calculated,
    then the storm surge will be the same as the SWELs, and this storm
    surge spreadsheet is not required.

.

### Surge Station Location Map

A Surge Station Location Map, a direct product of storm-surge modeling
that shows the locations of the modeled 1-percent-annual-chance SWELs,
should be provided in the FIS report narrative. The model output
locations should be summarized appropriately for clarity on the map. The
surge station locations may or may not coincide with the transect
locations. This map must be submitted in a JPEG or PDF file format,
named "Surge_Stations.\*\*\*." These files must be located in the
coastal database directory of the submittal. The specifications for the
Surge Station Location Map are provided in the sample report in section
J.6 of Appendix J of these Guidelines.

### Transect Location Map

A Transect Location Map illustrates the location of transects used in
coastal analyses and should be provided in the FIS report narrative.
This map must be submitted in JPEG or PDF file format, named
"Transect_Location.\*\*\*." Transect location maps are only needed in
the FIS if transects are not shown on the FIRM. If a Transect location
map is included in the FIS, only transects used for mapping should be
shown. These files must be located in the coastal database directory of
the submittal. The specifications for the Transect Location Map are
provided in the sample report in section J.6 of Appendix J of these
Guidelines.

### Transect Description Table

A Transect Description Table describes the physical location of each
transect shown in the Transect Location map, the associated
1-percent-annual-chance SWEL, and the maximum 1‑percent‑annual‑chance
wave crest elevation for each transect, and is to be provided in the FIS
report narrative. This table must be submitted in a Microsoft Word
format named "Transect_Description.doc." These files must be located in
the coastal database directory of this submittal. The specifications for
the Transect Description Table are provided in the sample report in
section J.6 of Appendix J of these Guidelines.

### Transect Data Table

A Transect Data Table describes the: flood source, transect identifier,
SWELs (10-, 2-, 1- and 0.2-percent annual chance), flood hazard zone,
and BFE range, for each transect, and is to be provided in the FIS
report narrative. This table should also indicate if a primary frontal
dune is mapped. This table must be submitted in a Microsoft Word
document named "Transect_Data.doc." These files must be located in the
coastal database directory of this submittal. The specifications for the
Transect Data Table are provided in the sample report in section J.6 of
Appendix J of these Guidelines.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner performing coastal analysis. General correspondence is
the written correspondence generated or received by the Mapping Partner
assigned to fulfill the requirements of performing coastal analysis.
Correspondence includes any documentation generated during this task
such as letters; transmittals; memoranda; general status reports and
queries; SPRs; technical issues that need to be documented; direction
given by FEMA; and internal communications, routing slips, and notes
that were relevant to the performance of this task. A narrative should
be prepared that describes the SOW, direction from FEMA, assumptions and
issues, and any information that may be useful for the Mapping Partner
performing the mapping analyses. Contractual documents, such as a signed
SOW or MAS, are not to be submitted as a part of the DCS.

### Certification of Work

Coastal work that was funded by FEMA must be certified using the form
provided in figure M-8. A PDF of the form must be submitted digitally
which has the original signature, data, and seal affixed to the form.
This form must be signed by a Registered Professional Engineer or
licensed land surveyor from the firm contracted to perform the work, or
by the appropriate government agency official. A digital version of this
form is available at www.fema.gov.

### Acceptable File Formats

Any spatial features must be stored in a spatially-compatible format.
Model input and output files and other data files used to support the
study can be provided in their native format.

-   PDFs for reports, correspondence, and certifications;

-   Shapefiles, GML or Personal Geodatabase for all coastal spatial
    files;

-   MXD or PDF for coastal map products;

-   Models in native formats; and

-   0.2-percent-annual-chance wave envelope profiles in PDF and DXF or
    spatially-compatible file.

### Metadata 

A metadata file that complies with the FEMA/FGDC metadata profiles
(available on the MIP via "Tools and Links") in XML-format must be
included with the submittal. The profiles follow the FGDC content
standard for metadata and define additional domains and business rules
for those elements mandatory for FEMA based on the specific submittal
type. For each spatial data source in the metadata file, the Mapping
Partner must assign a Source Citation Abbreviation.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to the
MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)) or on
one of the following electronic media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all digital media submitted must be labeled
with the following information:

-   Mapping partner name;

-   Community name and State for which the FIS was prepared;

-   Coastal data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[*sequential number*\] of \[*number of disks*\]. The media
    must be numbered sequentially, starting at Disk 1. \[Number of
    disks\] represents the total number of disks in the submission.

### Transfer Methodology 

Coastal Data artifacts can be uploaded to the MIP by following the
guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."

### Directory Structure and Folder Naming Conventions

The files in section M.9.2 Requirements must be submitted in the
following directory structure. The following folders can be created
either on a local work space (i.e., a personal computer) or within the
work space for the community on the MIP. If the following folders are
generated locally, these newly created folders and their contents must
be uploaded to the MIP.

In addition to the other requirements outlined in this section, the
Mapping Partner is required to submit the input and output files for
coastal computer models. If the data used to estimate the model
parameters are available, they must be submitted as well.

Models are organized with all model files in the *Simulations* folder
and support spatial files in the *Spatial Files* folder. Data must be
located in the appropriate directories, as follows:

-   \\General

```{=html}
<!-- -->
```
-   XML_format metadata file

-   Certification

-   Coastal analyses and mapping reports

-   Draft FIS Sections 3.1 and 3.3

    1.  Transect_Location Map

    2.  Transect_Description Table

    3.  Transect_Data Table

    4.  Surge_Stations Map

    5.  Stillwater_Summary Table

    6.  0.2-percent-annual-chance Wave Envelope (if applicable)

-   Project narrative

    -   \\Correspondence

-   Letters; transmittals; memoranda; general status reports and
    queries; SPRs; technical issues; direction by FEMA; and internal
    communications, routing slips, and note

    -   \\Coastal Models\\Coast Name\\Simulations

-   Model input and output files

-   Wave envelope files

    -   \\Coastal Models\\Coast Name\\Spatial Files

-   Spatial files

    -   \\Coastal Databases

-   Database file(s)

    -   \\Transects

-   Transects (If one-dimensional model was used)

# Floodplain Mapping Submittal Standards

## Overview 

This section describes the type and format of data that must be
submitted to FEMA for floodplain mapping performed by redelineation of
floodplains using updated topographic data and conversion of non-revised
effective FIRM information to digital format. All data must be submitted
in digital format. The Mapping Partner performing "Floodplain Mapping"
is required to submit the data in this section.

The submitting Mapping Partner must retain copies of all project-related
data for a period of 3 years. The submitting Mapping Partner will need
these data in order to respond to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of the preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files

The following files must be submitted for floodplain mapping:

-   A draft FIS report;

-   Certification of Work;

-   FBS self-certification documentation;

-   Redelineation files described in section M.10.2.3

-   Digital conversion files described in section M.10.2.4

### Draft FIS

The Mapping Partner performing "Floodplain Mapping" must produce the
draft FIS report by updating relevant sections of the effective FIS
report, including all profiles and tables converted to NAVD88, as well
as any other necessary items for the preparation of the preliminary FIS.
The submitting Mapping Partner must ensure the draft FIS report complies
with Appendix J of these Guidelines.

### Redelineation 

#### Riverine Redelineation

If the floodplain mapping involves the redelineation process for
riverine areas, then the following files must be submitted:

-   The following spatial files, where applicable:

    -   Floodplain Mapping submittal information (S_Submittal_Info
        described in Section M.12)

    -   Cross sections (S_XS described in section M.12)

    -   BFEs (S_BFE described in section M.12)

    -   Profile baseline (S_Profil_Basln described in section M.12)

    -   Floodplain mapping (S_Fld_Haz_Ar described in section M.12)

        -   Topographic data files as described in section M.4 (if not
            submitted under "Develop Topographic Data" described in
            section M.4)

        -   A project narrative describing the SOW, direction from FEMA,
            source and description of topographic data, issues, etc.

#### Coastal Redelineation

If the floodplain mapping involves the redelineation process for coastal
areas, then the following files must be submitted:

-   Spatial files, where applicable:

```{=html}
<!-- -->
```
-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12)

-   Shoreline (S_Shore_Ln described in section M.12)

-   Coastal transects (S_Cst_Tsct_Ln described in section M.12)

-   Floodplain mapping (S_Fld_Haz_Ar described in section M.12)

-   BFEs (S_BFE described in section M.12)

-   Limit of Moderate Wave Action (S_LIMWA described in section M.12)

-   Primary frontal dune delineations (S_PFD described in section M.12)

-   CBRS and OPAs (S_S_CBRS described in section M.12)

    -   Topographic data files as described in section M.4 (if not
        submitted under "Develop Topographic Data" described in section
        M.4)

    -   A project narrative describing the SOW, direction from FEMA,
        issues, etc.

### Digital Conversion

#### Riverine Digital Conversion

If the floodplain mapping involves conversion of non-revised effective
FIRM information to digital format for riverine areas, then the
following files must be submitted:

-   The following spatial files, where applicable:

    -   Floodplain Mapping submittal information (S_Submittal_Info
        described in section M.12)

    -   Cross sections (S_XS described in section M.12)

    -   BFEs (S_BFE described in section M.12)

    -   Profile baseline (S_Profil_Basln described in section M.12)

    -   Floodplain mapping (S_Fld_Haz_Ar described in section M.12)

        -   Base map data files as described in section M.3 (if not
            submitted under "Acquire Base Map" described in section M.3)

        -   A project narrative describing the SOW, direction from FEMA,
            issues, etc.

#### Coastal Digital Conversion

If the floodplain mapping involves conversion of non-revised effective
FIRM information to digital format for coastal areas, then the following
files must be submitted:

-   Spatial files, where applicable:

```{=html}
<!-- -->
```
-   Floodplain Mapping submittal information (S_Submittal_Info described
    in section M.12)

-   Shoreline (S_Shore_Ln described in section M.12)

-   Coastal transects (S_Cst_Tsct_Ln described in section M.12)

-   Floodplain mapping (S_Fld_Haz_Ar described in section M.12)

-   BFEs (S_BFE described in section M.12)

-   CBRS and OPAs (S_S_CBRS described in section M.12)

    -   Base map data files as described in section M.3 (if not
        submitted under "Acquire Base Map" described in section M.3)

    -   A project narrative describing the SOW, direction from FEMA,
        issues, etc.

### General Correspondence

A file that compiles general correspondence must be submitted by the
Mapping Partner performing floodplain mapping described in this section.
General correspondence is the written correspondence generated or
received by the Mapping Partner assigned to fulfill the requirements of
performing floodplain mapping. Correspondence includes any documentation
generated during this task such as letters; transmittals; memoranda;
general status reports and queries; SPRs; technical issues that need to
be documented; direction given by FEMA; and internal communications,
routing slips, and notes that were relevant to the performance of this
task. A narrative should be prepared that describes the SOW, direction
from FEMA, assumptions and issues, and any information that may be
useful for FEMA. Contractual documents, such as a signed SOW or MAS, are
not to be submitted as a part of the DCS.

### Certification of Work

Work funded by FEMA must be certified using the form provided in figure
M-8. A PDF of the form must be submitted digitally with the original
signature, data, and seal affixed to the form. In addition, an FBS
self-certification is also required for all projects completed. FBS
self-certification requirements are described in the following section.
These forms must be signed by a Registered Professional Engineer or
licensed land surveyor from the firm contracted to perform the work, or
by the appropriate government agency official. A digital version of
these forms is available at [www.fema.gov](http://www.fema.gov/).

### Floodplain Boundary Standard Self-Certification

The FBS self-certification documentation and data must be submitted
within 30 days after a mapping project is issued preliminary and also
within 30 days of the issuance of the Letter of Final Determination
(LFD) if there were changes to the SFHA boundaries during the
post-preliminary phase using the upload step in the MIP workflow for
each Flood Map Project funded in FY06 and later. The *Floodplain
Boundary Standard Audit Procedures --* located on FEMA's Web site *--*
outline the documentation needed for FBS compliance through
self-certification. The following data must be captured and submitted
for each Flood Mapping Project in the report format provided in
Attachment B of the *Floodplain Boundary Standard Audit Procedures*:

-   Self-Certification review type (GIS or WISE);

-   Description of materials used to perform the audit;

-   Mapping Partner performing the audit;

-   Self-Certification date;

-   Date submitted to Region;

-   Names of stream reaches audited;

-   Total stream length audited;

-   Number of floodplain boundary points audited;

-   Number of floodplain boundary points passed;

-   Number of floodplain boundary points failed;

-   Shapefile of points tested including exceptions;

-   Pass/Fail percentages for study FBS risk classes;

-   100k NHD Subbasin Pass/Fail shapefile if reporting results below
    study level pass; and

-   Stream name and length that passed audit.

### Acceptable File Formats

Any supporting documentation and data can be submitted in model or
native format. The following formats are accepted for files:

-   Shapefiles for all riverine and coastal spatial files;

-   Personal geodatabase for all riverine and coastal spatial files;

-   GML for all riverine and coastal spatial files;

-   PDF for correspondence and certifications;

-   Word or PDF for draft FIS report and Word, Excel, Access, and PDF
    for FWDT; and

-   DXF format for stream profiles (redelineation).

### Metadata 

A metadata file that complies with the FEMA/FGDC Metadata Profiles
(available on the MIP via "Tools and Links") in XML format must be
included with the submittal. The profiles follow the FGDC Content
Standard for metadata and define additional domains and business rules
for those elements mandatory for FEMA based on the specific submittal
type. For each spatial data source in the metadata file, the Mapping
Partner must assign a Source Citation Abbreviation.

### Transfer Media

-   Mapping Partners must submit files via the internet by uploading to
    the MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)
    ) or on one of the following electronic media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

When data is mailed to FEMA, all digital media submitted must be labeled
with the following information:

-   Mapping Partner name;

-   Community name and State for which the FIS was prepared;

-   Coastal data;

-   Date of submission (formatted mm/dd/yyyy); and

-   Disk \[*sequential number*\] of \[*number of disks*\]. The media
    must be numbered sequentially, starting at Disk 1. \[Number of
    disks\] represents the total number of disks in the submission.

[]{#__RefHeading___Toc209951124 .anchor}Figure M-8 Certification of
Compliance Form

  --------------------- ---------------------- ----------------------------------------------
  Project Name:                                

  Statement of Work                            
  No.:                                         

  Interagency Agreement                        
  No.:                                         

  CTP Agreement No.:                           

  Statement/Agreement                          
  Date:                                        

  Certification Date:                          

                        Tasks/Activities       
                        Covered by This        
                        Certification (Check   
                        All That Apply)        

                       Base Map               

                       Topographic Data       
                        Development            

                       Survey                 

                       Hydrologic Analysis    

                       Hydraulic Analysis     

                       Alluvial Fan Analysis  

                       Coastal Analysis       

                       Floodplain Mapping     

                        This is to certify     
                        that the work          
                        summarized above was   
                        completed in           
                        accordance with the    
                        statement/agreement    
                        cited above and all    
                        amendments thereto,    
                        together with all such 
                        modifications, either  
                        written or oral, as    
                        the Regional Project   
                        Officer and/or         
                        Assistance Officer or  
                        their representative   
                        have directed, as such 
                        modifications affect   
                        the                    
                        statement/agreement,   
                        and that all such work 
                        has been accomplished  
                        in accordance with the 
                        provisions contained   
                        in *Guidelines and     
                        Specifications for     
                        Flood Hazard Mapping   
                        Partners* cited in the 
                        contract document, and 
                        in accordance with     
                        sound and accepted     
                        engineering practices  
                        within the contract    
                        provisions for         
                        respective phases of   
                        the work.              

  Name:                                        

  Title:                                       

  Firm/Agency                                  
  Represented:                                 

  Registration No.:                            

  Signature:                                   

                        This form must be      
                        signed by a            
                        representative of the  
                        firm or agency         
                        contracted to perform  
                        the work, who must be  
                        a registered or        
                        certified professional 
                        in the area of work    
                        performed, in          
                        compliance with        
                        Federal and State      
                        regulations.           
  --------------------- ---------------------- ----------------------------------------------

### Transfer Methodology 

Floodplain Mapping data artifacts can be uploaded to the MIP by
following the guidelines for Data Submission and Validation located on
the MIP ([https://hazards.fema.gov](https://hazards.fema.gov/)) under
"User Guidance" in the "Guides & Documentation" tab of "MIP User Care".

### Directory Structure and Folder Naming Conventions

The files in section M.10.2 Requirements must be submitted within the
following directory structure which is created by the contractor within
their workspace prior to upload. The following folders can be created
either on a local work space (i.e., a personal computer) or within the
work space available for the community on the MIP. If the following
folders are generated locally, these newly created folders and their
contents must be uploaded to the MIP.

Data must be located in the appropriate directories as follows:

-   \\General

```{=html}
<!-- -->
```
-   XML_format metadata file

-   Draft FIS report

-   Project narrative

-   Certification of work

    -   \\Correspondence

    -   Letters; transmittals; memoranda; general status reports and
        queries; SPRs; technical issues; direction by FEMA; and internal
        communications, routing slips, and note

    -   \\Mapping\\FBS

-   FBS Self-Certification Documentation

    -   \\Mapping\\Redelineation\\Spatial Files

-   Spatial files

    -   \\Mapping\\Redelineation\\Topographic Data

```{=html}
<!-- -->
```
-   Topographic data files (if not submitted as part of data
    requirements described in section M.4)

    -   \\Mapping\\Digital Conversion\\Spatial Files

-   Spatial files

    -   \\Mapping\\Digital Conversion \\Base Map

-   Base map data files (if not submitted as part of data requirements
    described in section M.3)

# Post-Preliminary Data Submittal Standards

## Overview

This section describes the type and format of data required to be
submitted to FEMA that are generated during the post-preliminary phase
of the mapping process. All data must be submitted in digital format.
The Mapping Partner(s) contracted to "Manage Post Preliminary
Processing" is required to submit the data in this section.

There are a number of data artifacts generated for studies throughout
the post-preliminary processing, such as the flood elevation
determination notices, preliminary and final SOMAs, and Revalidation
letters which do not have associated workflow steps in the MIP workflow,
but include important information about the studies. It is extremely
important that FEMA captures these data artifacts as studies are
completed to ensure a complete set of technical study data is available
when questions arise about these studies and/or these studies are
updated in the future.

The submitting Mapping Partner must retain copies of all Project-related
data for a period of 3 years. The submitting Mapping Partner will need
these data in order to respond to the following:

-   Questions from FEMA or the receiving Mapping Partner during the
    review of the final draft materials;

-   Comments and appeals submitted to FEMA during the 90-day appeal
    period following the issuance of preliminary maps; and

-   Other concerns and issues that may develop during the processing of
    the revised FIS report and FIRM.

## Requirements 

### Data Files 

-   There are a number of documents and data generated after a FIRM is
    issued as preliminary. These documents and data are generated at
    various steps of the mapping process until the FIRM becomes
    effective. The following data files must be submitted at the
    designated MIP workflow steps:

-   MIP workflow step: Produce Preliminary Map Products:

```{=html}
<!-- -->
```
-   Preliminary SOMA

    -   MIP workflow step: Distribute Preliminary Map Products:

-   FBS Self-Certification Document (this document must be submitted
    within 30 days after issuance of maps as preliminary)

    -   MIP workflow step: Distribute LFD Letter:

-   FBS Self-Certification Document (this document must be submitted
    within 30 days after issuance of the LFD if floodplain boundaries
    were revised during the post-preliminary phase)

    -   MIP workflow step: Distribute Revalidation Letter

-   Flood Elevation Determination Docket (FEDD): The following documents
    must be included in the FEDD file per 44 CFR 67.3:

```{=html}
<!-- -->
```
-   Notice of proposed flood elevation determination to CEO (101/155
    letter)

-   Notice of proposed flood elevation determination published in paper

-   Notice of proposed flood elevation determination published in
    Federal Register

-   Appeals received by FEMA from CEO

-   Comments received by FEMA on the notice of the proposed flood
    elevation determination published in the Federal Register

-   Community's appeal or copy of its decision not to appeal the
    proposed flood elevation determination

-   Final determination with supporting documents (LFD)

-   Name of community subject to the flood elevation determination

-   FIS report

-   All correspondence between FEMA and the community concerning the
    study, reports of meetings among the Agency representatives,
    property owners, State coordinating agency, study contractors, or
    other interested persons;

-   Relevant publications;

-   Copy of completed flood elevations study consultation docket;

```{=html}
<!-- -->
```
-   Copies of Acknowledgement letters by FEMA to CEO;

-   Copies of resolution letters by FEMA to CEO;

-   Affidavit for the Notice of proposed flood elevation determination
    published in paper;

-   Revalidation letter; and

-   Notice of final flood elevation determination published in Federal
    Register.

### Certification of Work

Floodplain Boundary Standard self-certification must be submitted for
flood mapping projects funded by FEMA as described in section M.10.2.6.
The *Floodplain Boundary Standard Audit Procedures --* available at
FEMA's Guidelines and Specifications Web site *--* outline the
documentation needed for FBS compliance through self-certification. A
PDF of the self-certification form must be submitted digitally and must
have the original signature and date. This form must be signed by a
Registered Professional Engineer from the firm contracted to perform the
work, and/or by the appropriate government agency official.

### Acceptable File Formats

Documents and other supporting information identified in this section
must be submitted either in Word or PDF format.

### Metadata

Metadata is not required for post-preliminary data submittals. However,
supporting information during data submittals must be provided in the
abstract of Tools and Links. This abstract must include the CID, project
name, date of upload, filename, and FEDD. If FEDD is included in the
abstract it can be used as a Keyword in search and retrieve to pull all
the FEDD files. Abstracts for correspondence and publication data should
also state what the data involves. For correspondence, the abstract must
include the subject and names of individuals in the correspondence. For
publications, the source of publication and the date of publication must
be provided. If an additional file is uploaded under a category, the
abstract should then include the reason why, or specifically point out
the differences. If it is replacing a file because it is incorrect, and
that file is not overwritten when the new file is uploaded (because
filename does not match), MIPHelp may need to remove the incorrect file
so the incorrect data are not available.

### Transfer Media

Mapping Partners must submit files via the internet by uploading to the
MIP ([http://www.hazards.fema.gov](http://www.hazards.fema.gov/)) or on
one of the following electronic media:

-   CD-ROM;

-   DVD; or

-   External Hard Drive (for very large data submissions).

In special situations or as technology changes, other media may be
acceptable if coordinated with FEMA.

### Transfer Methodology 

Post-preliminary data artifacts can be uploaded to the MIP by following
the guidelines for Data Submission and Validation located on the MIP
([https://hazards.fema.gov](https://hazards.fema.gov/)) under "User
Guidance" in the "Guides & Documentation" tab of "MIP User Care."

### Directory Structure and Folder Naming Conventions

The files under section M.11.2 Requirements must be submitted in the
following directory structure created by the contractor in their
workspace prior to upload. The following folders can be created either
on a local work space (i.e., a personal computer) or within the work
space for the community on the MIP. If the following folders are
generated locally, these newly created folders and their contents must
be uploaded to the MIP.

The file naming convention for submitted files must include specific
information as defined under each folder. Data must be located in the
appropriate directories as follows:

-   \\SOMA

```{=html}
<!-- -->
```
-   Preliminary SOMA (File name:
    County_Community_State_SOMA_Preliminary)

-   Final SOMA (File name: County_Community_State_SOMA_Final)

    -   \\FBS

-   Self-Certification (File name: County or
    Community_State_FBS_Preliminary)

-   Self-Certification (if needed) (File name: County or
    Community_State_FBS_Final)

    -   \\FEDD

```{=html}
<!-- -->
```
-   Notice of proposed flood elevation determination to CEO (File name:
    County_Community_State_FEDD_CEOLetter_Date)

-   Notice of proposed flood elevation determination published in paper
    (File name: County_Community_State_FEDD_ProposedBFENotice)

-   Notice of proposed flood elevation determination published in
    Federal Register (File name:
    County_Community_State_FEDD_ProposedBFENoticeFR)

-   Appeals received by FEMA from CEO (File name:
    County_Community_State_FEDD_Appeals_Date)

-   Comments received by FEMA on the notice of the proposed flood
    elevation determination published in the Federal Register (File
    name: County_Community_State_FEDD_Comments_Date)

-   Community's appeal or copy of its decision not to appeal the
    proposed flood elevation determination (File name:
    County_Community_State_FEDD_Appeal_Date)

-   Final determination with supporting documents (File name:
    County_Community_State_FEDD_LFD_Date)

-   Name of community subject to the flood elevation determination

-   FIS report (File name: County or Community_State_FEDD_FISReport)

    -   All correspondence between FEMA and the community concerning the
        study , reports of meetings among the Agency representatives,
        property owners, state coordinating agency, study contractors,
        or other interested persons (File name:
        County_Community_State_FEDD_Correspondence_Date)

    -   Relevant publications (File name:
        County_Community_State_FEDD_Publication Name_Date)

    -   Copy of completed flood elevations study consultation docket
        (File name: County_Community_State_FEDD_Docket_Date)

    -   Copy of the FEMA's final determination

    -   Acknowledgement letters (File name:
        County_Community_State_FEDD_AckLetter_Date)

    -   Resolution letters (File name:
        County_Community_State_FEDD_ResolutionLetter_Date)

    -   Affidavits for BFE Notices (File name:
        County_Community_State_FEDD_Affidavit_Date)

    -   Copy of BFE Notice published in Federal Register (File name:
        County_Community_State_FEDD_FinalBFENoticeFR_Date)

        -   \\Revalidation

    -   Revalidation letters (File name:
        County_Community_State_Revalidation)

### Data Identification Requirements

When data are mailed to FEMA, all submitted digital media must be
labeled with the following information:

-   Mapping Partner name;

-   Community name and State for which the FIS was prepared;

-   Post-Preliminary Data;

-   Date of submission (formatted mm/dd/yyyy);

-   Disk \[*sequential number*\] of \[*number of disks*\] (if not
    uploaded through workflow). The media must be numbered sequentially,
    starting at Disk 1. \[Number of disks\] represents the total number
    of disks in the submission if the data is not uploaded through
    workflow on the MIP.

# GIS Spatial Requirements

This section describes the spatial files referenced in this appendix
which will be transferred to and merged with Appendix L of the
Guidelines when the update of Appendix L is completed, and a draft is
issued. Where possible, all mapping and engineering data elements will
be linked to physical geographic features that are georeferenced.

A GIS has the ability to precisely overlay the mapping and engineering
data. This approach supports a wide variety of existing and visionary
FEMA engineering and mapping products, such as digital mapping;
automated hydrologic and hydraulic modeling, automated mapping,
web-based publishing, and direct links between modeling and mapping
elements.

The DCS product is a GIS database made up of spatial data describing the
location of features on the earth and tabular data that describe the
attributes of these spatial features. The tables described in the
following sections that begin with "S\_" have a spatial component
associated with them. The tables described in the following sections
that begins with "L\_" are tabular (often referred to as a look-up or
business table); there is no direct spatial component.

Domain tables (tables in the specification that begin with D\_) were
established to assist FEMA's Mapping Partners in the creation of the
database related to the DCS. These domain tables provide the Mapping
Partner with valid or preferred attribute values for specific fields. A
domain table also helps minimize entry differences by standardizing the
value. For example, without domain tables, one user might enter
"floodway" while another user might enter "FLDWY" while completing the
FLOODWAY field in the S_Fld_Haz_Ar table. While both of these entries
reflect the same idea, the inconsistency between the two forms makes it
difficult to group similar features together. Using a domain table
ensures that both users enter the same value (i.e., floodway) to
describe the same feature. To capture local characteristics not included
in the domain table, Mapping Partners also may add and use their own
values in the domain table (e.g., a more restrictive locally regulated
floodway could be added to the accepted domain values as "Local
Floodway"). The domains utilized by this appendix are identified in
section M.12 Domain Tables.

A major aspect of GIS is horizontal and vertical position on the earth.
Mapping data must be referenced to a standard coordinate system, employ
a standard projection, and specify both the horizontal and the vertical
datums used. These positional references are established prior to the
field data collection and topographic mapping phase of the project. All
planimetric and topographic features must be collected and referenced to
this coordinate system and projection. See Appendix A of these
Guidelines for a detailed discussion of aerial mapping and surveying
specifications, which includes horizontal and vertical control for new
mapping. Also see Appendix B of these Guidelines for a discussion of
vertical datum selection and conversion.

As part of data collection, coordination and submittal, the assigned
Mapping Partner shall document the data sources, date of collection or
digitizing, scale of digitizing, projections, coordinate systems,
horizontal datum and vertical datum of all of the digital data used and
submitted. For each data source used, the assigned Mapping Partner shall
add a Source Citation entry to the DCS task-specific metadata file in
the Lineage section under Data Quality. Within the metadata file, each
data source is assigned a Source Citation Abbreviation.

The source citation value is assigned by the creator of the table. For
simplicity, it is strongly recommended that the source citation
abbreviation "MODEL" be used. For each model utilized in the study, the
source citation abbreviation should be numbered (e.g., MODEL1, MODEL2,
MODEL3). All of the spatial tables below have a SOURCE_CIT field. This
field should be populated with the source citation abbreviation from the
metadata file that applies to the related spatial feature.

The preferred projection, coordinate system, and horizontal datum for
the spatial data is the UTM projection and coordinate system and
referenced to the North American Datum of 1983 (NAD83). The data may
also be in a State Plane coordinate system and associated projection if
there is a compelling reason (e.g., project base map is in State Plane
coordinates). The assigned Mapping Partner shall obtain approval for
variations from these two options from the FEMA Lead in advance.
However, at a minimum, the assigned Mapping Partner shall create all
digital data in a system that is capable of referencing the data to a
geographic coordinate system and projection.

In the event that the county or other jurisdiction being mapped lies in
more than one projection and coordinate system zone, the assigned
Mapping Partner shall ensure that all digital data submitted are
projected in the zone that contains the largest portion of the
jurisdiction in a single zone. The assigned Mapping Partner shall not
use multiple State Plane or UTM zones within a single submittal. The
assigned Mapping Partner may compile data in another zone, particularly
if this facilitates higher positional accuracy of the data, reproject
the data to the chosen zone for the jurisdiction being mapped, and merge
the reprojected data with the rest of the data.

The assigned Mapping Partner shall compile all horizontal information on
either the North American Datum of 1927 (NAD27) (Clarke 1866 ellipsoid)
or NAD83 (Geodetic Reference System 1980 \-- GRS 80 ellipsoid or
revisions thereof). However, it is critical that horizontal datums not
be mixed within a Flood Map Project. See Appendix A of these Guidelines
for details on horizontal datum requirements.

The assigned Mapping Partner shall reference all vertical information to
either the National Geodetic Vertical Datum of 1929 (NGVD29) or the
NAVD88. However, the Mapping Partner must not mix vertical datums within
a Flood Map Project. See Appendix B of these Guidelines for details.

Digital files must be prepared using a pre-defined system or schema that
has been consistently used throughout. The attribute assigned to a
spatial element must be consistent and the information accessible to all
users. The data must be organized in one of the data structures
described in this Appendix and provided in one of the acceptable data
formats unless specific arrangements are made with the FEMA Project
Officer.

FEMA requires that all digital data be in one single file or a series of
thematic files that cover the entire geographic area being mapped
instead of individual small tiles that cover limited geographic areas.
The assigned Mapping Partner shall obtain approval for any variations to
this requirement from the FEMA Lead.

The assigned Mapping Partner shall ensure that vector data files must
meet the following data structure requirements:

-   All features must be digitized in their true positions as line
    strings or simple linear elements;

-   Line features must be continuous (no dashes, dots, patterns, or
    hatching);

-   Spatial layers must not contain curves, B-splines, or arcs;

-   Vectors may not cross other vectors within the same theme and all
    intersecting vectors must end at intersections;

-   Files must be free of discontinuities such as overlapping lines,
    gaps, \"turn backs,\" dangling lines and duplicate elements;

-   Spatial files must not contain any linear or area patterns; and

-   Gaps or overshoots between features that should close must be
    eliminated.

Logical consistency describes certain node-line-area relationships
internal to the digital data. The node-line-area relationship
requirements that the assigned Mapping Partner must meet include the
following:

-   Areas will be represented by closed polygons, without overshoots or
    undershoots;

-   Unattributed polygons are not permitted, including "sliver" polygons
    that result from poor digitizing methods;

-   Unnecessary nodes and vertices must be avoided;

-   Vertices must be placed conservatively when designing features so
    that only the minimal number of vertices or nodes is used to create
    the desired shape with appropriate smoothness (e.g., a straight line
    will be defined with two nodes only);

-   Lines must begin and end at nodes;

-   Lines must connect to each other at nodes; and

-   Lines must not extend through nodes.

Each DCS database table has a primary key field defined. This field is
normally the descriptive text similar to the table name followed by
"\_ID". The Mapping Partner that creates the digital data must populate
these fields. Normally, the assigned Mapping Partner shall number the
features in each table sequentially using this field; however, the
assigned Mapping Partner may choose another method provided that the
method is logical, documented, consistently implemented, and results in
a unique ID value for each spatial feature.

The assigned Mapping Partner must submit all of the applicable DCS
layers/tables. The Mapping Partner shall ensure that the applicable
fields use the appropriate values from the associated domain tables and
that these values are treated consistently across all attribute and
look-up tables. The components of the DCS database that are required
will depend on the task.

Mapping Partners may submit data in one of the following GIS file
formats:

-   ESRI personal geodatabase (PGDB)

-   ESRI shapefile (SHP)

-   Geography Markup Language (GML)

All of the submitted GIS layers and tables must be the same GIS file
format. For instance, the Mapping Partner cannot submit a portion of the
task-related layers in PGDB and a portion in SHP. Regardless of the GIS
date file format, the submittal also must include the metadata file.

For a GIS layer or table, there are inherent field properties that
specify the type and size of the data that will be stored. Generally
these properties are identified as the field name, field type, field
length, field precision, and field scale. The field name is the unique
term used to identify the table column (e.g., WTR_NM). The field type
indicates the type of data that are stored in the table column. Common
field types include text, date, float (i.e., a small fractional number),
double (i.e., a large fractional number), short integer (i.e., a small
integer number), and long integer (i.e., a large integer number).

The definition of the field length, precision, and scale depends on the
GIS data file format. For date and numeric field types in a PGDB, the
length describes the data size, in bytes, of the field. The length is
dependent upon the selected data type, and the user has no control over
its value. The precision and scale in a PGDB is not utilized and will
show only as a 0 value. For the date field type in an SHP, the length,
precision, and scale is inherent and cannot be specified by the user.
For the text field type in the PGDB, the user may opt to specify the
field length; the default value is 50. In this situation, the field
length indicates the number of characters that may be stored in the
table column (e.g., a text field which has a length of 100 may store no
more than 100 alphanumeric characters). Since only the data type and
length (for text fields) must be declared for the PGDB, the tables in
this appendix identifying the field properties will not include a
specification for precision and scale.

For reference, the default field length, precision, and scale for a PGDB
by data type are:

-   Double (8, 0, 0);

-   Float (4, 0, 0);

-   Long Integer (4, 0, 0);

-   Short Integer (2, 0, 0);

-   Date (8, 0, 0); and

-   Text (50, 0, 0).

For numeric field types in an SHP, the field length defines the total
number of characters that exist to the left and right of the decimal
place. The precision defines the number of characters to the left of
decimal place. The scale defines the number of characters to the right
of the decimal place. For those data types that store fractional values
(e.g., double and float), the user may define the precision and scale
(e.g., a double field type which has a scale of 2 and a precision of 10
will have a length of 12 and will allow the user to enter up to 2
decimal places). If the user opts to accept the default values of 0 for
the precision and scale, any number of decimal places (up to the length
size) may be stored. For those data types that store integer values
(e.g., short integer and long integer), the user may only define the
precision because the field value may not be fractional. For the date
field type in an SHP, the length, precision, and scale are inherent and
cannot be specified by the user. For the text field type, the field
length indicates the number of characters that may be stored in the
table column. The tables in this appendix identifying the field
properties will include the specification for the data type, length (for
text fields), precision (for numeric fields), and scale.

For reference, the default field length, precision, and scale for an SHP
by data type are:

-   Double (19, 0, 0);

-   Float (13, 0, 0);

-   Long Integer (9, 9, 0);

-   Short Integer (4, 4, 0);

-   Date (8, 0, 0); and

-   Text (50, 0, 0).

The GML field properties must match the SHP.

In the detailed table documentation in this section, each field name is
followed by a letter code as follows:

-   R -- Required for all records;

-   A -- Required if applicable to the described spatial feature or
    table record; and

-   O -- Optional; the Mapping Partner determines if the data for this
    field is available.

For required fields, Null values are not permitted. In the event that
the correct information cannot be obtained for a required field, the
Project Officer may allow the Mapping Partner to substitute a value that
indicates the affected field was intentionally not populated. Any use of
not populated values must be documented and explained in the metadata.
The value to use for not populated data for each field type is as
follows:

-   Text -- "NP";

-   Numeric -- -8888; and

-   Date -- 88880808.

For a field that is optional or required when applicable, but does not
apply, the value must be Null (i.e., the field must be left empty, not
set to zero). The Mapping Partner shall use the value zero only when an
attribute has the specific value of zero. Because of limitations in some
of the GIS formats used by FEMA, a true Null value cannot be used for
some fields. The value to use for "Null" fields for each field type is
as follows:

-   Text -- Null (or "", the empty string);

-   Numeric -- -9999; and

-   Date -- 99990909.

Date fields in the DCS database are stored in the native date format for
the GIS data file in which the table is distributed. The time of day is
not stored or is set to zero depending on the structure of the date
object in a particular data format. Where possible, the output format of
the date is set to YYYYMMDD.

## Floodplain Mapping Spatial Files - General

The following section describes the spatial file required to be produced
during the various tasks required of the Mapping Partners.

### Submittal Information 

The S_Submittal_Info layer contains essential information about the
study such as the FEMA case number and utilized engineering models. This
table is required to capture the spatial extent of the study areas and
must be submitted for each data development task by the assigned Mapping
Partner. These individual submissions will be integrated by the Mapping
Partner preparing the DFIRM Database.

The spatial entities representing the study areas are polygons
corresponding to the area to be revised by this case / the area covered
by the FIRM being revised / the area where new hydraulic analyses are to
be performed / the watershed boundaries of the catchments analyzed.
These can be one or multiple irregular shaped polygons to capture the
extent of the study area(s). If multiple polygons are required, the
attributes of each polygon should be set appropriately for the area
covered and all polygons for that project should contain the same FEMA
case number. Multiple polygons may be needed, for instance, when a
Mapping Partner performs hydraulic analyses for two streams - each with
a different type of hydraulic model. A single polygon would be created
for each of the study areas and the polygon's attribute values would
store the related model information. In cases where the flood hazards
for the entire County or Community included in the DFIRM have been
re-delineated and no new/updated study information was created, a single
polygon that matches the extent of the S_Pol_Ar polygon (see Appendix L)
shall be created. For the case where the flood hazards for a given DFIRM
were from both new/updated study data and re-delineated areas, the
polygon(s) for the re-delineated areas should not overlap with the
polygons for the new/re-study areas, and the outer edges should not
extend beyond the S_Pol_Ar polygon (see Appendix L) for the DFIRM.

The S_Submittal_Info layer contains the following elements:

SUBINF_ID R Primary key for table lookup. Assigned by table creator.

CASE_NO R FEMA Case Number. The FEMA case number is an alphanumeric
identifier for a project which is generated by the MIP. An example of a
FEMA case number for a study is 06-03-0002S.

CASE_DESC R Case Description. General description of the study area
outlining the extent of work performed. This description should include
the study location with limits of study, methods used, and any unique
circumstances associated with this study (e.g., This is a redelineation
of the East River using USGS DEMs.).

SUBMIT_BY R Data Submitter. Company name of Mapping Partner who is
submitting the dataset.

COMP_DATE R Completion Date. This is the date in which work was
completed by the assigned Mapping Partner.

HYDRO_MDL A Hydrologic Model. This is the name or abbreviation of the
hydrologic model that was used for the engineering analysis. Where
applicable, the version and year of the model must be specified. This
field is required when a hydrologic model was utilized in the study
area. Acceptable values for this field are listed in the D_Hydro_Mdl
table.

HYDRA_MDL A Hydraulic Model. This is the name or abbreviation of the
hydraulic model that was used for the engineering analysis. Where
applicable, the version and year of the model must be specified. This
field is required when a hydraulic model was utilized in the study area.
Acceptable values for this field are listed in the D_Hydra_Mdl table.

CST_MDL R Coastal Model. This is the name or abbreviation of the coastal
model that was used for the engineering analysis. Where applicable, the
version and year of the model must be specified. This field is required
when a coastal model was utilized in the study area. Acceptable values
for this field are listed in the D_Coastal_Mdl table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064183 .anchor}Table M.12-1. S_Submittal_Info
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SUBINF_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CASE_NO       | R   | Text     | 12    | Text     | 12    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CASE_DESC     | R   | Text     | 254   | Text     | 254   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SUBMIT_BY     | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| COMP_DATE     | R   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| HYDRO_MDL     | A   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| HYDRA_MDL     | A   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_MDL       | A   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

##  Floodplain Mapping Spatial Files -- Riverine Studies

The following sections describe the spatial files required for riverine
floodplain mapping submittals from Mapping Partners.

### Sub-Basins

The S_Subbasins layer is required for all types of hydrologic analyses.
The sub-basin features may overlap for different studies; however, they
cannot overlap within the same study. Watersheds are often divided into
sub-basins for hydrologic analyses. The outlet of a sub-basin typically
has a node associated with it which is often used as a point of
reference for flow computations.

The spatial entities representing sub-basins are polygons.

The S_Subbasins layer contains the following elements.

SUBBAS_ID R Primary key for table lookup. Assigned by table creator.

SUBBAS_NM A Sub-Basin Name. The sub-basin name matches what was used in
the model. This field is populated for detailed and limited detailed
studies. This field may also be populated when this information is
available for approximate studies.

SUB_AREA R Area of Sub-Basin. This is the area of the sub-basin.

AREA_UNIT R Area Units. This unit indicates the measurement system used
for the sub-basin area. Normally this would be square miles. Acceptable
values for this field are listed in the D_Area_Units table.

NODE_ID A Node Identification. This stores a code that links to the
S_Nodes table. The node is associated with the sub-basin. This field is
populated when the sub-basin has a node that was utilized for flow
computations.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064184 .anchor}Table M.12-2. S_Subbasins
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SUBBAS_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SUBBAS_NM     | A   | Text     | 254   | Text     | 254   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SUB_AREA      | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| AREA_UNIT     | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| NODE_ID       | A   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Nodes

The S_Nodes layer is required for all types of hydrologic analyses. Each
point in this spatial data must have associated computed discharge
values. The contributing drainage area and the 10‑, 2-, 1‑, and
0.2-percent-annual-chance flood discharges represent the total discharge
at that node. The points or nodes must lie on the profile baseline.
Nodes can represent sub basin pour points or confluences. The work map
in figure M-9 illustrates the proper placement of nodes. Note that nodes
are required at all flow change locations.

For hydraulic models that use nodes, such as SWMM or ICPR, the nodes can
be used to represent structures or hydraulic elements. In these cases,
the nodes and the profile baseline file are used to represent the
hydraulic connectivity of the network. Nodes can also represent more
detailed inventory, such as manholes or curb inlets. For situations
where cross sections are not integral to modeling, the cross section
spatial file should not be submitted and the water-surface elevations
must be reported in the nodes file.

The spatial entities representing nodes are points.

The S_Nodes layer contains the following elements.

NODE_ID R Primary key for table lookup. Assigned by table creator.

NODE_NAME A Node Name. This describes the location of the node. This
name matches what is used in the model. Must be unique across a
watershed. This field is populated for detailed and limited detailed
studies. This field may also be populated when this information is
available for approximate studies.

NODE_TYP R Node Type. Values include junction (default), structure,
outlet, and diversion. Acceptable values for this field are listed in
the D_Node_Typ table.

WTR_NM R Surface Water Name. This is the name of the stream or water
body.

DRAIN_AREA R Drainage Area. This is the contributing drainage area in
square miles.

AREA_UNIT R Area Units. This unit indicates the measurement system used
for the drainage area. Normally this would be square miles. Acceptable
values for this field are listed in the D_Area_Units table.

DSCH_10PCT R 10-percent Discharge. Discharge for the
10-percent-annual-chance flood at the node.

DSCH_2PCT R 2-percent Discharge. Discharge for the
2-percent-annual-chance flood at the node.

DSCH_1PCT R 1-percent Discharge. Discharge for the
1-percent-annual-chance flood at the node.

DSCH_02PCT R 0.2-percent Discharge. Discharge for the
0.2-percent-annual-chance flood at the node.

DISCH_UNIT R Discharge Units. This unit indicates the measurement system
used for the discharge associated with the drainage area. Normally this
would be cubic feet per second (cfs). Acceptable values for this field
are listed in the D_Discharge_Units table.

WSEL_10PCT A 10-percent Water-Surface Elevation. Water-surface elevation
for the 10-percent-annual-chance flood at the node. This field is
populated when cross sections are not utilized in the engineering
analysis.

WSEL_2PCT A 2-percent Water Surface Elevation. This is the water-surface
elevation for the 2-percent-annual-chance flood at the node. This field
is populated when cross sections are not utilized in the engineering
analysis.

WSEL_1PCT A 1-percent Water-Surface Elevation. This is the water-surface
elevation for the 1-percent-annual-chance flood at the node. This field
is populated when cross sections are not utilized in the engineering
analysis.

WSEL_02PCT A 0.2-percent Water-Surface Elevation. This is the
water-surface elevation for the 0.2-percent-annual-chance flood at the
node. This field is populated when cross sections are not utilized in
the engineering analysis.

LEN_UNIT A Water-Surface Elevation Units. This unit indicates the
measurement system used for the water-surface elevation. Normally this
would be feet. This field is populated when cross sections are not
utilized in the engineering analysis. Acceptable values for this field
are listed in the D_Length_Units table.

V_DATUM A Vertical Datum. The vertical datum indicates the reference
surface from which the flood elevations are measured. Normally this
would be NAVD88. This field is populated when cross sections are not
utilized in the engineering analysis. Acceptable values for this field
are listed in the D_V_Datum table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc209951125 .anchor}Figure M-9. **Example of Proper
Node Placement**

![](media/image9.jpeg){width="6.4in" height="3.709722222222222in"}

[]{#__RefHeading___Toc210064185 .anchor}Table M.12-3. S_Nodes Spatial
File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| NODE_ID       | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| NODE_NAME     | A   | Text     | 254   | Text     | 254   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| NODE_TYP      | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WTR_NM        | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DRAIN_AREA    | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| AREA_UNIT     | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DSCH_10PCT    | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DSCH_2PCT     | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DSCH_1PCT     | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DSCH_02PCT    | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DISCH_UNIT    | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_10PCT    | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_2PCT     | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_1PCT     | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_02PCT    | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LEN_UNIT      | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Profile Baseline

The S_Profil_Basln layer is required for all types of hydraulic
analyses. The profile baseline shows the path of flood flows on the FIRM
and is representative of the distance between cross sections, nodes, or
grids in the hydraulic model. The profile baseline is used for
stationing of the profiles found in the FIS.

The spatial entities representing the profile baseline are lines.

The S_Profil_Basln layer contains the following elements.

BASELN_ID R Primary key for table lookup. Assigned by table creator.

WTR_NM R Surface Water Name. This is the name of the stream or water
body.

SEGMT_NAME O Segment Name. This is an optional identification string for
each reach. If used, this value must be unique for a stream.

STUDY_TYP R Study Type. This describes the type of study performed for
flood hazard identification. Acceptable values for this field are listed
in the D_Study_Typ table.

UP_NODE A Upstream Node. This is the node ID at the upstream end of the
reach. This ID field must contain a number that matches the NODE_ID
field in the S_Nodes table, which documents points used to define the
topology of the hydrologic network. This field is populated when the
feature is associated with an upstream node and when the WATER_TYP
attribute value equals "PROFILE BASELINE" or "PROFILE BASELINE AND
STREAM CENTERLINE". In the DCS submission, the WATER_TYP value will
always be "PROFILE BASELINE" or "PROFILE BASELINE AND STREAM
CENTERLINE"; in the DFIRM Database this layer will store more than the
profile baseline and should only be populated when the feature is a
profile baseline.

DN_NODE A Downstream Node. This is the node ID at the downstream end of
the reach. This ID field must contain a number that matches the NODE_ID
field for a record in the S_Nodes table, which documents points used to
define the topology of the hydrologic network. This field is populated
when the feature is associated with a downstream node and when the
WATER_TYP attribute value equals "PROFILE BASELINE" or "PROFILE BASELINE
AND STREAM CENTERLINE". In the DCS submission, the WATER_TYP value will
always be "PROFILE BASELINE" or "PROFILE BASELINE AND STREAM
CENTERLINE"; in the DFIRM Database this layer will store more than the
profile baseline and should only be populated when the feature is a
profile baseline.

ROUTE_METH A Hydrologic Routing Method. This is the hydrologic routing
method used for the reach. This field is only populated if hydrologic
routing is used for the reach.

WATER_TYP R Surface Water Feature Type. The type value describes the
kind of watercourse represented. In Appendix M, this value will always
be "PROFILE BASELINE" or "PROFILE BASELINE AND STREAM CENTERLINE". The
S_Profil_Basln layer created as part of the DCS will be incorporated
into a more comprehensive layer as detailed in Appendix L. Acceptable
values for this field are listed in the D_Wtr_Typ table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064186 .anchor}Table M.12-4. S_Profil_Basln
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| BASELN_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WTR_NM        | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SEGMT_NAME    | O   | Text     | 254   | Text     | 254   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STUDY_TYP     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| UP_NODE       | A   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DN_NODE       | A   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| ROUTE_METH    | A   | Text     | 254   | Text     | 254   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WATER_TYP     | R   | Text     | 40    | Text     | 40    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Cross Sections 

The S_XS layer is required for models that utilize cross sections. Cross
sections define the geometry of the floodplain for input into the
hydraulic model, which then calculates flood elevations. Select cross
section locations are shown on the Flood Profiles in the FIS report and
can be used to cross reference the Flood Profiles to the planimetric
depiction of the flood hazard. All cross sections for which a spatial
location is available should be included in this table. It is not
required for 2-D models that do not employ cross sections for simulating
water surfaces.

The spatial entities representing the cross sections are lines.

The S_XS layer contains the following elements.

XS_LN_ID R Primary key for table lookup. Assigned by table creator.

XS_SOURCE R Cross Section Source Method. This value describes the
general methodology used in deriving the station and elevation data
along cross sections used in riverine flood hazards. Acceptable values
for this field are listed in the D_Method table.

STREAM_STN R Stream Station. This is the measurement along the profile
baseline to the cross section location.

STN_UNIT R Stream Station Unit. This unit indicates the measurement
system used for the stream stationing. Acceptable values for this field
are listed in the D_Length_Units table.

WTR_NM R Surface Water Feature Name. This is the name of the stream or
water body.

WSEL_10PCT R 10-percent Water-Surface Elevation. This is the
water-surface elevation for the 10-percent-annual-chance flood at the
cross section.

WSEL_2PCT R 2-percent Water-Surface Elevation. This is the water-surface
elevation for the 2-percent-annual-chance flood at the cross section.

WSEL_1PCT R 1-percent Water-Surface Elevation. This is the water-surface
elevation for the 1-percent-annual-chance flood at the cross section.

WSEL_02PCT R 0.2-percent Water-Surface Elevation. This is the
water-surface elevation for the 0.2-percent-annual-chance flood at the
cross section.

LEN_UNIT R Water-Surface Elevation Units. This unit indicates the
measurement system used for the water-surface elevation. Normally this
would be feet. Acceptable values for this field are listed in the
D_Length_Units table.

V_DATUM R Vertical Datum. The vertical datum indicates the reference
surface from which the flood elevations are measured. Normally this
would be NAVD88. Acceptable values for this field are listed in the
D_V_Datum table.

VEL_10PCT A 10-percent Velocity. This is the velocity for the
10-percent-annual-chance flood at the cross section. This field is
populated when the 10-percent-annual-chance flood is analyzed in the
hydraulic model.

VEL_2PCT A 2-percent Velocity. This is the velocity for the
2-percent-annual-chance flood at the cross section. This field is
populated when the 2-percent-annual-chance flood is analyzed in the
hydraulic model.

VEL_1PCT A 1-percent Velocity. This is the velocity for the
1-percent-annual-chance flood at the cross section. This field is
populated when the 1-percent-annual-chance flood is analyzed in the
hydraulic model.

VEL_02PCT A 0.2-percent Velocity. This is the velocity for the
0.2-percent-annual-chance flood at the cross section. This field is
populated when the 0.2-percent-annual-chance flood is analyzed in the
hydraulic model.

VEL_UNIT R Velocity Units. This unit specifies the unit of measurement
for the velocity of the floodway. Acceptable values for this field are
listed in the D_Velocity_Units table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064187 .anchor}Table M.12-5. S_XS Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| XS_LN_ID      | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| XS_SOURCE     | R   | Text     | 30    | Text     | 30    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STREAM_STN    | R   | Text     | 12    | Text     | 12    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STN_UNIT      | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WTR_NM        | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_10PCT    | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_2PCT     | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_1PCT     | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WSEL_02PCT    | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LEN_UNIT      | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_10PCT     | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_2PCT      | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_1PCT      | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_02PCT     | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_UNIT      | R   | Text     | 30    | Text     | 30    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

####  {#section-1 .unnumbered}

### Base Flood Elevations (BFEs)

The S_BFE layer is required when base flood elevations are developed as
part of the hydraulic or coastal analysis. The S_BFE table contains
information about the BFEs within a study area. BFE lines indicate the
rounded whole-foot water-surface elevation of the
1-percent-annual-chance flood.

The spatial entities representing the BFEs are lines. The BFE line
extends from the SFHA to SFHA boundary. The BFE line will have no
visible gaps or overshoots between the SFHA boundary and the end of the
BFE line at the publication scale of the FIRM. Each BFE is represented
by a single line. Generally the BFE is a straight line although they may
bend consistent with the procedures described in Volume 1 of these
Guidelines.

The S_BFE layer contains the following elements.

BFE_LN_ID R Primary key for table lookup. Assigned by table creator.

ELEV R Base Flood Elevation. The rounded, whole-foot elevation of the
1-percent-annual-chance flood.

LEN_UNIT R BFE Units. This unit indicates the measurement system used
for the BFEs. Normally this would be feet. Acceptable values for this
field are listed in the D_Length_Units table.

V_DATUM R Vertical Datum. The vertical datum indicates the reference
surface from which the flood elevations are measured. Normally this
would be NAVD88 for new studies. Acceptable values for this field are
listed in the D_V_Datum table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064188 .anchor}Table M.12-6. S_BFE Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| BFE_LN_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| ELEV          | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LEN_UNIT      | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

####  {#section-2 .unnumbered}

### Alluvial Fan Spatial File

The S_Alluvial layer is required when the modeling includes alluvial
fans. Only the 1-percent-annual-chance flood is mapped for alluvial
fans. The alluvial fan could be mapped as: Zone AO areas with depths and
velocities; Zone AO areas with just depths; or as Zone A, AE, or X.

The spatial entities representing the alluvial fans are polygons.

The S_Alluvial layer contains the following elements.

ALLUVL_ID R Primary key for table lookup. Assigned by table creator.

VELOCITY A Velocity. This value represents the velocity of the
1-percent-annual-chance flood flow in this area. This field is populated
when a velocity is shown on the FIRM.

VEL_UNIT A Velocity Unit. This is the unit of measurement for the
velocity for the 1-percent-annual-chance flood. This field is populated
when the VELOCITY field is populated. Acceptable values for this field
are listed in the D_Velocity_Units table.

DEPTH A Depth. This is the depth for the 1-percent-annual-chance flood
for Zone AO areas. This field is populated if the hydraulic analysis
determines a depth for the AO zone.

DEPTH_UNIT A Depth Units. This unit indicates the measurement system
used for depths. This field is populated when the DEPTH field is
populated. Acceptable values for this field are listed in the
D_Length_Units table.

FLD_ZONE R Flood Zone. This is the flood zone designation for the
alluvial fan. These zones are used by FEMA to designate the SFHAs and
for insurance rating purposes. NOTE: The symbol '%' is a reserved symbol
in most software packages so the word 'percent' was abbreviated to
'PCT'. Acceptable values for this field are listed in the D_Zone table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064189 .anchor}Table M.12-7. S_Alluvial Spatial
File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| ALLUVL_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VELOCITY      | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_UNIT      | A   | Text     | 30    | Text     | 30    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DEPTH         | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DEPTH_UNIT    | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| FLD_ZONE      | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Flood Hazard Area Spatial File

The S_Fld_Haz_Ar layer contains information about the flood hazards
within the study area. These zones are used to designate the SFHA and
for insurance rating purposes. These data must be the regulatory flood
zones designated by FEMA.

The spatial entities representing the flood zones are polygons. All
stream reaches being restudied or redelineated should have a
corresponding flood zone polygon. There is one polygon for each
contiguous flood zone designated.

The S_Fld_Haz_Ar layer contains the following elements.

FLD_AR_ID R Primary key for table lookup. Assigned by table creator.

STUDY_TYP R Study Type. This describes the type of study performed for
flood hazard identification. Acceptable values for this field are listed
in the D_Study_Typ table.

FLD_ZONE R Flood Zone. This is a flood zone designation. These zones are
used by FEMA to designate the SFHAs and for insurance rating purposes.
NOTE: The symbol '-percent' is a reserved symbol in most software
packages so the word 'percent' was abbreviated to 'PCT'. Acceptable
values for this field are listed in the D_Zone table.

FLOODWAY A Floodway Type. Floodway areas are designated by FEMA and
adopted by communities to provide an area that will remain free of
development to moderate increases in flood heights due to encroachment
on the floodplain. Normal floodway areas are specified as 'FLOODWAY'.
Special cases will have a more specific term for the designation (such
as COLORADO RIVER). This field is populated when the area is designated
as a floodway. Acceptable values for this field are listed in the
D_Floodway table.

SFHA_TF R Special Flood Hazard Area. If the area is within the SFHA,
this field would be true. This field will be true for any area that is
coded for any A or V zone flood areas. It should be false for all other
flood zone areas. Acceptable values for this field are listed in the
D_TrueFalse table.

STATIC_BFE A Static Base Flood Elevation. This field will be populated
for areas that have been determined to have a constant BFE. In this
situation, the same BFE applies to the entire polygon. This normally
occurs in lakes and coastal zones.

V_DATUM A Vertical Datum. The vertical datum indicates the reference
surface from which the flood elevations are measured. Normally this
would be NAVD88 for new studies. This field is only populated when the
STATIC_BFE field is populated. Acceptable values for this field are
listed in the D_V_Datum table.

DEPTH A Depth. This is the depth for Zone AO Areas. This field is only
populated when a depth is associated with the flood zone area.

LEN_UNIT A Length Units. This unit indicates the measurement system used
for the BFEs and/or depths. Normally this would be feet. This field is
populated when the STATIC_BFE or DEPTH field is populated. Acceptable
values for this field are listed in the D_Length_Units table.

VELOCITY A Velocity. This is the velocity measurement of the flood flow
in the area. Normally this is applicable to alluvial fan areas (certain
Zone AO areas). This field is populated when a velocity is associated
with the flood zone area.

VEL_UNIT A Velocity Unit. This is the unit of measurement for the
velocity. This field is populated when the VELOCITY field is populated.
Acceptable values for this field are listed in the D_Velocity_Units
table.

AR_REVERT A Revert Zone. If the area is Zone AR, this field would hold
the zone that the area would revert to if the AR zone were removed. This
field is populated when the corresponding area is Zone AR. Acceptable
values for this field are listed in the D_Zone table.

BFE_REVERT A Revert BFE. If Zone is Zone AR, this field would hold the
static BFE for the reverted zone. This field is populated when Zone
equals AR, and the reverted zone has a static BFE. The elevation unit is
referenced in the LEN_UNIT field.

DEP_REVERT A Revert Depth. If Zone is Zone AR, this field would hold
that flood depth for the reverted zone. This field is populated when
Zone equals AR, and the reverted zone has an assigned depth. The depth
unit is referenced in the LEN_UNIT field.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064190 .anchor}Table M.12-8. S_Fld_Haz_Ar
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+===============+=====+==========+=======+==========+=======+=======+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| FLD_AR_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STUDY_TYP     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| FLD_ZONE      | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| FLOODWAY      | A   | Text     | 40    | Text     | 40    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SFHA_TF       | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STATIC_BFE    | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DEPTH         | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LEN_UNIT      | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VELOCITY      | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VEL_UNIT      | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| AR_REVERT     | A   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| BFE_REVERT    | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| DEP_REVERT    | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

####  {#section-3 .unnumbered}

### General Structures Spatial File

The S_Gen_Struct layer is required whenever hydraulic structures are
shown in the flood profile. It is also required if levees are shown on
the FIRM, channels containing the flooding are shown on the FIRM, or any
other structure that impacts the area's flood risk is shown on the FIRM.

The S_Gen_Struct table contains information about the hydraulic and
coastal structures within the study area. It must include all structures
shown in the flood profiles. In addition, levees, sea walls, channels
that contain flooding, and other significant flood-control structures
shown on the FIRM must be included. A spatial file with location
information also corresponds with this data table.

The spatial entities representing general structures are represented by
lines. The lines must represent the primary characteristic of the
structure. For example, bridges must be represented by the
transportation centerline carried by the bridge. Dams must be
represented by a line corresponding to the top of the dam. Levees must
be represented by a line corresponding to the top of levee. A line
corresponding to the centerline of the main barrel must represent a
culvert.

The S_Gen_Struct table contains the following elements.

STRUCT_ID R Primary key for table lookup. Assigned by table creator.

STRUCT_TYP R Structure Type. Hydraulic and coastal structures within the
study area. Acceptable values for this field are listed in the
D_Struct_Typ table.

CST_STRUCT A Coastal Structure Classification. This provides the primary
classification of the coastal structure. This field is populated when
the structure type is a coastal structure. Acceptable values for this
field are listed in the D_Cst_Struct table.

STRUCT_NM A Structure Name. This is the proper name of the feature
and/or the related transportation feature name. If the flood profile has
the proper structure name and no related transportation name, this field
stores the proper name (e.g., Hoover Dam). If the flood profile has the
related transportation name and no proper name, this field stores the
related transportation name (e.g., Main Street). If the flood profile
has the proper name and the transportation name, this field stores both
names (e.g., Hoover Dam / Main Street). If structure has no proper name
and no related transportation name, this field is left blank; this field
should not store the structure type (e.g., dam).

WTR_NM R Surface Water Name. This is the name of the stream or water
body.

CST_STR_ID A Coastal Structure ID. This stores a code that links to the
L_Cst_Struct table. This field is populated when the structure feature
is a coastal structure.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064191 .anchor}Table M.12-9. S_Gen_Struct
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STRUCT_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STRUCT_TYP    | R   | Text     | 36    | Text     | 36    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_STRUCT    | A   | Text     | 40    | Text     | 40    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STRUCT_NM     | R   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WTR_NM        | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_STR_ID    | A   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

## Required Floodplain Mapping Spatial Files -- Coastal Studies

The following are the required spatial files and data tables for coastal
submittals. Mapping Partners should note that not all fields are
relevant to all studies.

### Coastal Transects 

The S_Cst_Tsct_Ln layer is required for all coastal studies for which
transect-based analyses are performed. Normally this is any area with a
coastal study. The S_Cst_Tsct_Ln table contains information about the
Coastal Transect Lines within the study area, if applicable. The
transect lines indicate the location that was used to provide
representative topographic information for the coastal flood models
used. Hydraulic analyses of coastal flood effects are executed along
transects, which are cross sections taken perpendicular to the shoreline
representing a segment of coast with similar characteristics. Data are
compiled primarily for transects, which, in turn, are situated on work
maps at the final scale of the DFIRM. Work maps are used to located and
develop transects and to interpolate and delineate the flood zones and
elevations.

The spatial elements representing coastal transects are lines generally
extending from offshore all the way across the coastal floodplain.
Transects can also extend seaward when wave runup modeling is used when
determining coastal flood hazards. Each transect should be represented
by a single line feature without the circles on each end shown on the
hard copy map. The location and shape of the lines should depict, as
accurately as possible, the position of the transect used.

The S_Cst_Tsct_Ln table contains the following elements:

TRAN_LN_ID R Primary key for table lookup. Assigned by table creator.

TRAN_NO R Transect Number. Each transect is normally numbered
sequentially.

CST_MDL_ID R Coastal Model Identification. This field is populated by a
code that links to the L_Cst_Model table. Multiple transects may link to
a single record in the L_Cst_Model table. This field is populated for
new coastal studies.

METHOD R Transect Source Method. This value describes the general
methodology used in deriving the station and elevation point data along
transects used in coastal flood hazards. Acceptable values for this
field are listed in the D_Method table.

VZONE_EXT R V Zone Extent. This information provides a brief summary to
users about the predominating methodology that was used to determine the
landward extent of the V Zone in any mapped flood hazard area.
Acceptable values for this field are listed in the D_VZone table.

SETUP_DPTH R Wave Set-up Depth. This is the depth of the wave setup that
is added to the 1-percent-annual-chance SWEL. Normally shown in feet.

SIG_HT R Significant Wave Height. This is the wave height associated
with the 1-percent annual chance storm event. It is the average height
of the highest 1/3 of all waves. It is used in WHAFIS 3.0 and RUNUP 2.0
models. Normally shown in feet.

SIG_PD R Significant Wave Period. This is the wave period associated
with the 1-percent annual chance storm event. It is the time it takes
for a wave of the significant wave height to pass a point. Normally
shown in seconds.

CON_HT A Controlling Wave Height. The controlling wave height value is
1.6 times the significant wave height. This field is populated when the
controlling wave height is available for the start of each transect.
This field is not required if the controlling wave height is not
available for the start of each transect, and WHAFIS default values are
used.

CONHT_UNIT A Controlling Wave Height Unit. This unit indicates the
measurement system used for the controlling wave height. Normally shown
in feet. This field is populated when the CON_HT field is populated.
Acceptable values for this field are listed in the D_Length_Units table.

CON_PD A Controlling Wave Period. It is the time it takes for a wave of
the controlling wave height to pass a point. Normally shown in seconds.
This field is populated when the controlling wave period is available
for the start of each transect. This field is not required if the
controlling wave period is not available for the start of each transect,
and WHAFIS default values are used.

MEAN_HT R Mean Wave Height. Average height of all waves. This
information is typically derived from wave gage data.

MEAN_PD R Mean Wave Period. Average period of all waves. This
information is typically derived from wave gage data. Normally shown in
seconds.

FETCH_LEN R Fetch Length. This is the starting fetch length.

FTCHLNUNIT R Fetch Length Units. This unit indicates the measurement
system used for the fetch length. Normally shown in miles. Acceptable
values for this field are listed in the D_Length_Units table.

EROS_METH A Erosion Methodology. This field describes the erosion
methodology. This field is populated when dunes are present in the study
area. Acceptable values for this field are listed in the D_Erosion
table.

L_RANGE R Left Range of Coastal Transect. Looking landward, the range is
the along-shore distance to the left of the transect line that the
transect is intended to represent.

L_DIRECT R Direction of Left Range. Direction is entered as the bearing
of the range away from the transect. The left range direction is
measured in degrees and is the angle of an arc taken in a clockwise
direction from north to the range's bearing. If the transect is oriented
perpendicular to the shoreline, this value will be +/- 90 degrees of the
transect's direction in degrees from north.

R_RANGE R Right Range of Coastal Transect. Looking landward, the range
is the along-shore distance to the right of the transect line that the
transect is intended to represent.

R_DIRECT R Direction of Right Range. Direction is entered as the bearing
of the range away from the transect. The right range direction is
measured in degrees and is the angle of an arc taken in a clockwise
direction from north to the range's bearing. If the transect is oriented
perpendicular to the shoreline, this value will be +/- 90 degrees of the
transect's direction in degrees from north.

LOC_DESC R Location Description. This field describes the location of
the coastal transect, such as "starts at the Atlantic Ocean Shoreline
200 feet east of Main Street."

LU_SOURCE R Land Use Description Source. This is the description of a
land use data source along the transect (aerials, land-use shapefile,
etc.).

XCOORD R X-Coordinate. The X-coordinate of the 0.0-foot elevation point
along the transect. This point must fall on the transect and have the
same horizontal datum of the subsequent DFIRM study. The coordinates
must be entered using the same coordinate system intended for the DFIRM
Database. If the S_Shore_Ln spatial file is provided, the shoreline
should cross the transect at this point.

YCOORD R Y-Coordinate. The Y-coordinate of the 0.0-foot elevation point
along the transect. This point must fall on the transect and have the
same horizontal datum of the subsequent DFIRM study. The coordinates
must be entered using the same coordinate system intended for the DFIRM
Database. If the S_Shore_Ln spatial file is provided, the shoreline
should cross the transect at this point.

WTR_NM R Surface Feature Water Name. This is the formal name of the
surface water feature acting as the primary flooding source for the
transect line.

V_DATUM R Vertical Datum. This is the vertical datum in which the
transect lines were drawn. The vertical datum indicates the reference
surface from which the flood elevations are measured. Normally this
would be NAVD88. Acceptable values for this field are listed in the
D_V_Datum table.

CSTLN_TYP R Coastline Type. This describes the type of coastline.
Acceptable values for this field are listed in the D_Cst_Typ table.

SWEL_1PCT R 1-percent-annual-chance SWEL. This is the starting SWEL for
the 1-percent-annual-chance flood.

ELEV_UNIT R Elevation Units. This is the unit of measurement for the
SWEL. Acceptable values for this field are listed in the D_Length_Units
table.

WAVE_02PCT R 0.2-percent Wave Calculations. Were 0.2-percent wave
calculations performed? Acceptable values for this field are listed in
the D_TrueFalse table.

LEN_UNIT R Length Units. This unit indicates the measurement system used
for wave setup depth, significant wave height, or mean wave height.
Normally this would be feet. Acceptable values for this field are listed
in the D_Length_Units table.

TIME_UNIT R Units of Time Measurement. This field is populated if there
is a value entered for the significant wave period, controlling wave
period, or the mean wave period. The period values all should use the
same unit of time measurement. Acceptable values for this field are
listed in the D_Time_Units table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064192 .anchor}Table M.12-10. S_Cst_Tsct_Ln
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+===============+=====+==========+=======+==========+=======+=======+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TRAN_LN_ID    | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TRAN_NO       | R   | Text     | 4     | Text     | 4     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_MDL_ID    | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| METHOD        | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| VZONE_EXT     | R   | Text     | 40    | Text     | 40    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SETUP_DPTH    | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SIG_HT        | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SIG_PD        | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CON_HT        | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CONHT_UNIT    | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CON_PD        | A   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| MEAN_HT       | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| MEAN_PD       | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| FETCH_LEN     | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| FTCHLNUNIT    | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| EROS_METH     | A   | Text     | 15    | Text     | 15    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| L_RANGE       | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| L_DIRECT      | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| R_RANGE       | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| R_DIRECT      | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LOC_DESC      | R   | Text     | 250   | Text     | 250   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LU_SOURCE     | R   | Text     | 254   | Text     | 254   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| XCOORD        | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| YCOORD        | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WTR_NM        | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CSTLN_TYP     | R   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SWEL_1PCT     | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| ELEV_UNIT     | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WAVE_02PCT    | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LEN_UNIT      | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIME_UNIT     | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Coastal Model

The L_Cst_Model table is completed if a coastal engineering analysis was
performed. It is required for new coastal studies. The L_Cst_Model table
is a lookup table that contains information about the coastal models
that were used during the engineering analysis.

The L_Cst_Model table contains the following elements.

CST_MDL_ID R Primary key for table lookup. Assigned by table creator.

WTR_NM R Surface Water Feature Name. This is the formal name of the
surface water feature.

SURGE_MDL R Hurricane Surge Model. This is the name or abbreviation of
the FEMA-approved hurricane surge model that is associated with the
coastal engineering analysis. Acceptable values for this field are
listed in the D_Surge_Mdl table.

SURGE_DATE R Hurricane Surge Model Run Date. This is the date the model
was run.

SURGE_ZIP R Surge File. \<Filename.zip\> containing surge model input,
surge model output, README.TXT, and any other supporting reports and
documentation.

SURGE_EFF R Surge Effective Date. Effective date of the surge model.

WAVEHT_MDL A Wave Height Model. This is the name or abbreviation of the
FEMA approved wave height model that was used for the coastal
engineering analysis. Acceptable values for this field are listed in the
D_Wave_Mdl table.

WAVEHT_DT A Wave Height Model Run Date. This is the date the model was
run.

RUNUP_MDL A Runup Model. This is the name or abbreviation of the
FEMA‑approved wave runup model that was used for the coastal engineering
analysis. Acceptable values for this field are listed in the D_Runup_Mdl
table.

RUNUP_DATE A Runup Model Run Date. This is the date the wave runup model
was run.

SETUP_METH A Wave Setup Methodology. This information should detail the
methodology used for determining the wave setup magnitude.

SETUP_DATE A Wave Setup Methodology Date. This is the date the setup
methodology was run.

PFD_TF R Primary Frontal Dune. Have primary frontal dune criteria been
applied in the coastal modeling? Acceptable values for this field are
listed in the D_TrueFalse table.

EROS_TF A Erosion Treatment. Has erosion treatment been applied in the
coastal modeling? Acceptable values for this field are listed in the
D_TrueFalse table.

WAVE_EFF A Wave Effective Date. Effective date of the wave height and
wave runup models

WAVE_ZIP A Wave Files. \<Filename.zip\> containing wave height input,
wave height output, wave runup input, wave rump output, README.TXT, and
any other supporting reports and documentation.

[]{#__RefHeading___Toc210064193 .anchor}Table M.12-11. L_Cst_Model Table

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+===============+=====+==========+=======+==========+=======+=======+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_MDL_ID    | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WTR_NM        | R   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SURGE_MDL     | R   | Text     | 40    | Text     | 40    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SURGE_DATE    | R   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SURGE_ZIP     | R   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SURGE_EFF     | R   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WAVEHT_MDL    | A   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WAVEHT_DT     | A   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| RUNUP_MDL     | A   | Text     | 30    | Text     | 30    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| RUNUP_DATE    | A   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SETUP_METH    | A   | Text     | 100   | Text     | 100   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SETUP_DATE    | A   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| PFD_TF        | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| EROS_TF       | A   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WAVE_EFF      | A   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WAVE_ZIP      | A   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Coastal Gage Data

The S_Cst_Gage layer is required when gage information (from either
tide, wind, or buoy stations) is used in the determination or to support
flood height calculations. Specifically, this table is required in the
following situations: when tide gage information is used to support the
calibration and validation of hydrodynamic models; when tide gage
information is used in the determination of flood elevations by
statistical analyses of annual extrema; when buoy wave data provides
information regarding the wave climate in the study area; when buoy wave
data has been used in the estimation of offshore wave conditions; for
calibration and validation of a numerical wave model; and when data from
wind stations has been used for water level hindcasts or wave
estimation. Wave heights, wave period, and spectral parameters computed
during the study must be compared with observed data from wave buoys
whenever possible.

The S_Cst_Gage table contains information about coastal gages for the
study area. The spatial location of these gages may be some distance
from the areas for which coastal flood hazards were determined. A
spatial file with location information also corresponds with this data
table.

The spatial entities representing the coastal gages are points.

The S_Cst_Gage table contains the following elements.

GAGE_ID R Primary key for table lookup. Assigned by table creator.

CST_MDL_ID A Coastal Model Identification. This field is populated by a
linking element to the L_Cst_Model table. The L_Cst_Model table contains
detailed information about the coastal models that were used to
determine the coastal flood hazard for the area of each individual gage.
This ID field should contain a number that matches the CST_MDL_ID field
for a record in the L_Cst_Model. Multiple gages may link to a single
record in the L_Cst_Model table. This field is required for new coastal
studies.

GAGE_NM R Gage Name. This is the name of the gage assigned by the agency
maintaining the gage. This field can include information such as gage
station ID number, gage name, and location description.

AGENCY R Gage Agency. This is the name of the agency maintaining the
gage.

REC_INTVL A Recording Interval. This is the interval of time at which
the gage records data. This field is populated only if the coastal gage
is a fixed-interval gage.

TIME_UNIT A Recording Interval Time Unit. This field is populated only
if the coastal gage is a fixed-interval gage. Acceptable values for this
field are listed in the D_Time_Units table.

START_PD R Gage Record Starting Date. This is the date for the start of
the earliest period of record used in gage analysis.

START_TIME A Gage Record Starting Time. This is the time for the start
of the earliest period of record used in gage analysis. This value
should be formatted as hh:mm. This field is populated when the starting
time is available.

END_PD R Gage Record Ending Date. This is the date for the end of the
latest period of record used in gage analysis.

END_TIME A Gage Record Ending Date. This is the time for the end of the
latest period of record used in gage analysis. This value should be
formatted as hh:mm. This field is populated when the end time is
available

GAGE_TYPE R Gage Type. This value indicates the type of coastal gage.
Acceptable values for this field are listed in the D_Gage_Typ table.

V_DATUM R Vertical Datum. The vertical datum indicates the reference
surface from which the gage elevations are measured. Normally this would
be NAVD88 for new studies. Acceptable values for this field are listed
in the D_V_Datum table.

TIDE_TF R Record Tide Elevations. Does the gage record tide elevations?
Acceptable values for this field are listed in the D_TrueFalse table.

TIDE_EPOCH A Tidal Epoch. This field stores the date range for the tidal
epoch; for example, "1983-2001." This field is populated when the tide
gage information is available.

TIDE_ELEV A Observed Tide Elevation Time Series. This attribute stores
the name of the observed tidal elevation time series data file. The data
represent the total water levels recorded at tide gages used in the
coastal flood study. The file should be named \<DATE\>\_tideelev.zip,
where \<DATE\> is the date of the file creation. This field is populated
when observed tidal gage information is used as part of the study.

TIDE_PRED A Predicted Tide Time Series. This attribute stores the name
of the predicted tidal elevation time series data file. The data
represent the water levels predicted (the astronomic tide component) at
tide gages used in the coastal flood study. The file should be named
\<DATE\>\_tidepred.zip, where \<DATE\> is the date of the file creation.
This field is populated when tidal gage predictions differ from values
observed (as part of the TIDE_ELEV information).

TIDE\_ VBM R Tide Benchmark Vertical Marker. This is the NOAA, NGS or
community-assigned permanent benchmark identifier. The identifier must
be unique for each benchmark.

WVDIR_TF R Record Wave Direction. Does the gage record wave direction?
Acceptable values for this field are listed in the D_TrueFalse table.

WVSPEC_TF R Record Wave Spectra. Does the gage record wave spectra?
Acceptable values for this field are listed in the D_TrueFalse table.

WDSPD_TF R Record Wind Speed. Does the gage record wind speed?
Acceptable values for this field are listed in the D_TrueFalse table.

WDDIR_TF R Record Wind Direction. Does the gage record wind direction?
Acceptable values for this field are listed in the D_TrueFalse table.

WDSTN_HT A Wind Station Height. This is the height of the wind station
above ground elevation. This field is populated when wind gage data is
used in the study.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064194 .anchor}Table M.12-12. S_Cst_Gage
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| GAGE_ID       | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_MDL_ID    | A   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| GAGE_NM       | R   | Text     | 150   | Text     | 150   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| AGENCY        | R   | Text     | 150   | Text     | 150   |       |
+---------------+-----+----------+-------+----------+-------+-------+
| REC_INTVL     | A   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIME_UNIT     | A   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| START_PD      | R   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| START_TIME    | A   | Text     | 10    | Text     | 10    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| END_PD        | R   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| END_TIME      | A   | Text     | 10    | Text     | 10    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| GAGE_TYPE     | R   | Text     | 40    | Text     | 40    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIDE_TF       | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIDE_EPOCH    | A   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIDE_ELEV     | A   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIDE_PRED     | A   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| TIDE_VBM      | A   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WVDIR_TF      | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WVSPEC        | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WDSPD_TF      | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WDDIR_TF      | R   | Text     | 1     | Text     | 1     |       |
+---------------+-----+----------+-------+----------+-------+-------+
| WDSTN_HT      | A   | Long     | de    | Long     | de    |       |
|               |     | Integer  | fault | Integer  | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Shoreline

The S_Shore_Ln layer is required for all coastal studies. The S_Shore_Ln
spatial file contains information about the shoreline used in the
coastal flood hazard model. Typically, the S_Shore_Ln represents the
0.0-foot elevation contour. The spatial elements representing the
shorelines are lines. The file describes the shoreline profile setting
and must also include the reference to vertical datum.

The spatial entities representing the shoreline are lines.

The S_Shore_Ln table contains the following elements.

SHR_LN_ID R Primary key for table lookup. Assigned by table creator.

SHR_LN_TYP R Shoreline Type. This is the type of shoreline. This value
describes the criteria used in determining the shoreline in coastal
flood hazard models. Acceptable values for this field are listed in the
D_Shrln_Typ table.

BEACH_SET R Beach Setting. This field describes the local geomorphic
characteristics of the shore and backshore zone. Acceptable values for
this field are listed in the D_Beachset table. See Appendix D of these
Guidelines for additional information regarding beach setting.

V_DATUM R Vertical Datum. The vertical datum indicates the reference
surface from which the 0.0-foot contour is measured. Normally this would
be NAVD88. Acceptable values for this field are listed in the D_V_Datum
table.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064195 .anchor}Table M.12-13. S_Shore_Ln
Spatial File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SHR_LN_ID     | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SHR_LN_TYP    | R   | Text     | 35    | Text     | 35    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| BEACH_SET     | R   | Text     | 75    | Text     | 75    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| V_DATUM       | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### CBRS and Otherwise Protected Areas (OPAs)

The S_CBRS layer only applies to coastal areas that have specially
protected areas designated by Congress on John H. Chafee CBRS maps.
Authoritative CBRS boundary locations are shown on maps administered by
the U.S. Fish and Wildlife Service. Normally these areas are already
shown on existing FIRMs for the area. CBRS areas have restrictions on
Federal funding (including flood insurance coverage) after specified
dates for new or substantially improved structures. See Appendix K of
these Guidelines for more detailed information about CBRS areas.

The spatial entities representing the CBRS and OPA features are
polygons. There is a polygon for each CBRS unit.

The S_CBRS table contains the following elements.

CBRS_ID R Primary key for table lookup. Assigned by table creator.

CBRS_TYP R CBRS Type. The type code provides details of the types of
prohibitions that apply to the area. Normally this would be a CBRS area
or Otherwise Protected Area (OPA). Acceptable values for this field are
listed in the D_CBRS_Typ table.

CBRS_DATE R CBRS Date. Legislative or administrative date on which
prohibitions for the CBRS area apply. This should be indicated on the
FIRM with a note or with a fill pattern indicated on the legend.

CBRS_PHONE R CBRS Phone Number. This is the phone number for the contact
person/office for the CBRS legislative area. Enter the phone number as a
ten-digit numeric string with hyphens in the following format,
000-000-0000.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064196 .anchor}Table M.12-14. S_CBRS Spatial
File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CBRS_ID       | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CBRS_TYP      | R   | Text     | 35    | Text     | 35    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CBRS_DATE     | R   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CBRS_PHONE    | R   | Text     | 15    | Text     | 15    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Primary Frontal Dunes

The S_PFD_Ln layer is required when a primary frontal dune (PFD) is
present along portions or the entire coastline within the modeled
coastal floodplain. PFDs are not required to be continuous along the
length of the studied shoreline. The S_PFD_Ln spatial file contains
information about the PFD features for the coastal study area. PFDs are
not shown on the FIRM but are used in the coastal floodplain analysis.

The spatial entities representing the PFDs are lines. They are lines
that represent the landward dune heel or where the gradient changes from
steep to gentle.

The S_PFD_Ln table contains the following elements.

PFD_ID R Primary key for table lookup. Assigned by table creator.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064197 .anchor}Table M.12-15. S_PFD_Ln Spatial
File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| PFD_ID        | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Limit of Moderate Wave Action (LiMWA)

The S_LiMWA layer is required when a Limit of Moderate Wave Action
(LiMWA, previously described as Coastal A Zone) is delineated within the
coastal floodplain.

The spatial entities representing the LiMWA are lines. The line
represents the limit of 18-inch or greater waves in a Coastal AE Zone.

The S_LiMWA table contains the following elements.

LIMWA_ID R Primary key for table lookup. Assigned by table creator.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064198 .anchor}Table M.12-16. S_LIMWA Spatial
File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LIMWA_ID      | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

### Coastal Structures

The L_Cst_Struct table is required whenever coastal structures, such as
breakwaters, levees, or seawalls, affect local topography and flood
hazards. The L_Cst_Struct table contains information about the coastal
structures within the study area.

The L_Cst_Struct table contains the following elements:

CST_STR_ID R Primary key for table lookup. Assigned by table creator.

CERT_DOC A Certification Document. \<Filename.zip\> of the structure
certification documentation. This field is populated when the coastal
structure has been certified by a professional engineer or Federal
agency to remain intact during a 1-percent-annual-chance flood event.

CERT_STAT A Certification Status. This describes the type of
certification that the coastal structure possesses. This field is
populated for structures that protect up to the 1-percent-annual-chance
flood. Acceptable values for this field are listed in the D_Cert_Status
table.

LENGTH R Structure Length. This field stores the length of the coastal
structure.

LEN_UNIT R Length Units. This is the unit of measure for the structure
length. Acceptable values for the field are listed in the D_Length Units
table.

STRUCT_MTL R Structure Material. This describes the type of material of
which the structure is composed. Acceptable values for this field are
listed in the D_Struct_Mtl table.

SURVEY_DT A Survey Date. Date of the structure survey. This field is
populated when the structure is surveyed.

SURVEY_TM A Survey Time. Time of the structure survey. This value should
be formatted as hh:mm. This field is populated when the time of the
survey is available.

SOURCE_CIT R Source Citation. Abbreviation used in the metadata file
when describing the source information for the feature.

[]{#__RefHeading___Toc210064199 .anchor}Table M.12-17. L_Cst_Struct
Table File

+---------------+-----+----------+-------+----------+-------+-------+
| Field         | R/  | PGDB     |       | SHP      |       |       |
|               | A/O |          |       |          |       |       |
+---------------+-----+----------+-------+----------+-------+-------+
|               |     | Type     | L     | Type     | Le    | Scale |
|               |     |          | ength |          | ngth/ |       |
|               |     |          |       |          |       |       |
|               |     |          |       |          | Prec  |       |
|               |     |          |       |          | ision |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CST_STR_ID    | R   | Text     | 25    | Text     | 25    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CERT_DOC      | A   | Text     | 60    | Text     | 60    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| CERT_STAT     | R   | Text     | 50    | Text     | 50    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LENGTH        | R   | Double   | de    | Double   | de    | 2     |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| LEN_UNIT      | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| STRUCT_MTL    | R   | Text     | 20    | Text     | 20    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SURVEY_DT     | A   | Date     | de    | Date     | de    |       |
|               |     |          | fault |          | fault |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SURVEY_TM     | A   | Text     | 10    | Text     | 10    |       |
+---------------+-----+----------+-------+----------+-------+-------+
| SOURCE_CIT    | R   | Text     | 11    | Text     | 11    |       |
+---------------+-----+----------+-------+----------+-------+-------+

# Domain Tables

  ------------------- ----------------------- ------------------------ ---------------------------
                                                                       

  Domain Name                                 Value                    

                                                                       

  D_ANI_LID                                   Area Not Included In     
                                              Flood Insurance Study    

                                              T                        

                                              F                        

  D_Area_Units                                Type of Area Unit        

                                              SQUARE KILOMETERS        

                                              SQUARE MILES             

                                                                       

  D_BeachSet                                  Type of Beach Setting    

                                              Sandy beach backed by    
                                              low sand berm or high    
                                              sand dune formation      

                                              Sandy beach backed by    
                                              shore protection         
                                              structures               

                                              Cobble, gravel, shingle, 
                                              or mixed grain sized     
                                              beach and berms          

                                              Erodible coastal bluffs  

                                              Non-erodible coastal     
                                              cliffs and bluffs        

                                              Tidal flats and wetlands 

                                                                       

  D_CARTO_RQST                                Cartographic Request     

                                              BASE MAP UPDATE          

                                              INDEX PANEL ERRORS       

                                              MAP BODY (PANEL) ERRORS  

                                              FLOOD HAZARD FEATURE     
                                              SYMBOLIZATION AND NOTES  

                                              MAP COLLAR ISSUES        

                                                                       

  D_CBRS_Typ                                  Type of CBRS             

                                              COASTAL BARRIER          
                                              RESOURCES SYSTEM         

                                              OTHERWISE PROTECTED AREA 

                                                                       

  D_Cert_Status                               Type of Certification    
                                              Status                   

                                              Meets existing FEMA      
                                              ACCREDITATION policy     

                                              Certified prior to       
                                              existing FEMA policy     

                                              Certified by another     
                                              Federal Agency           

                                              Not certified: Failure   
                                              of vertical structure    

                                              Not certified: Failure   
                                              of revetment             

                                              Not certified: Failure   
                                              of levee                 

                                              Not Applicable           

                                                                       

  D_Coastal_Mdl                               Type of Coastal Model    
                                              (see accepted models     
                                              list on FEMA's Web site) 

                                              ACES 1.07                

                                              Advanced Circulation     
                                              Model (ADCIRC) 2DDI      
                                              (2003)                   

                                              CHAMP 2.0 (April 2007)   

                                              Delft 3D (FLOW, WAVE,    
                                              MOR)                     

                                              DYNLET                   

                                              FEMA Surge (1988)        

                                              MIKE 21 (HD/NHD) 2002 D, 
                                              2004, 2005, and 2007     

                                              MIKE 21 Flexible Mesh    
                                              Spectral Wave Model (FM  
                                              SW) 2004, 2005, and 2007 

                                              MIKE 21 Nearshore        
                                              Spectral Wave Model      
                                              (NSW) 2002D, 2005, and   
                                              2007                     

                                              RCPWAVE (1986)           

                                              RUNUP 2.0                

                                              Simulating Waves         
                                              Nearshore (SWAN), Cycle  
                                              III Version 40.51        

                                              TABS RMA2 v.4.3 (Oct     
                                              1996)                    

                                              WHAFIS 3.0 (1988) and    
                                              4.0 (2007)               

                                              WHAFIS 3.0 GL (1988)     

                                                                       

  D_Cst_Struct                                Type of Coastal          
                                              Structure Classification 

                                              BEACH STABILIZATION      
                                              STRUCTURES               

                                              COASTAL ARMORING         
                                              STRUCTURES               

                                              MISCELLANEOUS STRUCTURES 

                                                                       

  D_Cst_Typ                                   Type of Coastline        

                                              Open Coast               

                                              Sheltered Waters         

                                              Combined Open Coast and  
                                              Sheltered Waters         

                                                                       

  D_Discharge_Units                           Type of Discharge Unit   

                                              CFS                      

                                              CMS                      

                                                                       

  D_ELEMENT                                   Element Yes/No           

                                              Yes                      

                                              No                       

                                                                       

  D_Erosion                                   Type of Erosion          

                                              MK-A                     

                                              K-D                      

                                              SBEACH                   

                                              EBEACH                   

                                              COSMOS                   

                                              Dune Removal             

                                              Dune Retreat             

                                              None Applied             

                                              Other                    

                                                                       

                                                                       

  D_FBS_TF                                    Floodplain Boundary      
                                              Standard                 

                                              T                        

                                              F                        

                                                                       

  D_FLD_DATA_RQST                             Flood Data Request       

                                              CHANGES TO HYDROLOGIC    
                                              CONDITION                

                                              CHANGES TO HYDRAULIC     
                                              CONDITION                

                                              FLOODPLAIN DELINEATION   
                                              ERRORS                   

                                              FLOODWAY DELINATION      
                                              ERRORS                   

                                              SFHA LABELING ERRORS     

                                              BFE ERRORS               

                                              CROSS SECTION ERRORS     

                                              LIMIT OF STUDY ERRORS    

                                              COASTAL GUTTER ERRORS    

                                              CBRS BOUNDARY ERRORS     

                                              ANY LABELIN OUTSIDE      
                                              COUNTY BOUNDARY          

                                              HIGH WATER FROM RECENT   
                                              FLOOD                    

                                              IMPACTED STRUCTURES      

                                              COMMUNITY MODEL OR DATA  

                                              POPULATION CHANGE OR     
                                              GROWTH IN FLOODPLAIN     

                                                                       

  D_FLOOD_TYP                                 Flooding Type            

                                              RIVER                    

                                              COASTAL                  

                                              ALLUVIAL                 

                                              LACUSTRINE               

                                              PONDING                  

                                                                       

  D_Floodway                                  Type of Floodway         

                                              ADMINISTRATIVE FLOODWAY  

                                              AREA OF SPECIAL          
                                              CONSIDERATION            

                                              COMMUNITY ENCROACHMENT   
                                              AREA                     

                                              COLORADO RIVER           

                                              DENSITY FRINGE AREA      

                                              FLOODWAY                 

                                              FLOODWAY CONTAINED IN    
                                              CHANNEL                  

                                              FLOWAGE EASEMENT         
                                              BOUNDARY                 

                                              STATE ENCROACHMENT       

                                                                       

  D_Gage_Typ                                  Type of Gage             

                                              FIXED INTERVAL           

                                              FLOW                     

                                              FLOW / STAGE             

                                              INSTANTANEOUS            

                                              STAGE                    

                                              TIDE                     

                                              WAVE HEIGHT              

                                              WAVE HEIGHT AND          
                                              DIRECTION                

                                              WIND DIRECTION           

                                              WIND SPEED               

                                              WIND SPEED AND DIRECTION 

                                                                       

  D_HAZUS_LVL                                 Hazus Level              

                                              Level 1                  

                                              Level 2                  

                                              Level 3                  

                                                                       

  D_Hydra_Mdl         Type of Hydraulic Model                          
                      (see accepted models                             
                      list on FEMA's Web                               
                      site)                                            

                      ADVANCED ICPR 2.20                               
                      (OCTOBER 2000) and 3.02                          
                      (November 2002)                                  

                      CHAN for Windows v.                              
                      2.03 (1997)                                      

                      Culvert Master v. 2.0                            
                      (September 2002) and up                          

                      DHM 21 and 34 (AUGUST                            
                      1987)                                            

                      FEQ 8.92 (1999) and FEQ                          
                      9.98 (2005)                                      

                      FEQUTL 4.68 (1999) and                           
                      FEQUTL 5.46 (2005)                               

                      FESWMS 2DH 1.1 and up                            
                      (JUNE 1995)                                      

                      FLDWAV (NOVEMBER 1998)                           

                      FLO-2D V.2003.6,                                 
                      2004.10 and 2006.1                               

                      GAGE ANALYSIS                                    

                      HCSWMM 4.31B (AUGUST                             
                      2000)                                            

                      HEC-2 4.6.2 (MAY 1991)                           

                      HEC-RAS 3.1.1 and up                             

                      HY8 4.1 (November 1992)                          
                      and up                                           

                      MIKE 11 HD (2002 D,                              
                      2004)                                            

                      MIKE Flood HD (2002 D                            
                      and 2004)                                        

                      NETWORK (June 2002)                              

                      PondPack v. 8 (May                               
                      2002) and up                                     

                      QUICK-2 1.0 (January                             
                      1995) and up                                     

                      S2DMM (February 2005)                            

                      StormCAD v.4 (June                               
                      2002) and up                                     

                      SWMM 4.30 (MAY 1994)                             

                      SWMM 4.31 (JANUARY                               
                      1997)                                            

                      SWMM 5 Version 5.0.005                           
                      (May 2005) and up                                

                      TABS-RMA2 V.4.3                                  
                      (OCTOBER 1996)                                   

                      TABS-RMA4 V.4.5 (JULY                            
                      2000)                                            

                      WSPGW 12.96 (OCTOBER                             
                      2000)                                            

                      WSPRO (JUNE 1988) and                            
                      up                                               

                      XP-SWMM 8.52 and up                              

                      Xpstorm 10.0 (May 2006)                          

                                                                       

  D_Hydro_Mdl         Type of Hydrologic                               
                      Model (see accepted                              
                      models list on FEMA's                            
                      Web site)                                        

                      AHYMO 97 (AUGUST 1997)                           

                      CUHPF/PC (MAY 1996 and                           
                      May 2002)                                        

                      FAN                                              

                      HEC-FFA 3.1 (February                            
                      3.1)                                             

                      HEC-1 4.0.1 (May 1991)                           
                      and up                                           

                      HEC-HMS 1.1 (March                               
                      1998) and up                                     

                      HSPF 10.10 (December                             
                      1993) and up                                     

                      MIKE 11 RR (2002 D and                           
                      2004)                                            

                      MIKE 11 UHM (2002 D and                          
                      2004)                                            

                      PEAKFQ 2.4 (APRIL 1998)                          
                      and up                                           

                      PondPack v.8 (May 2002)                          
                      and up                                           

                      PRMS Version 2.1                                 
                      (January 1996)                                   

                      REGRESSION EQUATIONS                             

                      SWMM (RUNOFF) 4.30 (MAY                          
                      1994)                                            

                      SWMM (RUNOFF) 4.31                               
                      (JANUARY 1997)                                   

                      SWMM 5 Version 5.0.005                           
                      (May 2005) and up                                

                      TR-20 (FEBRUARY 1992)                            

                      TR-20 Win 1.00.002                               
                      (January 2005)                                   

                      TR-55 (JUNE 1986)                                

                      Win TR-55 1.0.08                                 
                      (January 2005)                                   

                      XP-SWMM 8.52 and up                              

                      Xpstorm 10.0 (May 2006)                          

                                                                       

  D_Len_Units         Type of Length Unit                              

                      CENTIMETERS                                      

                      FEET                                             

                      INCHES                                           

                      KILOMETERS                                       

                      METERS                                           

                      MILES                                            

                      MILLIMETERS                                      

                                                                       

  D_Method            Type of Elevation                                
                      Source Method                                    

                      COMBO OF TOPO AND                                
                      SURVEY                                           

                      CUT FROM TOPO                                    

                      DIGITIZED FROM FIRM                              

                      FIELD SURVEY                                     

                                                                       

  D_MTHOD_TYPE        Method Type                                      

                      NEW                                              

                      UPDATED                                          

                      REDELINEATION                                    

                                                                       

  D_NEED_CAT           Need Category                                   

                      VALIDATED                                        

                      UNMET NEED                                       

                                                                       

  D_Node_Typ          Type of Node                                     

                      DIVERSION                                        

                      JUNCTION                                         

                      OUTLET                                           

                      STRUCTURE                                        

  D_RQST_CAT          Request Category                                 

                      CARTOGRAPHIC                                     

                      FLOOD DATA                                       

                                                                       

  D_RQST_LVL          Level Of Request                                 

                      DETAILED WITHOUT                                 
                      FLOODWAY                                         

                      DETAILED WITH FLOODWAY                           

                      APPROXIMATE                                      

                      LIMITED DETAIL                                   

                      NA                                               

                                                                       

  D_RQSTR_TYPE        Requester Type                                   

                      OFA                                              

                      HOME OWNER                                       

                      COMMUNITY                                        

                      MAPPING PARTNER                                  

                      FEMA                                             

                                                                       

  D_Runup_Mdl         Type of Runup Model                              

                      ACES 1.07 (1992)                                 

                      CHAMP (2.0) (2007)                               

                      EROSION (1998)                                   

                      TAW                                              

                      RUNUP 2.0 (1990)                                 

                                                                       

  D_Shrln_Typ         Type of Shoreline                                

                      ZERO FOOT CONTOUR FIELD                          
                      SURVEY                                           

                      ZERO FOOT CONTOUR LIDAR                          
                      / SHOALS                                         

                                                                       

  D_Struct_Mtl        Type of Structure                                
                      Material                                         

                      Stone                                            

                      Asphalt                                          

                      Concrete                                         

                      Earthen                                          

                      Timber                                           

                      Steel                                            

                      Sand                                             

                      Other                                            

                      Unknown                                          

                                                                       

  D_Struct_Typ        Type of Structure                                

                      AQUEDUCT                                         

                      BEACH STABILIZATION                              
                      STRUCTURE                                        

                      BRIDGE                                           

                      CANAL                                            

                      CHANNEL                                          

                      CHANNEL CONTAINS                                 
                      0.2-PCT FLOOD EVENT                              

                      CHANNEL CONTAINS 1-PCT                           
                      FLOOD EVENT                                      

                      COASTAL ARMORING                                 
                      STRUCTURE                                        

                      CONTROL STRUCTURE                                

                      CULVERT                                          

                      CULVERT CONTAINS                                 
                      0.2-PCT FLOOD EVENT                              

                      CULVERT CONTAINS 1-PCT                           
                      FLOOD EVENT                                      

                      DAM                                              

                      DIKE                                             

                      DOCK                                             

                      DROP STRUCTURE                                   

                      ENERGY DISSIPATER                                

                      FISH LADDER                                      

                      FLOODWAY CONTAINED IN                            
                      CHANNEL                                          

                      FLOODWAY CONTAINED IN                            
                      CULVERT                                          

                      FLUME                                            

                      FOOTBRIDGE                                       

                      GATE                                             

                      JETTY                                            

                      LEVEE                                            

                      LOCK                                             

                      OTHER / MISC STRUCTURE                           

                      PENSTOCK                                         

                      PIER                                             

                      PIPELINE                                         

                      PUMP STATION                                     

                      RETAINING WALL                                   

                      SEAWALL                                          

                      SIDE WEIR STRUCTURE                              

                      SIPHON                                           

                      STORM SEWER                                      

                      STORM SEWER CONTAINS                             
                      1-PCT FLOOD                                      

                      UTILITY CROSSING                                 

                      WEIR                                             

                      WING WALL                                        

                                                                       

  D_Study_Typ         Type of Study                                    

                      Approximate                                      

                      Limited Detailed                                 

                      Detailed                                         

                      Redelineation                                    

                      Digital Conversion                               

                      DETAIL-FLOODWAY                                  

                                                                       

  D_Surge_Mdl         Type of Surge Model                              

                      DYNLET                                           

                      FEMA SURGE (1988)                                

                      FLOW2D (1975)                                    

                      MIKE 21 HD/NHD                                   

                      NEW ENGLAND TIDE                                 
                      PROFILE                                          

                      NORTHEASTER MODEL                                
                      (1978)                                           

                      ODISTIM (1975)                                   

                      TABS RMA V.4.3 (OCTOBER                          
                      1996)                                            

                      USACE GREAT LAKES TIDE                           
                      PROFILE (1998)                                   

                      ADCIRC (2003)                                    

  D_Surge_Runoff      Type of Surge Runoff                             

                      Independent                                      

                      Correlation                                      

                      Other                                            

                                                                       

  D_Surge_Tide        Type of Surge Tide                               

                      Linear combination                               

                      High/low                                         

                      EST approach                                     

                      1-D Monte Carlo                                  
                      approach                                         

                      2-D surge modeling                               

                                                                       

  D_Time_Units        Type of Time Unit                                

                      DAYS                                             

                      HOURS                                            

                      MINUTES                                          

                      MONTHS                                           

                      SECONDS                                          

                      WEEKS                                            

                      YEARS                                            

                                                                       

  D_TrueFalse         True, False, Unknown                             

                      T                                                

                      F                                                

                      U                                                

                                                                       

  D_V_Datum           Type of Vertical Datum                           

                      LOCAL TIDAL DATUM                                

                      MLLW                                             

                      MLW                                              

                      MSL                                              

                      NAVD88                                           

                      NGVD29                                           

                                                                       

  D_Velocity_Units    Type of Velocity Unit                            

                      CENTIMETERS / DAY                                

                      CENTIMETERS / HOUR                               

                      FEET / SECOND                                    

                      INCHES / DAY                                     

                      INCHES / HOUR                                    

                      METERS / SECOND                                  

                      MICROMETERS / SECOND                             

                      MILLIMETERS / DAY                                

                      MILLIMETERS / HOUR                               

                                                                       

  D_VZone             Type of V Zone                                   

                      30 FOOT SPLASH ZONE                              
                      BEHIND STRUCTURE                                 

                      PFD                                              

                      RUNUP EXTENT                                     

                      WHAFIS                                           

                                                                       

  D_Water_Typ         Type of Water Feature                            

                      PROFILE BASELINE                                 

                      PROFILE BASELINE AND                             
                      STREAM CENTERLINE                                

                                                                       

                                                                       

  D_Wave_Mdl          Type of Wave Model                               

                      MIKE 21 (OSW)                                    

                      MIKE 21 (NSW)                                    

                      RCPWAVE (1986)                                   

                      WHAFIS 3.0 (1988)                                

                      WHAFIS 3.0 GL (1983)                             

                                                                       

                      WHAFIS 4.0 (2007)                                

                      SWAN (2008)                                      

  D_Zone              Type of Flood Zone                               

                      A                                                

                      AE                                               

                      AH                                               

                      AO                                               

                      AR                                               

                      1-PCT-ANNUAL-CHANCE                              
                      FLOOD HAZARD CONTAINED                           
                      IN CHANNEL                                       

                      1-PCT FUTURE CONDITIONS                          

                      A99                                              

                      V                                                

                      VE                                               

                      0.2-PCT-ANNUAL-CHANCE                            
                      FLOOD HAZARD                                     

                      0.2-PCT-ANNUAL-CHANCE                            
                      FLOOD HAZARD CONTAINED                           
                      IN CHANNEL                                       

                      AREA NOT INCLUDED                                

                      D                                                

                      X PROTECTED BY LEVEE                             

                      X                                                

                      X AREA OF SPECIAL                                
                      CONSIDERATION                                    

                      OPEN WATER                                       

                                                                       

                                                                       
  ------------------- ----------------------- ------------------------ ---------------------------

# References  {#references .unnumbered}

Federal Geographic Data Committee, FGDC-STD-001-1998. *Content Standard
for Digital Geospatial Metadata (version 2.0),* FGDC, c/o USGS, Reston,
VA\
<http://www.fgdc.gov/metadata/metadata.html>

U.S. Department of the Army, Corps of Engineers, Hydrologic Engineering
Center, *HEC-1 Flood Hydrograph Package, User's Manual*[,]{.underline}
Davis, CA, 1990.

U.S. Department of the Army, Corps of Engineers, Hydrologic Engineering
Center, *HEC-RAS, River Analysis System, User's Manual*[,]{.underline}
Version 3.0, Davis, CA, 2001.

U.S. Department of the Army, Corps of Engineers, Hydrologic Engineering
Center, *Hydrologic Modeling System, HEC-HMS, User's
Manual*[,]{.underline} Version 2.1, Davis, CA, 2001.

Federal Emergency Management Agency, 1990, FAN -- *An Alluvial Fan
Flooding Computer Program, User's Manual and Program Disk:* available
from Michael Baker, Jr., Alexandria, Virginia.

Federal Emergency Management Agency, 2007, *Floodplain Boundary Standard
Audit Procedures -- Version 2.0:* available on FEMA's Web site
http://www.fema.gov/plan/prevent/fhm/gs_main.shtm

Federal Emergency Management Agency, 2007, *Draft Scoping Guidelines:*
available from Michael Baker, Jr., Alexandria, Virginia.