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.

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 N: Data Capture Standards, describe the digital topographic data that were 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 N, Section N.1.2)

The Town of Pocatello, Bannock County, ID created 2ft contours by photogrametric methods to serve as terrain. The areas for contour creation 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.

Mineral Resources Section personnel from the Alaska Division of Geological & Geophysical Surveys (DGGS) carried out a geologic field survey, including mapping and sampling, in the eastern part of the Bonnifield mining district in the Fairbanks A-1 and A-2 and the Healy D-1 and D-2 quadrangles, Alaska, from June 16 through July 18, 2008. The fieldwork provides basic information critical to building an understanding of Alaska's geology and is part of an integrated program of airborne geophysical surveys followed by geologic mapping. Specifically, this work provides geologic context for geophysical surveys conducted in 2006. Interpretation and synthesis of this data has been presented in professional and trade meetings. This report and associated geologic map data are preliminary, have not undergone rigorous peer review, and will be superseded by a subsequent Report of Investigations map and report that will be issued later in 2016. The objective of the eastern Bonnifield project is to produce a 1:50,000-scale geologic map to foster a better understanding of the area's geology and mineral potential. Although DGGS concentrated on mapping the Paleozoic metamorphic rocks that host the volcanogenic massive sulfide deposits (VMS) and Mesozoic igneous rocks associated with Au-Ag-As-Sb veins, we also studied the Tertiary sedimentary section, which could contain coal resources. The geologic map data are available in digital format as ESRI shapefiles.

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).

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 levation 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).