Appendix L - Federal Emergency Management Agency

More documents

Recommendations

Info

Appendix LL.8.36 Table: L_Comm_Info [October 2011]This table is required for all Preliminary or Final FIRM Databases.The L_Comm_Info table is a lookup table that contains community map repository details and maphistory information that is shown in the Listing of NFIP Jurisdictions, Map Repositories, and CommunityMeetings tables in the FIS report. This table will include any community that has a CID; even if it isconsidered non-floodprone or non-participating. Communities that do not have a CID issued by FEMA,or are not included within the area of the data submittal, will not appear in this table. The “not populated”values that are described in Section L.4.6.12 may be used to fill in some of the required fields whennecessary. There is normally one record in this table for each community mapped on the FIRM.The L_Comm_Info table contains the following elements.DFIRM_ID R Flood Risk Project Identifier. For a single-jurisdiction flood risk project, thevalue is composed of the two-digit State FIPS code and the four-digit FEMACID code (e.g., 480001). For a countywide flood risk project, the value iscomposed of the two-digit State FIPS code, the three-digit county FIPScode, and the letter “C” (e.g., 48107C). Within each FIRM Database, theDFIRM_ID value will be identical.VERSION_ID R Version Identifier. Identifies the product version and relates the feature tostandards according to how it was created.COM_NFO_ID R Primary key for table lookup. Values in this field must match the values inthe COM_NFO_ID field of the S_Pol_Ar table.REPOS_ADR1 R Repository Street Address 1. First line of the mailing or street address forthe map repository. The map repository is the office the community hasdesignated as responsible for maintaining copies of all the flood hazardinformation FEMA publishes for the community. The public may viewcopies of the current effective information at the map repository. Forexample, this line might read ‘Division of Community and EconomicDevelopment.’REPOS_ADR2 A Repository Street Address 2. Second line of the mailing or street address forthe map repository. For example, this line might read ‘226 W. FourthStreet.’ This field is applicable if the map repository address requires morethan one line.REPOS_ADR3 A Repository Street Address 3. Third line of the mailing or street address forthe map repository. For example, this line might read ‘Suite 200.’ This fieldis applicable if address requires additional space.REPOS_CITY R Repository City. City portion of the mailing or street address for the maprepository. For example, this line might read ‘Springfield.’REPOS_ST R Repository State. State portion of the mailing or street address for the maprepository. The full name of the State should be provided. For example, thisline might read ‘ILLINOIS.’ This field is used to populate the FIS ReportMap Repositories table. Acceptable values for this field are listed in theD_State_Name table.REPOS_ZIP R Repository Zip code. ZIP code portion of the mailing or street address forthe map repository. This information is also displayed in the FIRM legendor index. For example, this line might read ‘62269.’ This field is used topopulate the FIS Report Map Repositories table.Guidelines and Standards forFlood Risk Analysis and Mapping Page L-110 Section L.8 Requirements for FIRM Databases
Appendix LIN_ID_DAT R Initial Identification Date. This is the initial identification date for thecommunity as shown on the FIRM legend, index, or FIS report. Thisinformation can also be obtained from FEMA. See Appendix J of theseGuidelines and Procedure Memorandum No. 66 for more detailedinformation about map dates.IN_NFIP_DT R Initial NFIP Date. This is the initial date of the first NFIP map published byFEMA for this community. This can be obtained from the FIRM legend,index, or FIS report. This information can also be obtained from FEMA.See Appendix J of these Guidelines and Procedure Memorandum No. 66 formore detailed information about map dates.IN_FHBM_DT R Initial FHBM Date. This is the initial date of first Flood Hazard BoundaryMap published for this community.IN_FRM_DAT R Initial FIRM Date. This is the date of the initial FIRM created for thiscommunity. This can be obtained from the FIRM legend, index, or FISreport. This information can also be obtained from FEMA. See Appendix Jof these Guidelines and Procedure Memorandum No. 66 for more detailedinformation about map dates.FST_CW_EFF R Initial Countywide Effective Date. This is the effective date of the firstcountywide FIRM for this community. This date will be displayed on theFIRM panel under the heading EFFECTIVE DATE OF COUNTYWIDEFLOOD INSURANCE RATE MAP.FST_CW_FIS R Initial Countywide Effective Flood Insurance Study Date. This is theeffective date of the first countywide FIS for this community. This date willgenerally be the same as the first countywide FIRM for this community,except where an FIS was not published with the first countywide FIRM.RECENT_DAT A Most Recent Panel Date. This can be obtained from the FIRM Index or theFEMA Community Status book at www.msc.fema.gov. This field is onlypopulated for Final FIRM Databases. See Appendix J of these Guidelinesand Procedure Memorandum No. 66 for more detailed information aboutmap dates.REVISIONS R Revisions. This indicates whether the community has had map revisions. Ifthere are map revisions for this community, enter true. Acceptable valuesfor this field are listed in the D_TrueFalse table.MULTICO_TF R Multi-county community. This attribute would be True if the community isin more than one county. Acceptable values for this field are listed in theD_TrueFalse table.FLOODPRONE R Floodprone. This attribute stores information about the floodprone status ofthe community. Enter True if the community is floodprone. Acceptablevalues for this field are listed in the D_TrueFalse table.FIS_INCLUD R Community Included in this FIS. This value indicates whether thecommunity is included in this FIS report. If the FIS is included, this field isTrue. Acceptable values for this field are listed in the D_TrueFalse table.RECENT_FIS R FIS Report Effective Date. This is the effective date of the current FISreport.Guidelines and Standards forFlood Risk Analysis and Mapping Page L-111 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: Appendix LField R/A TypeTable: Stud
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

Create successful ePaper yourself

Delete template?

Save as template?