Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.4).

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).

The Oregon Department of Geology & Mineral Industries (DOGAMI) contracted with Watershed Sciences, Inc. to collect high resolution topographic LiDAR data for multiple areas within the State of Oregon. The areas for LiDAR collection have been designed as part of a collaborative effort of state, federal, and local agencies in order to meet a wide range of project goals. This LiDAR data set was collected between May 3, 2008 and April 25, 2009 and encompasses portions of the following counties in southwest Oregon- Coos, Curry, Lane, and Douglas. This data set consists of bare earth and unclassified points. There are approximately 8 points per square meter over terrestrial surfaces. In some areas of heavy vegetation or forest cover, there may be relatively few ground points in the LiDAR data. Elevation values for open water surfaces are not valid elevation values because few LiDAR points are returned from water surfaces. LiDAR intensity values were also collected.

Elevation data, as defined in FEMA?s Guidelines and Standards for Flood Risk Analysis and Mapping, describe the digital topographic data that were used to create the data representing the terrain environment of a watershed and/or floodplain. Elevation data requirements allow for flexibility in the types of information used to produce final terrain deliverables. Submission of the terrain data sources allows FEMA to account for the origins of the flood study terrain data.(Source: FEMA Guidelines and Standards for Flood Risk Analysis and Mapping.)

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).

Terrain data, as defined in FEMA Guidelines and Specifications, Appendix M: Data Capture Standards, describes the digital topographic data that was used to create the elevation data representing the terrain environment of a watershed and/or floodplain. Terrain data requirements allow for flexibility in the types of information provided as sources used to produce final terrain deliverables. Once this type of data is provided, FEMA will be able to account for the origins of the flood study elevation data. (Source: FEMA Guidelines and Specifications, Appendix M, Section M.1.2).