M.2 Scoping Submittal Standards
Summary of questions/comments received for the scoping section on DHS Interactive and responses provided through October 10, 2008.
| Topic | Comment | Response |
|---|---|---|
| Scoping Data Requirements | Will the S_Needs_Ar spatial file need to be populated with the approximate flood hazard areas for county-wide restudies? If so, the attribute field Reach will be populated many times with "unnamed stream." Would it be possible to group the approximate flood hazard areas by basin? Additionally: 1 - The requirements for S_Hydro_Ar should also be defined along with S_Hydro_Ln 2 - For S_Fin_Study_Ln, are the DFIRM database and NHD 100k stream networks the only acceptable stream networks that can be used? 3 - For S_Fin_Study_Ar, can project subbasins be used rather than DFIRM database and NHD-based subbasins? 4 - For the NatMetrics_Info table, does Area refer to the area of floodplain being mapped or community area? 5 - The scoping directory structure looks more like an outline. This should be formatted to look like the other sections (Basemap, Terrain, etc.) |
The S_Needs_Ar spatial file captures needs with a polygon feature for a stream reach or ponding area. All effective study flood hazard areas must be represented as individual polygons in the S_Needs_Ar spatial file for the validation process. The reach name should reflect the flooding source name from the DFIRM database or hydrography data source. Multiple entries of 'unnamed stream' are acceptable. 1. Text will be revised as follows: "The S_Hydro_Ln spatial file contains the stream centerlines for the study area that extend beyond the community boundary by 1,000 to 2,000 feet. This enables the capture of effective segments that may meander just outside the community boundary. The S_Hydro_Ar spatial file contains the watersheds that either fall completely within or intersect the study area." The requirement for submittal of both these files will be optional. 2. Other data sets are acceptable. Text will be revised as follows "This spatial file contains flood sources included in the scope of work for the Flood Map Project update. Best available data sources that should be used include the study area's effective DFIRM Database S_WTR_LN feature class or the USGS NHD Stream data. To ensure that the Scope of Work is captured it may be necessary to use other stream data sources or a combination of stream data sources. This file should provide an inventory of miles by effective and proposed zone and study type for the project area." The requirement for submittal of this file will be optional. 3. Other subbasins can be used. Text will be revised as follows "This spatial file contains flood sources included in the scope of work for the Flood Map Project update. Best available data sources that should be used include the study area’s effective watershed boundary or the USGS HUC data. To ensure that the Scope of Work is captured it may be necessary to use other data sources or a combination of stream data sources. This file should provide an inventory of square miles by effective and proposed zone and study type for the project area." The requirement for submittal of this file will be optional. 4. This field represents the non-riverine flooding sources (i.e., ponding areas) to be studied in the new FIS. 5. The scoping section does not have comparable metadata, certification, or project narrative requirements. The scoping deliverables are organized to match the discussion in the accompanying guidance document. |
| Project Scoping Initiation Requirements | It would be helpful if the requirements for who participates on the Flood Map Project Management Team were defined or included a reference for where this information can be found. | This information is typically included in the Mapping Activity Statement (MAS) or Scope of Work (SOW) documents. However, guidance regarding the deliverables for scoping assessment and scoping processes, such as who participates on the Project Management Team, is currently being developed by FEMA as an update to Appendix I. |
| Field Names | Since ESRI Shapefile format is listed as an acceptable file format for scoping data, many field names are too long for adherence to .shp (.dbf) standards, even though acceptable in a personal/file GDB. For example: S_Needs_Ar = date_resolv = date_effana S_Requests = Date_ResolV = Fld_Data_Rqst S_Fin_Study_Ln & S_Fin_Study_Ar = Effective zone_LID = LEVEL_EFF_LID = Flooding_type_LID = Stream_Name = LEVEL_FIN_LID Also, if DBF is used for tabular information files, some field names will also be too long. |
In order to be compatible with specified acceptable file format (.shp and .dbf) standards, the following field name changes will be incorporated in the next revision of Appendix M.2.: Feature Class: S_Needs_Ar 1. date_req -> Date_Rqst 2. date_Resolv -> Date_Resol 3. date_effana -> Date_Effct Feature Class: S_Requests 1. Date_ResolV -> Date_Resol 2. Fld_Data_Rqst -> FData_Rqst S_Fin_Study_Ln & S_Fin_Study_Ar 1. Effective zone_LID -> Eff_Zone 2. LEVEL_EFF_LID -> Level_Eff 3. Flooding_type_LID -> Flood_typ 4. Stream_Name -> Strm_Name 5. LEVEL_FIN_LID -> Level_Fin Additional related changes not addressed include: NatMetrics_Info 1. TOT_MAPPED_MI -> TOT_MAP_MI Domain Name Change 2. D_Fld_Data_Rqst -> D_FData_Rqst |
Last Modified: Thursday, 04-Jun-2009 13:41:06 EDT