New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
GJN3890 Revenue Folder
COE
>
PW
>
Admin
>
Finance
>
Capital
>
2008
>
GJN3890 Revenue Folder
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2009 3:56:00 PM
Creation date
12/30/2008 10:10:49 AM
Metadata
Fields
Template:
PW_Capital
PW_Document_Type_Capital
Admin Documents
PW_Active
Yes
External_View
No
GJN
003890
GL_Project_Number
905116
COE_Contract_Number
2005-00202
GL_Grant
167
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
93
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
• A Summary Report that describes and provides the results of all automated or manual QA/QC <br /> review steps taken during the preparation of the DFIRM; <br /> • NSP Format DFIItM Database or Intermediate Data Delivery consistent with the NSP <br /> Intermediate Data Specifications. <br /> Appendix M may be downloaded from the FEMA Flood Hazard Mapping Web site at <br /> http•//www fema gov/pdf/flim/frm gsam pdf. <br /> Activity 13B -Independent QA/QC Review of DFIRM Product Meeting FEMA <br /> Graphics and Database Specifications <br /> Responsible Mapping Partner: FEMA (NSP) <br /> Scone: Upon completion of the floodplain mapping activities (Activity 11) and DFIlZM production <br /> activities (Activities 13 and 13A), the NSP shall review the DFIRM to ensure it meets current FEMA <br /> j graphics specifications. In addition, the NSP shall review the DFIltM spatial database to determine if it <br /> meets current FEMA database specifications. The NSP shall coordinate with FEMA and other Mapping <br /> Partners, as necessary, to resolve any problems identified during this QA/QC review. This work shall <br /> ~ ensure that the requirements below are met. <br /> ~ • All required DFIRM features are accurately and legibly labeled and follow the examples shown <br /> in the FEMA DFIRM specifications. This includes all flood insurance risk zones, BFEs, cross <br /> sections, studied streams, mapped political entities, and all roads within and adjacent to the 1- <br /> percent-annual-chance floodplains. <br /> <br /> I <br /> • All DFIRM features are correctly symbolized with the appropriate symbol, line pattern, or area <br /> shading and follow the requirements in Guidelines and Specifications for Flood Hazard Mapping <br /> Partners. <br /> • All map collar information is complete, correct, and follows the requirements specified in <br /> Guidelines and Specifications for Flood Hazard Mapping Partners. <br /> • DFIRM mapping files are in one of the GIS file and database formats specified in FEMA's <br /> Guidelines and Specifications for Flood Hazard Mapping Partners and conform to those <br /> specifications for content and attribution. <br /> • DFIRM database files are in one of the database formats specified in FEMA's Guidelines and <br /> Specifications for Flood Hazard Mapping Partners and conform to those specifications for <br /> content and attribution. <br /> • Metadata files describing the DFIRM data include all required information shown in Guidelines <br /> and Specifications for Flood Hazard Mapping Partners. <br /> • The FIS report is prepared in the FEMA Countywide Format as documented in Appendix J of <br /> Guidelines and Specifications for Flood Hazard Mapping Partners. <br /> Standards: All work under Activity 13B shall be performed in accordance with the standards specified in <br /> Section 5 of this MAS. <br /> Deliverables: In accordance with the TSDN format described in described in Appendix M of Guidelines <br /> and Specifications for Flood Hazard Mapping Partners, the NSP shall make the following products <br /> available to FEMA: <br /> Mapping Activity Statement No. 1 1 g <br /> City of Eugene,,OR <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.