Appendix L - Federal Emergency Management Agency

More documents

Recommendations

Info

<strong>Appendix</strong> LField R/A TypeTable: L_Source_Cit [October 2011]Length/PrecisionScale(SHP Only)Joined Spatial /Lookup Tables orDomainsDFIRM_ID R Text 6 N/AVERSION_ID R Text 11 N/ASOURCE_CIT R Text 11 All Spatial TablesCITATION A Text 25 N/APUBLISHER R Text 254 N/ATITLE R Text 254 N/AAUTHOR A Text 254 N/APUB_PLACE A Text 100 N/APUB_DATE R Text 30 N/AWEBLINK A Text 128 N/ASRC_SCALE A Text 12 N/AMEDIA R Text 50 N/AGuidelines and Standards forFlood Risk Analysis and Mapping Page L-134 Section L.8 Requirements for FIRM Databases
<strong>Appendix</strong> LL.8.50 Table: L_Summary_Discharges [October 2011]The L_Summary_Discharges table is required when a Summary of Discharges table is to be included inthe FIS report. This table stores the hydrologic information, including drainage area and peak discharges,associated with the node. This table contains information used in the Summary of Discharges table in theFIS report.The nodes to be included in the Summary of Discharges table should be at or near major road or streetcrossings, upstream and downstream of major tributaries (where base flood discharge changes by at least25-percent), at diversions of flow from the channel, at or near gaging stations, at corporate or countyboundaries, and at major flood control structures. In the absence of these locations, nodes should beincluded in the Summary of Discharges table when there is an approximately 25-percent change in thebase flood discharge.The L_Summary_Discharges table contains the following elements.DFIRM_ID R Flood Risk Project Identifier. For a single-jurisdiction flood risk project,the value is composed of the two-digit State FIPS code and the four-digitFEMA CID code (e.g., 480001). For a countywide flood risk project,the value is composed of the two-digit State FIPS code, the three-digitcounty FIPS code, and the letter “C” (e.g., 48107C). Within each FIRMDatabase, the DFIRM_ID value will be identical.VERSION_ID R Version Identifier. Identifies the product version and relates the featureto standards according to how it was created.SUMDSCH_ID R Primary key for table lookup. Assigned by table creatorNODE_ID R Node Identification. This is the foreign key to the S_Nodes table. Thenode is associated with the subbasin. This field is populated to showwhether or not the discharge is to be included in the Summary ofDischarges table in the FIS report.NODE_DESC R Node Location Description. This describes the location of the node.This name must match what is used in the model and will be shown inthe Summary of Discharges Table in the FIS report text. It must beunique across a watershed. Examples of this value include“Downstream of State Route 234,” “At the confluence of Hillton Run,”and “Approximately 1.08 miles upstream of confluence with McIntoshRun.”DRAIN_AREA R Drainage Area. This is the contributing drainage area. For alluvial fanstudies, this is the “above the apex” value.AREA_UNIT R Area Units. This unit indicates the measurement system used for thedrainage area. Normally, this would be square miles. Acceptable valuesfor this field are listed in the D_Area_Units table.EVENT_TYP R Flood Event. Identifies the annual percentage of the chance ofexceedance for a flooding event, such as 0.2-, 1-, 2-, 4, and 10-percent.Acceptable values for this field are listed in the D_Event table.DISCH R Discharge. Existing conditions discharge at the node for the flood eventdescribed in the EVENT_TYP field. This is the cumulative dischargebased on the total drainage above the node.Guidelines and Standards forFlood Risk Analysis and Mapping Page L-135 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 and 98:
Appendix LST_FIPS R State FIPS. Thi
Page 99 and 100: Appendix LL.8.24 Table: S_Profil_Ba
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: Appendix LL.8.49 Table: L_Source_Ci
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?