Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Pol_Ar table contains information about political areas within the Flood Risk Project area. This includes the attributes for the political areas within the Flood Risk Project and whether or not they have been studied or participate in the National Flood Insurance Program (NFIP). The political jurisdiction assigned to each area corresponds to the jurisdiction responsible for NFIP and floodplain management for that area. This table is used in following FIS Report components: the FIS Report cover, the FIRM panel index, the Panel Locator on the FIRM panels, the Transect Locator Map and the following tables in the FIS Report: Listing of NFIP Jurisdictions, Flooding Sources Included this FIS Report, Flood Zone Designations by Community, Levees, Transect Locator Map, Summary of Topographic Elevation Data Used in Mapping, Community Map History, Summary of Contracted Studies Included in this FIS Report and Community Meetings. The spatial entities representing political areas are polygons. </SPAN></P></DIV></DIV></DIV>
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 12 Font Family: Times New Roman Font Style: normal Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is maintained only in the National Flood Hazard Layer (NFHL) database. It is not part of Mapping Partners’ Preliminary or Effective FIRM Database submittals. This table is not prepared by Mapping Partners but by the FEMA contractors responsible for maintaining the NFHL database. This layer incorporates the results of effective Letter of Map Revisions (LOMRs) into FIRM data submitted to FEMA and is stored in the NFHL database for future PMRs. The S_LOMR layer includes all LOMRs that have been incorporated into the NFHL database. The S_LOMR feature class should contain at least one record for each LOMR incorporated into the NFHL. Multipart polygons are not allowed. The spatial entities representing LOMRs are polygons. The spatial information contains the bounding polygon for each LOMR area, broken on panel boundaries. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>This table is required for any FIRM Database where cross sections are shown on the FIRM or where modeled cross sections were used to generate the special flood hazard area boundaries. Normally, any FIRM that has associated flood profiles has cross sections. The S_XS table contains information about cross section lines. This information is used in the Floodway Data Tables in the FIS Report, as well as on the FIRM panels. Database attributes should reflect the final regulatory water surface elevations that include any backwater elevations regardless of flood hazard zone and should be consistent with values in the floodway data tables and flood profiles, where applicable. All cross sections – modeled or interpolated – must be stored in the S_XS, regardless of whether or not they are shown on the FIRM and regardless of the flood hazard zone ultimately depicted on the effective panels. </SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The spatial elements representing BFE features are lines extending from Special Flood Hazard Area (SFHA) boundary to SFHA boundary. The ends of the BFE lines must be snapped precisely to the SFHA boundary. The Base Flood Elevation (BFE) table is required for any digital data where BFE lines will be shown on the corresponding FIRM, with the exception of newly studied areas where a profile exists. For newly studied areas where a profile exists, the water-surface elevation (BFE value) will be labeled on the cross sections as stored in the FIRM Database S_XS feature class. The use of BFE lines is only required in special cases. BFEs (i.e., cross-section values supplemented with BFE lines where needed) must be shown at appropriate locations to allow map users to accurately interpolate flood elevations both horizontally and vertically. BFEs for ponding and lacustrine areas must be expressed to the 10th of a foot if they have been calculated to that level of precision; otherwise, they should be shown as whole-foot rounded elevations. Unrevised lake and ponding elevations may be converted to 10th foot elevations if supported by technical data on a project-by project basis and if supported by the FEMA Region. BFEs for coastal flood zones must be shown as whole foot elevations. Other examples include; a riverine AE zone without a flood profile in the FIS Report, areas studied with two- dimensional modeling, certain ponding areas and backwater areas off to the side of streams with flood profiles. BFEs may be used for other exceptions at the discretion of the FEMA Project Officer. Any exceptions to these guidelines should be documented in the metadata. The Mapping Partner must avoid overcrowding of the BFE and cross section lines. When a stream is so steep that there are more than four cross sections and / or BFE lines per one inch of map panel distance, determine the best elevation increments to retain clear labeling. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Profil_Basln layer is required for all types of riverine hydraulic analyses. Profile baselines are required to be shown on FIRM panels for all valid studies with profiles or otherwise established Base Flood Elevations. Profile baselines are also required in new riverine Zone A areas with model backup. At the discretion of the FEMA Project Officer water lines may be shown on vector maps to represent the bank or stream centerline location. When a profile baseline and water lines are available for the same stream reach, only the profile baseline shall be shown on the FIRM in order to eliminate overlaps. A profile baseline is also required when a Flood Risk Project is not being updated but the effective profile baseline still accurately represents conditions on the ground. This information is used in the following tables within the FIS Report: Flooding Sources Included in this FIS Report, Principal Flood Problems, Summary of Hydrologic and Hydraulic Analyses, Summary of Topographic Elevation Data Used in Mapping, the Stream-by-Stream Vertical Datum Conversion and Summary of Contracted Studies Included in this FIS Report. The spatial entities representing the profile baseline are lines. Profile baselines are to be stored in Polyline ZM feature classes, storing both profile station values (M-values) and 1-percent-annual- chance water-surface elevations (Z-values) at cross sections, structures and other modeled inflection points. For new models and effective models with valid profile baselines, vertices along the profile baseline are to be calibrated between cross sections and structures using linear referencing / dynamic segmentation tools in GIS. The first vertex of each profile baseline will be the downstream most point on the profile. </SPAN></P></DIV></DIV></DIV>
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Tsct_Basln layer is required for all coastal studies. The S_Tsct_Basln spatial file contains information about the transect baseline used in the coastal flood hazard model. Typically, the S_Tsct_Basln represents the 0.0-foot elevation contour, the starting point for the transect and the measuring point for the coastal mapping. The spatial elements representing the transect baselines are lines. The file describes the transect baseline profile setting and must also include a reference to the vertical datum. When a coastal transect baseline and water lines are available for the same study reach, only the transect baseline shall be shown on the FIRM in order to eliminate overlaps. This information is used in the following tables in the FIS Report: Transect Locator Map, as well as in the Flooding Sources Included this FIS Report, Summary of Coastal Analyses, Summary of Topographic Elevation Data Used in Mapping and Coastal Transect Parameters. The spatial entities representing the transect baselines are lines. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is required for any Preliminary or Final FIRM Database that includes levees, floodwalls or dikes that have been designed for flood control, including those portions that are closure structures, whether or not they have been demonstrated to meet the NFIP requirements in 44 CFR 65.10. This information is shown in the Levees table in the FIS Report and on the FIRM panels. The S_Levee table contains information about levees shown on the FIRMs that are accredited and known to be protecting against the 1-percent-annual-chance flood, as well as levees that are provisionally accredited, and non-accredited. The purpose of this table is to document the accreditation status of levees, as well as associated information necessary to be shown on the FIRM and for the population of FIS Report text related to levee structures. The spatial entities representing levees are lines, drawn at the centerline of levees, floodwalls and levee closure structures. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is required whenever hydraulic structures are shown in the flood profile. It is also required when 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. This table contains both riverine and coastal structure types. The S_Gen_Struct table must include all structures shown on the flood profiles, with the exception of riverine or coastal levees, floodwalls and closure structures; those structures must be placed in S_Levee, not in S_Gen_Struct. Refer to the S_Levee table for more information. Additional information about coastal structures is placed in L_Cst_Struct. In addition, channels that contain flooding and other significant flood control structures shown on the FIRM, must be included. Spatial elements 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. A line corresponding to the centerline of the main barrel must represent a culvert. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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 Flood Risk Project. The S_Cst_Tsct_Ln table contains information about the Coastal Transect Lines within the Flood Risk Project area, if applicable. The spatial elements representing coastal transects are lines that generally extend from offshore all the way across the coastal floodplain. Transects can also extend seaward when wave runup modeling is used to determine coastal flood hazards. This information is needed for the Transect Locator Map table and Coastal Transect Parameters table in the FIS Report. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is required for all Preliminary or Final FIRM Databases that show coastal Limit of Moderate Wave Action (LiMWA) features. Reference Procedure Memorandum No. 50 for additional information. The S_LiMWA layer is required when a Limit of Moderate Wave Action (LiMWA, previously described as a Coastal Zone A boundary line) is delineated within the coastal floodplain. This layer is required for new coastal analysis. The spatial entities representing the LiMWA are lines. The line represents the limit of 1.5-foot or greater waves in a Coastal AE Zone. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>The S_Cst_Gage layer is required when gage information (from 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 wave buoy data provides information regarding the wave climate in the Flood Risk Project area; when wave buoy 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 Flood Risk Project must be compared with observed data from wave buoys whenever possible. The S_Cst_Gage table contains information about coastal gages for the Flood Risk Project area. The spatial location of these gages may be some distance from the areas for which coastal flood hazards were determined. This information is needed for the Tide Gage Analysis Specifics table in the FIS Report. The spatial entities representing the coastal gages are points. </SPAN></P></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is required for any FIRM Database where vector surface water features are shown on the FIRM and some of these features are represented as lines in the spatial data. Vector streams must always be shown with a vector base map. They may also be shown on raster base maps at the discretion of the FEMA Project Officer. The S_Wtr_Ln table contains information about surface water linear features. A spatial file with location information also corresponds with this data table. The spatial elements representing surface water line features are lines. Surface water features may appear in either the S_Wtr_Ar table or the S_Wtr_Ln table or both. However, features that appear in both must match exactly. The hydrologic structure of the modeled stream network will be represented by the S_Profil_Basln layer. This information is used in the Transect Locator Map and the FIRM Panel Index in the FIS Report, as well as the FIRM panels. </SPAN></P></DIV></DIV></DIV>
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 11 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is required for any FIRM Database where vector surface water features are shown on the FIRM and some of these features are represented as polygons in the spatial data. Otherwise, the table is optional. The S_Wtr_Ar table contains information about surface water area features. A spatial file with location information also corresponds with this data table. The spatial elements representing surface water area features are polygons. This information is used in the Transect Locator Map and the FIRM Panel Index in the FIS Report, as well as the FIRM panels. </SPAN></P></DIV></DIV></DIV>
Color: [0, 77, 168, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Times New Roman Font Style: italic Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>S_Gage table contains information about riverine gages for the Flood Risk Project area. Coastal gages are stored in S_Cst_Gage. This table is required for all new studies containing riverine analysis and should be populated with available data from existing studies when possible. The spatial location of these gages may be some distance from areas from which flood hazards were determined. A spatial file with location information also corresponds with this data table. This information is needed for the Stream Gage Information Used to Determine Discharges table in the FIS Report. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>S_HWM table contains information about high water marks (HWMs) for the Flood Risk Project area. This table is required for Preliminary and Final FIRM Databases when the community has provided high water mark data. A spatial file with location information also corresponds with this data table. This table is used for the Historic Flooding Elevations table in the FIS Report, if this information is available. The spatial entities representing the high water marks are points. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>The S_Riv_Mrk table contains information about the river marks shown on the FIRM if applicable. A spatial file with location information also corresponds with this data table. The spatial entities representing the river marks are points. The points are generally located along the centerline of the river at regular intervals or as indicated by the data source. </SPAN></P></DIV></DIV>
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This table is required for any FIRM Database that has an S_Profil_Basln, S_Riv_Mrk or L_XS_Elev table. It is used to populate the Floodway Data Tables and Flood Profiles, as well as the Flood Hazard and Non-Encroachment Data for Selected Streams table in the FIS Report. The S_Stn_Start table contains information about station starting locations. These locations indicate the reference point that was used as the origin for distance measurements along streams and rivers. This table is referenced by both the L_XS_Elev table, which contains stream station information for cross sections and the S_Riv_Mrk table, which contains river distance marker points. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>The S_Fld_Haz_Ln table contains information about the flood zone boundary features for the Flood Risk Project area. A spatial file with location information also corresponds with this data table. Flood hazard data should not be shown beyond the extent of the county/community boundary. If the modeled information extends beyond the political area, the flood hazard data should be clipped to the political boundary. The spatial elements representing the boundaries of the flood hazard areas depicted on the FIRM are lines. </SPAN></P></DIV></DIV>
Label Placement: esriServerLinePlacementAboveAlong Label Expression: "LIMIT OF STUDY" Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 1128.497176 Max. Scale: 0.0 Label Placement: esriServerLinePlacementAboveAlong Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Fld_Haz_Ar table contains information about the flood hazards within the Flood Risk Project area. A spatial file with location information also corresponds with this data table. These zones are used by FEMA to designate the Special Flood Hazard Area (SFHA) and for insurance rating purposes. These data are the regulatory flood zones designated by FEMA. The spatial elements representing the flood zones are polygons. The entire area of the jurisdiction(s) mapped by the FIRM should have a corresponding flood zone polygon. There is one polygon for each contiguous flood zone designated. </SPAN></P></DIV></DIV></DIV>
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 18055.954822 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Min. Scale: 0.0 Max. Scale: 0.0 Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: N/A Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Nodes layer is required for non-coastal hydrologic analyses where nodes were defined as part of the analysis. The contributing drainage area and the discharges for all frequencies required for the Flood Risk Project (e.g., the 10-percent, 2-percent, 1-percent and 0.2-percent-annual-chance floods) represent the discharges based on the cumulative upstream drainage area. Nodes can represent sub basin outlets, junctions, reservoirs, structures or diversions. Note that nodes are required at all flow change locations. This information is used in the following tables in the FIS Report: Summary of Discharges, Summary of Summary of Non-Coastal Stillwater Elevations and Flood Hazard and Non- Encroachment Data for Selected Streams. In addition to hydrologic modeling usage, 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 L_Summary_Elevations file at the corresponding node. A node should be placed in areas with non-coastal static BFEs and a corresponding L_Summary_Elev record entered for each event type for the NODE_ID unless the Region determines that the flood sources do not warrant inclusion in the FIS Report. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The table is required for all hydrologic analyses. The hydrologic reach represents the connectivity between the subbasins and the flow direction between nodes in the hydrologic model. The spatial entities representing the hydrologic reaches are lines. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Subbasins table contains data specific to each subbasin in the hydrologic analysis, including the relationship of the subbasin to the hydrologic network. The subbasin may be specific to a detailed hydrologic model. It may also correspond to the drainage area used in a regression analysis or to the drainage area for a stream gage. S_Subbasins is intended to store Hydrologic Unit Code 8 (HUC8) or smaller subbasin information related to the hydrologic model. This information is used in the Basin Characteristics tables in the FIS Report, as well as for the FIRM Panel Index Map. The spatial elements representing the subbasins are polygons. In some cases, the extent of these polygons may overlap, for example, cumulative subbasin areas for a regression analysis. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Datum_Conv_Pt table is required when a countywide/community-based or flooding sourced- based vertical datum conversion was performed as part of the Flood Risk Project. It is not required for a passive vertical datum conversion. The Vertical Datum Conversion Guidance document should be referenced to determine which type of factor must be calculated. See also the FIRM Database Guidance document for additional information about datum conversion points. The spatial elements representing this layer are points. There cannot be a mixture of countywide/community-based and flooding source-based conversion factors within one FIRM Database. This information is needed for the Countywide Vertical Datum Conversion and Flooding Source-Based Vertical Datum Conversion tables in the FIS Report. </SPAN></P></DIV></DIV></DIV>
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The S_Submittal_Info layer contains essential information about the Flood Risk Project such as the FEMA case number and utilized engineering models. The spatial entities representing the Flood Risk Project areas are polygons corresponding to the area to be revised by this Flood Risk Project. These can be one or multiple irregular polygons that capture the extent of the Flood Risk Project area(s). Each data capture submittal requires a corresponding S_Submittal_Info layer with one or more polygons that reflect the scope of the data for that specific submittal. In the finished FIRM Database, the separate S_Submittal_Info layers for each data submittal are combined into a composite layer made up of all the individual S_Submittal_Info polygons from each data capture submittal. In the final FIRM Database, there will be multiple S_Submittal_Info polygons for the same Flood Risk Project area that represent multiple Data Capture task areas. S_Submittal_Info polygons can overlap between different Data Capture tasks. However, with some exceptions, S_Submittal_Info polygons should not overlap within the same Data Capture task. For example, the S_Submittal_Info polygons for the Hydraulics Data Capture task for two streams modeled using different hydraulic models should not overlap. Similarly, S_Submittal_Info polygons for the finished terrain surface used for modeling should not overlap other polygons corresponding to the finished terrain surface. In other words, for any given location there should be only one polygon representing the hydraulic model or the finished terrain surface used in the Flood Risk Project. Existing Topographic Data Capture S_Submittal_Info polygons may overlap. 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. This information is used in the following tables in the FIS Report: Summary of Contracted Studies Included in this FIS Report, Summary of Hydrologic and Hydraulic Analyses and Summary of Topographic Elevation Data Used in Mapping. </SPAN></P></DIV></DIV></DIV>
Label Placement: esriServerPolygonPlacementAlwaysHorizontal Label Expression: "See Notes To User for, information about this boundary" Use Coded Values: true Symbol:
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 9 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: The S_Base_Index table contains information about the raster data used as a base map for the Flood Risk Project area. This table is required if a different base map was used for modeling than the base map for the FIRM when using AMP.
The spatial elements representing raster base map tile index features are rectangular polygons. For standard U.S. Geological Survey Digital Ortho Quadrangles, polygons must match quarter-quad boundaries. Otherwise, polygons must match the boundaries of the raster tiles used. Polygonal overlap is acceptable where necessary. S_Base_Index is required on both tiled rasters and raster mosaics.
Data last acquired from FEMA MSC on 20230710.