Appendix L - Federal Emergency Management Agency

More documents

Recommendations

Info

<strong>Appendix</strong> LTable: S_Pol_Ar [October 2011]Field R/A TypeLength/PrecisionScale(SHP Only)Joined Spatial /Lookup Tables orDomainsDFIRM_ID R Text 6 N/AVERSION_ID R Text 11 N/APOL_AR_ID R Text 25 N/APOL_NAME1 R Text 50 N/APOL_NAME2 A Text 50 N/APOL_NAME3 A Text 50 N/ACO_FIPS R Text 3 N/AST_FIPS R Text 2 D_STATE_FIPSCOMM_NO R Text 4 N/ACID R Text 6 L_POL_FHBMANI_TF R Text 1 D_TRUEFALSEANI_FIRM A Text 6 N/ACOM_NFO_ID A Text 25 L_COMM_INFOSOURCE_CIT R Text 11 L_SOURCE_CITGuidelines and Standards forFlood Risk Analysis and Mapping Page L-82 Section L.8 Requirements for FIRM Databases
<strong>Appendix</strong> LL.8.24 Table: S_Profil_Basln [October 2011]The S_Profil_Basln layer is required for all types of riverine hydraulic analyses. Profile baselines arerequired to be shown on FIRM panels for all valid studies with profiles or otherwise established BaseFlood Elevations. At the discretion of the FEMA Project Officer water lines may be shown on vectormaps to represent the bank or stream centerline location. When a profile baseline and water lines areavailable for the same stream reach, only the profile baseline shall be shown on the FIRM in order toeliminate overlaps. A profile baseline is also required when a flood risk project is not being updated, butthe effective profile baseline still accurately represents conditions on the ground.The profile baseline shows the path of flood flows on the FIRM and is an accurate representation of thedistance between cross sections, structures, nodes, or grids in the hydraulic model. If the flood flow pathfollows the main channel of the stream, then the profile baseline and stream centerline will match, butonly the profile baseline should be shown on the FIRM. The profile baseline is used for replicating thestationing and water-surface elevations found in the FIS report profiles, but in GIS format. Thisinformation is used in the following tables within the FIS report: Flooding Sources Included in this FISreport, Principal Flood Problems, Summary of Hydrologic and Hydraulic Analyses, Summary ofTopographic Elevation Data Used in Mapping, the Stream-by_Stream Vertical Datum Conversion, andSummary of Contracted Studies Included in this FIS Report.The spatial entities representing the profile baseline are lines. Profile baselines are to be stored inPolyline ZM feature classes, storing both profile station values (M-values) and 1-percent-annual-chancewater-surface elevations (Z-values) at cross sections, structures, and other modeled inflection points. Fornew models and effective models with valid profile baselines, vertices along the profile baseline are to becalibrated between cross sections and structures using linear referencing / dynamic segmentation tools inGIS. The first vertex of each profile baseline will be the downstream most point on the profile.This table stores Principal Flood Problem and Special Consideration data for use in the FIS text. Due tothe limitations in the Esri Shapefile DBF format, text fields are limited in size. Several fields have beenprovided, but in the event that the description of principal flood problems or special considerationsexceeds the number of characters provided, a tab separated value text file may be submitted instead. Thefirst row of the text file must include a header as follows:WTR_NM FLD_PROB SPEC_CON Each row after the header would have the name of the studied reach/stream followed by a tab, theprincipal flood problem text followed by a tab, and special considerations for that reach, followed by acarriage return.When required, principal flood problem and special consideration files will be named using the followingconvention: _FIS_Fld_Problems_Spec_Considerations.txtGuidelines and Standards forFlood Risk Analysis and Mapping Page L-83 Section L.8 Requirements for FIRM Databases
Page 1 and 2:
Guidelines and Standards for FloodR
Page 3 and 4:
Appendix LDate Affected Section(s)
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Appendix LTable of ContentsL.1. Flo
Page 19 and 20:
Appendix LL.8.17 Table: S_Levee [Oc
Page 21 and 22:
Appendix LAppendix LDigital Data an
Page 23:
Appendix LFIRM Table NameTableTypeT
Page 26 and 27:
Appendix LTable L-2. Mapping Partne
Page 28 and 29:
Appendix LFIR M Table NameAcquireB
Page 30:
Appendix LAppendix are identified i
Page 33 and 34:
Appendix Lfiles for lookup tables.
Page 35 and 36:
Appendix LWhen possible, tables req
Page 37 and 38:
Appendix L• Area spatial features
Page 39 and 40:
Appendix LTopologyFilename(*_TOPOLO
Page 41 and 42:
Appendix LIn the FIRM Database, flo
Page 43 and 44:
Appendix Lfield length indicates th
Page 45 and 46:
Appendix LL.4.8 Deliverables [Octob
Page 47 and 48: Appendix LL.5. Database Table Struc
Page 49 and 50: Appendix LL.7. Metadata Example for
Page 51 and 52: Appendix LFAN_VEL_MX A Alluvial Fan
Page 53 and 54: Appendix LTable: S_Base_Index [Octo
Page 55 and 56: Appendix Lboundary. Each BFE is rep
Page 57 and 58: Appendix LTable: S_CBRS [October 20
Page 59 and 60: Appendix LTIME_UNIT A Recording Int
Page 61 and 62: Appendix LL.8.6 Table: S_Cst_Tsct_L
Page 63 and 64: Appendix LCON_PD A Controlling Wave
Page 65 and 66: Appendix LTable: S_Cst_Tsct_Ln [Oct
Page 67 and 68: Appendix LL.8.7 Table: S_Datum_Conv
Page 69 and 70: Appendix LL.8.8 Table: S_FIRM_Pan [
Page 71 and 72: Appendix LL.8.9 Table: S_Fld_Haz_Ar
Page 73 and 74: Appendix LTable: S_Fld_Haz_Ar [Octo
Page 75 and 76: Appendix LL.8.11 Table: S_Gage [Oct
Page 77 and 78: Appendix LL.8.12 Table: S_Gen_Struc
Page 79 and 80: Appendix LL.8.13 Table: S_HWM [Octo
Page 81 and 82: Appendix LL.8.14 Table: S_Hydro_Rea
Page 83 and 84: Appendix LL.8.16 Table: S_Label_Pt
Page 85 and 86: Appendix LL.8.17 Table: S_Levee [Oc
Page 87 and 88: Appendix LTable: S_Levee [October 2
Page 89 and 90: Appendix LL.8.19 Table: S_LOMR [Oct
Page 91 and 92: Appendix LL.8.20 Table: S_Nodes [Oc
Page 93 and 94: Appendix LL.8.21 Table: S_PFD_Ln [O
Page 95 and 96: Appendix LTable: S_PLSS_Ar [October
Page 97: Appendix LST_FIPS R State FIPS. Thi
Page 101 and 102: Appendix LFLD_PROB3 A Description o
Page 103 and 104: Appendix LL.8.26 Table: S_Stn_Start
Page 105 and 106: Appendix LL.8.27 Table: S_Subbasins
Page 107 and 108: Appendix LL.8.28 Table: S_Submittal
Page 109 and 110: Appendix LField R/A TypeTable: S_Su
Page 111 and 112: Appendix LTable: S_Trnsport_Ln [Oct
Page 113 and 114: Appendix LField R/A TypeTable: S_Ts
Page 115 and 116: Appendix LTable: S_Wtr_Ar [October
Page 117 and 118: Appendix LTable: S_Wtr_Ln [October
Page 119 and 120: Appendix LXS_LTR A Cross Section Le
Page 121 and 122: Appendix LL.8.34 Table: S_Zone_AR [
Page 123 and 124: Appendix LH_DATUM R Horizontal Datu
Page 125 and 126: Appendix LField R/A TypeTable: Stud
Page 127 and 128: Appendix LIN_ID_DAT R Initial Ident
Page 129 and 130: Appendix LL.8.37 Table: L_Comm_Revi
Page 131 and 132: Appendix LSTRM_PRM A Storm Paramete
Page 133 and 134: Appendix LTable: L_Cst_Model [Octob
Page 135 and 136: Appendix LField R/A TypeTable: L_Cs
Page 137 and 138: Appendix LL.8.41 Table: L_ManningsN
Page 139 and 140: Appendix LL.8.43 Table: L_MT2_LOMR
Page 141 and 142: Appendix LL.8.44 Table: L_Mtg_POC [
Page 143 and 144: Appendix LL.8.45 Table: L_Pan_Revis
Page 145 and 146: Appendix LL.8.46 Table: L_Pol_FHBM
Page 147 and 148: Appendix LL.8.48 Table: L_Profil_La
Page 149 and 150:
Appendix LL.8.49 Table: L_Source_Ci
Page 151 and 152:
Appendix LL.8.50 Table: L_Summary_D
Page 153 and 154:
Appendix LL.8.51 Table: L_Summary_E
Page 155 and 156:
Appendix LL.8.52 Table: L_XS_Elev [
Page 157 and 158:
Appendix LWSEL_FLDWY A Base Flood W
Page 159 and 160:
Appendix LField R/A TypeTable: L_XS
Page 161 and 162:
Appendix LV_DATUM R Vertical Datum.
Page 163:
Appendix LL.10. Domain Tables [Octo
show all

Appendix L - Federal Emergency Management Agency

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

Delete template?

Save as template?