DFIRM Quality Control Review Training June 18, 2008 Automation of Six Visual Checks for DFIRM QA/QC Agenda Multi-Hazard Flood Map Modernization Overview of QA/QC Process Process change and user impacts & benefits Summary of each of the six validation checks being moved from Visual Review to Automated Review Q & A Current QA/QC Process Multi-Hazard Flood Users submit DFIRM data for Automated Review at Draft and at Preliminary stage Auto Pass/Failnotification and reportlink sent back to user through MIP Users submit DFIRM data and panel images forAutomated and Visual Review at Final stage Auto and Visual Pass/Fail notification and report link sent back touser through MIP Impact of Process Change Six checks added to the Draft submission May increase the errors received; will not validate data not present in submission (will not increase failures for “structure only” submissions) Will find errors earlier in the process, giving users more time to resolve Management impact: • Partners may need to spend more time resolving errors before prelim submission June 19, 2008 (any DFIRM that is submitted for the first time as part of Quality Review #1; any DFIRM re-submittals after this date will not be subjected to these checks). • Six checks added to Prelim & Final submissions Will increase errors received; project cannot proceed until errors are resolved (PM 42) Will find errors earlier in the process, giving users more time to resolve Management impact: • Additional errors for prelim submissions, along with hard stop until errors are resolved, may delay prelimunless more time is planned (cost/schedule increase) June 19, 2008 (any DFIRM that is submitted for the first time as part of Quality Review # 3 or #5; DFIRM re-submittals after this date will not be subjected to these checks). Impact of Process Change Transition Studies Studies submitted for the first time prior to deployment will need to be monitored MOD Team will review error reports and pass studies with only 1300 Series errors Email to joseph.schule@mapmodteam.com with questions or concerns regarding FAFS notifications Benefits of Process Change Early detection of 1300 Series errors improvesdata quality and reduces recycle rate ofsubsequent submissions Known tolerances – make adjustments toproduction process to stay within tolerances Will increase the quality of the end product bycatching errors that would slip through visualinspection New QA/QC Process After completing Autoreview, each submission then enters Six Checks Users will then receive an integrated reportshowing checks for theexisting Auto Screen andthe Six Checks Users do not have to make any changes to the way they send data Users will have to correct errors called bySix Checks to pass Auto Users should receive a shorter Visual reportsince errors will have been fixed earlier Multi-Hazard Flood Six new checks moved from Visual to Automated review Map Modernization Logic descriptions found in “FEMA DFIRM Verification Check Standard”, v2.0, July 11, 2007 Check 2.9.1.1 (Error 1301) SFHA polygons must be surrounded by a flood hazard line with a valid LN_TYP Check 2.9.1.2 (Error 1302) BFE lines must end within 25 feet of the SFHA boundary Check 2.9.1.3 (Error 1303) BFE lines must not intersect Check 2.9.1.4 (Error 1304) Vertical datum cited in the STUDY_INFO table must match the vertical datum for every cross section (S_XS) line Check 2.9.1.5 (Error 1305) Vertical datum cited in the STUDY_INFO table must match the vertical datum for every BFE (S_BFE) line Check 2.9.1.6 (Warning 1306) The PNP_REASON field must be populated for every non-printed panel inS_FIRM_PAN Check 1301: Invalid line type Multi-Hazard Flood Checks that the flood hazard line surrounding Special Flood Hazard Area polygons are coded with a valid line type. Check 1301 logic: If S_FLD_HAZ_AR SFHA_TF attribute is coded to “T” and the bounding S_FLD_HAZ_LN LN_TYP is coded as: “Floodway, Limit of Floodway, Limit of Detailed Study, Limit of Study, 1 PCT Annual Chance Flood Hazard, End of Spatial Extent, Zone Break, Apparent Limit, or Source Boundary” Then: Correct – Please move to next check Else: An error will be returned as: “Error 1301: The S_FLD_HAZ_AR polygon attributed as a Special Flood hazard Area is bound by an invalid S_FLD_HAZ_LN LN_TYP” Check 1301: Example 1 Error is called because SFHA polygon is Zone A but surrounded by a line coded “0.2 PCT ANNUAL CHANCE FLOOD HAZARD” Auto Report will list the ID of the affected polygon, in this case FLD_AR_ID = ‘279’ To correct the error, flood hazard line ID 629 must be coded “1 PCT ANNUAL CHANCE FLOOD HAZARD” 1301: Example 2Check 1301: Example 212 Check 1301 will also find flood hazard lines that overshoot a polygon boundary and overlap theline around the adjacent polygon In this example, the 0.2 PCT linearound the lower polygon extendsupwards past the polygon boundaryand touches the 1 PCT polygon A 25-foot tolerance was added to Check 1301-lines like this one will be allowed to pass Check 1301 will still be called if the overshooting line is longer than 25 feet To correct the error, the overshooting line will have to beclipped at the polygon boundary 0.2PCTlineoverlaps1PCTlineforthissegment.Lengthabout7.5feet. Check 1302: BFE line Undershoot/Overshoot Map Modernization Checks that BFE lines extend to the Special Flood Hazard Area boundary Checks BFE lines in AE and AH zone polygons with no static BFEs Small overshoots and undershoots of less than 25 feet will be allowed to pass Check 1302 logic: If: S_BFE line is within +/-25 feet of the SFHA boundary Then: Correct – Please move to next check Else: An error will be returned as: “Error 1302: The following S_BFE line (s) undershoot or overshoot the SFHA boundary by more than 25 feet” 1302: BFE line Under/Overshoot This BFE line undershoots the SFHA boundary by more than 25 feet To fix the error, the line must be extended to the SFHA boundary Small undershoots or overshoots will be allowed to pass if they are less than 25 feet Check 1302: BFE line Under/Overshoot Example 2 Map Modernization Check 1302 allows special cases to pass BFE lines that do not extend across the SFHA will still pass ifthe adjacent polygon is not supposed to have BFE lines The lines will pass aslong as they are within25 of the polygonboundary in this example Check 1302: BFE line Under/Overshoot Example 3 Map Modernization Check 1302 allows special cases to pass BFE lines that do not extend across the SFHA will still pass ifthey are interrupted bya general structure such as a levee The lines will pass aslong as they are within25 feet of the general structure Check 1303: BFE lines do not intersect Checks that BFE lines to not intersect any other BFE lines. Check 1303 logic: If S_BFE line does not overlap or touch another S_BFE line Then: Correct – Please move to next check Else: An error will be returned as: “Error 1303: The S_BFE line overlaps or touches another S_BFE line” Check 1303: BFE lines do not intersect Example These two BFE lines (ID222 and ID 223) overlapeach other To correct this error, one of the lines needs to be removed BFElineID222and223overlap Check 1304: V_DATUM must match Map Modernization Checks that the vertical datum cited in the study_info table matches the vertical datum cited for every cross section line Check 1304 logic: If: S_XS V_Datum field is equal to the V_Datum field in the STUDY_INFO table. Then: Correct – Please move to next check Else: An error will be returned as: “Error 1304: The S_XS line V_Datum attribute does not match the V_Datum attribute in the STUDY_INFO table” Check 1304: V_DATUM must match Example Map Modernization The vertical datum cited in STUDY_INFO is “NAVD88” while the vertical datum is mistyped as “NADV88” in the S_XS table To correct this error, V_DATUM must be changed to “NAVD88” for every cross section Check 1305: V_DATUM must match Map Modernization Checks that the vertical datum cited in the study_info table matches the vertical datum cited for every BFE line Check 1305 logic: If: S_BFE V_Datum field is equal to the V_Datum field in the STUDY_INFO table. Then: Correct – Please move to next check Else: An error will be returned as: “Error 1305: The BFE line V_Datum attribute does not match the V_Datum attribute in the STUDY_INFO table” Check 1305: V_DATUM must match Example Map Modernization The vertical datum cited in STUDY_INFO is “NAVD88” while the vertical datum is mistyped as “NADV88” in the S_BFE table To correct this error, V_DATUM must be changed to “NAVD88” for every BFE line Check 1306: Panel-not-printed Reason Map Modernization Checks that the PNP_REASON field is populated for every non-printed panel in S_FIRM_PAN Check 1306 logic: If: S_FIRM_PAN PANEL_TYP field is populated as Countywide, Not Printed or Community Based, Not Printed and the PNP_REASON is field populated with a string Then: Correct – Please move to next check Else: An error will be returned as: “Warning 1306: The S_FIRM_PAN polygon has a potentially incorrect combination of attributes for PANEL_TYP and PNP_REASON.” Check 1306: Panel-not-printed Reason Example Map Modernization The PNP_REASON is blank for these five records even though the PANEL_TYP is“COUNTYWIDE, NOT PRINTED” To correct this problem, thePNP_REASON field must be populated with thepanel-not-printed reason The specific wording for the panel-not-printedreason will still be validated against the Index Mapduring visual inspection