{"action":"create","ckan_id":null,"date_created":"Mon, 09 Mar 2026 23:52:43 GMT","date_finished":null,"harvest_job_id":"57bd946f-9090-4070-9c1c-346d1ce3ce91","harvest_source_id":"4c62556f-0fa3-402d-90f6-6a46cd80a117","id":"f69dfdb8-3764-4969-ba62-ec4919a39735","identifier":"https://hazards.fema.gov/filedownload/metadata/R10/637092-DevTopographicData.xml","parent_identifier":null,"source_hash":"1b47a010675c885e549dc87b43116667b126a87cfc1f8728d46163842bdca838","source_raw":"\r\n\r\n \r\n \r\n \r\n STARR (Strategic Alliance for Risk Reduction)\r\n Watershed Sciences, Inc.\r\n 20110216\r\n DCS Terrain Submission for City of Scappoose PAL, Columbia County OR\r\n FEMA-DCS-Terrain\r\n \r\n Washington, DC\r\n Federal Emergency Management Agency\r\n \r\n http://hazards.fema.gov\r\n \r\n \r\n Federal Emergency Management Agency\r\n Unknown\r\n FEMA CASE 11-10-0129S\r\n \r\n \r\n \r\n \r\n \r\n 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).\r\n Terrain data is used to represent the topography of a watershed and/or floodplain environment and to extract useful information for hydraulic and hydrologic models. (Source: FEMA Guidelines and Specs, Appendix M)\r\n Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data of the Columbia River in Oregon, Washington, Idaho, and Montana. The requested AOI area for this delivery was 181,694 acres. The area was expanded to include a 100 m buffer to ensure complete coverage and adequate point densities around survey area boundaries, resulting in 191,071 acres of delivered data. LiDAR data for delivery two was collected between December 2nd, 2009 and February 5th, 2010. This area includes portions of the Columbia River from Castle Rock to Woodland and extends southeast from Portland to the Bonneville Dam. The collection flight was flown at approximately 900 feet AGL. Watershed Sciences, Inc. acquired the LiDAR terrain data using the Leica ALS50 Phase II and ALS60 laser systems, which can fire up to 105,000 laser pulses per second. LiDAR data was collected with the following parameters: Pulse Rate Frequency of 105 kHz; Scan Frequency of 52 Hz; Scan Angle of +/-14 degrees from nadir. Watershed Sciences, Inc post-processed the data and a ground model was derived from the LiDAR dataset. The positional accuracy of these laser returns are within 13 centimeters in the vertical axis, with at least 8 laser shots per square meter. All areas were surveyed with an opposing flight line side-lap of H60% (H100% overlap) to reduce laser shadowing and increase surface laser painting. The Leica laser systems allow up to four range measurements (returns) per pulse, and all discernable laser returns were processed for the output dataset. To accurately solve for laser point position (geographic coordinates x, y, z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Aircraft position was measured twice per second (2 Hz) by an onboard differential GPS unit. Aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft/sensor position and attitude data are indexed by GPS time.\r\n \r\n \r\n \r\n \r\n 20110223\r\n \r\n \r\n MIP Submission Date\r\n \r\n \r\n In work\r\n Unknown\r\n \r\n \r\n \r\n -124.1219\r\n -114.0123\r\n 49.0009\r\n 44.8207\r\n \r\n \r\n \r\n \r\n ISO 19115 Topic Category\r\n elevation\r\n \r\n \r\n FEMA NFIP Topic Category\r\n Land Surface\r\n Relief\r\n Topography\r\n Digital Terrain Model\r\n Elevation Data\r\n LIDAR\r\n Breaklines\r\n Contours\r\n DEM\r\n \r\n \r\n None\r\n REGION 10\r\n STATE OR\r\n COUNTY COLUMBIA\r\n COUNTY-FIPS 009C\r\n COMMUNITY Columbia County, Unincorporated and Incorporated Areas\r\n FEMA-CID 41009C\r\n COMMUNITY Columbia County, Unincorporated Areas\r\n FEMA-CID 410034\r\n COMMUNITY City of Scappoose\r\n FEMA-CID 410039\r\n \r\n \r\n Restricted\r\n Acknowledgement of FEMA would be appreciated in products derived from these data. This digital data is produced for the purposes of updating/creating a DFIRM database.\r\n \r\n \r\n The Terrain package includes flow vectors and non-tiled data (SinkBreach, NoData, VoidData, ExternalBoundary, Island). The Terrain data are consistent with the elevation dataset. A comparison of profile plots with the flow vector data confirms that flow vectors are correctly drawn. Flood hazard boundaries do not extend beyond the ExternalBoundary, if it exists. FIRM panels show the flood hazard area delineations where Island data are present.\r\n Data contained in the Terrain package highlights specific issues in the elevation datasets. Terrain data are derived datasets that aid automated hydrologic and hydraulic analyses, the flood hazard area boundary delineations, and quality control.\r\n \r\n \r\n Absolute Accuracy\r\n \r\n 30\r\n Horizontal Accuracy information is not provided within the ?LiDAR Remote Sensing Data Collection: Columbia River Survey Delivery 2?, dated May 13, 2010, and prepared by Watershed Sciences. We assumed that it is 30 cm (RMSE) based upon the specifications for the Columbia River Treaty 2014/2024 project.\r\n \r\n \r\n \r\n Absolute Accuracy\r\n \r\n 4.1\r\n The specification for the Columbia River Treaty 2014/2024 project required the absolute vertical accuracy of less than 13cm (RMSE). For delivery area 2, the absolute vertical accuracy as tested from 4983 RTK fixed, hard-packed road surface points is 4.1 cms for 1-sigma, an average delta-z of -1.8cms, and a RMSE of 4.4 cms. Please see Lidar report for more details.\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n Watershed Sciences, Inc.\r\n 201011\r\n Lower_Columbia_Terrain_2010nov.gdb\r\n \r\n \r\n External Hard drive\r\n \r\n \r\n \r\n 20100210\r\n \r\n \r\n ground condition\r\n \r\n VARIABLE-SPACING1\r\n post-processed bare earth point cloud provided by United States Army Corps of Engineers for use in Columbia County, Scappoose PAL PMR Study\r\n \r\n \r\n \r\n \r\n Watershed Sciences, Inc.\r\n 201011\r\n be_45122F6, be_45122F7, be_45122F8, be_45122G6, be_45122G7, be_45122G8\r\n \r\n \r\n External Hard drive\r\n \r\n \r\n \r\n 20100210\r\n \r\n \r\n ground condition\r\n \r\n REGULAR-GRID1\r\n 1 meter DEMs derived from post-processed bare earth point cloud provided by United States Army Corps of Engineers for use in Columbia County, Scappoose PAL PMR Study\r\n \r\n \r\n \r\n \r\n David C. Smith and Associates (DSA)\r\n 201011\r\n CF1_BREAKLINES.dwg - CF3_BREAKLINES.dwg, FH1_BREAKLINES.dwg - FH4_BREAKLINES.dwg, KO1_BREAKLINES.dwg - KO6_BREAKLINES.dwg, LC1_BREAKLINES.dwg - LC3_BREAKLINES.dwg, MCA1_BREAKLINES.dwg - MCA5_BREAKLINES.dwg, PDX1_BREAKLINES.dwg - PDX7_BREAKLINES.dwg, PO1_BREAKLINES.dwg - PO7_BREAKLINES.dwg, SN1_BREAKLINES.dwg - SN7_BREAKLINES.dwg, TC1_BREAKLINES.dwg - TC3_BREAKLINES.dwg, UC1_BREAKLINES.dwg - UC6_BREAKLINES.dwg\r\n \r\n \r\n External Hard drive\r\n \r\n \r\n \r\n 201011\r\n \r\n \r\n ground condition\r\n \r\n BREAKLINES1\r\n breaklines used for enforcing the finalized ground model provided by United States Army Corps of Engineers for use in Columbia County, Scappoose PAL PMR Study\r\n \r\n \r\n \r\n \r\n STARR (Strategic Alliance for Risk Reduction)\r\n 20110223\r\n be_45122f6_3m_inft_cont.shp, be_45122f7_3m_inft_cont.shp, be_45122f8_3m_inft_cont.shp, be_45122g6_3m_inft_cont.shp, be_45122g7_3m_inft_cont.shp, be_45122g8_3m_inft_cont.shp\r\n \r\n \r\n External Hard drive\r\n \r\n \r\n \r\n 20110223\r\n \r\n \r\n publication date\r\n \r\n CONTOURS1\r\n 2 foot contours derived from output utm10_3m_bils_in_feet grids for use in Columbia County, Scappoose PAL PMR Study\r\n \r\n \r\n \r\n \r\n STARR (Strategic Alliance for Risk Reduction)\r\n 20110223\r\n be_45122f6_3m_inft.bil, be_45122f7_3m_inft.bil, be_45122f8_3m_inft.bil, be_45122g6_3m_inft.bil, be_45122g7_3m_inft.bil, be_45122g8_3m_inft.bil\r\n \r\n \r\n External Hard drive\r\n \r\n \r\n \r\n 20110223\r\n \r\n \r\n publication date\r\n \r\n REGULAR-GRID2\r\n 3 meter raster grid converted into US feet both horizontally and vertically - derived from REGULAR-GRID1 for use in Columbia County, Scappoose PAL PMR Study\r\n \r\n \r\n \r\n \r\n STARR (Strategic Alliance for Risk Reduction)\r\n 20110223\r\n topoindex_bil_3m_in_feet.shp\r\n \r\n \r\n External Hard drive\r\n \r\n \r\n \r\n 20110223\r\n \r\n \r\n publication date\r\n \r\n Other1\r\n Corner registration has been rounded to nearest 1 meter. Some of the original grids had cell corner coordinates that were about 0.000122 meters more than a round meter (e.g. about 1/8000 meter more). However a few had rounded meter registration. To enable mosaicing of the grids, they were all rounded to meter registration. This causes a maximum shift of about 1/5000 meter in some of the grids, which is very small.\r\n \r\n \r\n SinkBreach is a linear spatial file representing sink breaches used to hydrologically correct terrain models. A comparison of flow path automatically generated by a GIS software using the Elevation data and known flow paths from existing maps and/or orthophotos show sinks that need to be corrected. NoData, VoidArea, ExternalBoundary and Island are polygon spatial files by reviewing elevation datasets.\r\n 20101221\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n Universal Transverse Mercator\r\n \r\n 10\r\n \r\n 0.9996\r\n -123.0\r\n 0.0\r\n 500000\r\n 0.0\r\n \r\n \r\n \r\n \r\n coordinate pair\r\n \r\n 0.000172\r\n 0.000172\r\n \r\n meters\r\n \r\n \r\n \r\n North American Datum of 1983\r\n Geodetic Reference System 80\r\n 6378137.000000\r\n 298.257222\r\n \r\n \r\n \r\n \r\n North American Vertical Datum of 1988\r\n 0.0001\r\n meters\r\n Attribute values\r\n \r\n \r\n \r\n \r\n \r\n \r\n POINTCLOUD\r\n Post-processed bare earth point cloud data\r\n FEMA Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix M: Data Capture Standards and Data Capture Guidelines (available at http://www.fema.gov/fhm/dl_cgs.shtm)\r\n \r\n \r\n \r\n \r\n DEMGRIDS\r\n Elevation models (1 m resolution) - Breakline Enforced Bare Earth Model (ESRI GRID format) derived from post-processed bare earth point cloud data\r\n FEMA Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix M: Data Capture Standards and Data Capture Guidelines (available at http://www.fema.gov/fhm/dl_cgs.shtm)\r\n \r\n \r\n \r\n \r\n BREAKLINES\r\n Breaklines used to supplement the LiDAR data in creation of a final ground model\r\n FEMA Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix M: Data Capture Standards and Data Capture Guidelines (available at http://www.fema.gov/fhm/dl_cgs.shtm)\r\n \r\n \r\n \r\n \r\n CONTOURS\r\n A linear representation of the ground elevation at uniform intervals\r\n FEMA Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix M: Data Capture Standards and Data Capture Guidelines (available at http://www.fema.gov/fhm/dl_cgs.shtm)\r\n \r\n \r\n \r\n \r\n BILGRIDS\r\n Re-registered raster grids in .bil format re-sampled into both 1 meter and 3 meter cell sizes\r\n FEMA Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix M: Data Capture Standards and Data Capture Guidelines (available at http://www.fema.gov/fhm/dl_cgs.shtm)\r\n \r\n \r\n \r\n \r\n TOPOINDEX\r\n Index tiles based on USGS quadrangles used with the 3 meter .bil raster grids\r\n FEMA Guidelines and Specifications for Flood Hazard Mapping Partners, Appendix M: Data Capture Standards and Data Capture Guidelines (available at http://www.fema.gov/fhm/dl_cgs.shtm)\r\n \r\n \r\n \r\n The Terrain data package is made up of several data themes containing primarily spatial information. These data supplement the Elevation datasets by providing additional information to aid flood risk evaluation and flood hazard area delineations.\r\n Appendix M of FEMA Guidelines and Specifications for FEMA Flood Hazard Mapping Partners contains a detailed description of the data themes and references to other relevant information.\r\n \r\n \r\n \r\n \r\n \r\n \r\n Portland District, U.S. Army Corps of Engineers\r\n \r\n \r\n mailing\r\n
P.O. Box 2946
\r\n Portland\r\n Oregon\r\n 97208-2946\r\n USA\r\n \r\n 1-503-808-4844\r\n Jacob.Macdonald@usace.army.mil\r\n \r\n \r\n Post-processed bare earth point cloud data\r\n No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty.\r\n \r\n \r\n \r\n FEMA-DCS-Terrain\r\n \r\n \r\n \r\n \r\n \r\n http://lidar.cr.usgs.gov/\r\n \r\n \r\n \r\n \r\n \r\n No charge\r\n \r\n \r\n \r\n \r\n 20110901\r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n \r\n Federal Emergency Management Agency\r\n \r\n \r\n mailing\r\n
500 C Street, S.W.
\r\n Washington\r\n District of Columbia\r\n 20472\r\n USA\r\n \r\n 1-877-336-2627\r\n miphelp@riskmapcds.com\r\n \r\n \r\n FEMA-derived data products\r\n No warranty expressed or implied is made by FEMA regarding the utility of the data on any other system nor shall the act of distribution constitute any such warranty.\r\n \r\n \r\n \r\n FEMA-DCS-Terrain\r\n \r\n \r\n \r\n \r\n \r\n http://hazards.fema.gov\r\n \r\n \r\n \r\n \r\n \r\n Contact Distributor\r\n \r\n \r\n \r\n 20110216\r\n \r\n \r\n \r\n Kelly Durst\r\n Federal Emergency Management Agency\r\n \r\n \r\n mailing\r\n
130 228th Avenue Southwest
\r\n Bothell\r\n Washington\r\n 98021-9796\r\n USA\r\n \r\n 1-425-487-4636\r\n kelly.durst@dhs.gov\r\n \r\n \r\n FGDC Content Standards for Digital Geospatial Metadata\r\n FGDC-STD-001-1998\r\n \r\n http://hazards.fema.gov\r\n http://www.epsg.org\r\n FEMA NFIP Metadata Content and Format Standard\r\n \r\n \r\n\r\n\r\n","source_transform":null,"status":"error"}