Lidar-derived elevation models for Homer, Alaska

Metadata also available as - [Parseable text] - [XML]

Frequently anticipated questions:


What does this data set describe?

Title: Lidar-derived elevation models for Homer, Alaska
Abstract:
The Alaska Division of Geological & Geophysical Surveys (DGGS) used lidar to produce digital terrain models (DTM), a digital surface model (DSM), and an intensity model for Homer, Alaska. Detailed bare earth elevation data for Homer were collected and processed for use in a landslide hazard resiliency project for the City of Homer. Data coverage includes neighboring Kachemak City. Lidar and Global Navigation Satellite System (GNSS) data were collected on June 3, 2019, and subsequently processed using TerraSolid and ArcGIS. The Alaska Division of Mining Land & Water (DMLW) Survey Section conducted a targeted Ground Control Survey for this project on June 19-20, 2019. These data are being released as a Raw Data File with an open end-user license. All files can be downloaded free of charge from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/30591).
Supplemental_Information:
classified point cloud data:    Classified point cloud data is provided in this collection in compressed *.LAZ format. Data are classified in accordance with ASPRS 2014 guidelines and contain return and intensity information. Elevation surfaces interpolated from areas with a point density of fewer than 4 pts/m2 were classified as no data.	
digital surface model:    DSMs represent surface elevations as they appear to the naked eye. They include the heights of vegetation, buildings, bridges, etc. The DSM is a single band, 32-bit GeoTIFF file, with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038.	
digital terrain model:    DTMs represent surface elevations of ground surfaces, achieved by penetrating or flattening any vegetation, bridges, buildings, and other non-ground features. The DTM is a single-band, 32-bit float GeoTIFF file, with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038.	
hydro-enforced digital terrain model:    The hydro-flattened DTM represents bare earth surfaces which have undergone a selective flattening process, where elevation values for any hydrologic features are replaced with a consistent, appropriate pixel (elevation) value. The hydro-enforced DTM is a single-band, 32-bit float GeoTIFF file, with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038.	
lidar intensity image:    The lidar intensity image describes the relative amplitude of reflected signals contributing to the point cloud. Lidar intensity is largely a function of scanned object reflectance in relation to the signal frequency, is dependent on ambient conditions, and is not necessarily consistent between separate scans. The intensity image is a single-band, 32-bit float GeoTIFF file with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038 (32-bit, floating-point minimum).
  1. How might this data set be cited?
    Salisbury, J.B., Daanen, R.P., and Herbst, A.M., 2021, Lidar-derived elevation models for Homer, Alaska: Raw Data File RDF 2021-2, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 6 p.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -151.732364
    East_Bounding_Coordinate: -151.373102
    North_Bounding_Coordinate: 59.709396
    South_Bounding_Coordinate: 59.598820
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 03-Jun-2020
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: report, point cloud, GeoTIFF
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a raster data set.
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 5
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -153
      Latitude_of_Projection_Origin: 0
      False_Easting: 500000.000000
      False_Northing: 0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest .00000001
      Ordinates (y-coordinates) are specified to the nearest .00000001
      Planar coordinates are specified in Meters
      The horizontal datum used is NAD83.
      The ellipsoid used is GRS 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257222101000025.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: NAVD88, GEOID12B
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    classified point cloud data
    Classified point cloud data is provided in this collection in compressed *.LAZ format. Data are classified in accordance with ASPRS 2014 guidelines and contain return and intensity information. Elevation surfaces interpolated from areas with a point density of fewer than 4 pts/m2 were classified as no data. (Source: Alaska Division of Geological & Geophysical Surveys (DGGS))
    digital surface model
    DSMs represent surface elevations as they appear to the naked eye. They include the heights of vegetation, buildings, bridges, etc. The DSM is a single band, 32-bit GeoTIFF file, with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038. (Source: Alaska Division of Geological & Geophysical Surveys (DGGS))
    digital terrain model
    DTMs represent surface elevations of ground surfaces, achieved by penetrating or flattening any vegetation, bridges, buildings, and other non-ground features. The DTM is a single-band, 32-bit float GeoTIFF file, with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038. (Source: Alaska Division of Geological & Geophysical Surveys (DGGS))
    hydro-enforced digital terrain model
    The hydro-flattened DTM represents bare earth surfaces which have undergone a selective flattening process, where elevation values for any hydrologic features are replaced with a consistent, appropriate pixel (elevation) value. The hydro-enforced DTM is a single-band, 32-bit float GeoTIFF file, with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038. (Source: Alaska Division of Geological & Geophysical Surveys (DGGS))
    lidar intensity image
    The lidar intensity image describes the relative amplitude of reflected signals contributing to the point cloud. Lidar intensity is largely a function of scanned object reflectance in relation to the signal frequency, is dependent on ambient conditions, and is not necessarily consistent between separate scans. The intensity image is a single-band, 32-bit float GeoTIFF file with a ground sample distance of 0.5 meters. No Data value is set to -3.40282306074e+038 (32-bit, floating-point minimum). (Source: Alaska Division of Geological & Geophysical Surveys (DGGS))

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?
    These data were collected and processed by the Alaska Division of Geological & Geophysical Surveys staff with funding by the Federal Emergency Management Agency (FEMA) through Cooperating Technical Partnership (CTP) with the City of Homer and AK DGGS under federal grant number CTP EMS-2018-CA-00016-S01.
  3. To whom should users address questions about the data?
    Alaska Division of Geological & Geophysical Surveys
    Metadata Manager
    3354 College Road
    Fairbanks, AK
    USA

    (907)451-5020 (voice)
    (907)451-5050 (FAX)
    dggspubs@alaska.gov
    Hours_of_Service: 8 am to 4:30 pm, Monday through Friday, except State holidays
    Contact_Instructions:
    Please view our website (https://www.dggs.alaska.gov) for the latest information on available data. Please contact us using the e-mail address provided above when possible.

Why was the data set created?

Detailed bare earth elevation data for Homer were collected and processed for use in a landslide hazard resiliency project for the City of Homer. Data coverage includes neighboring Kachemak City. This data release is one of a series of DGGS publications to present elevation data.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 03-Jun-2020 (process 1 of 3)
    Airborne survey - DGGS operates a Riegl VUX1-LR laser scanner with a GNSS and Northrop Grumman Inertial Measurement Unit (IMU). The integration was designed by Phoenix LiDAR systems. The sensor can collect up to 820,000 points per second over a 150 m range. We flew the instrument with a repetition rate of 400,000 pulses per second, a scan speed of 200 revolutions per second, at approximately 200 m above ground level, and at a ground speed of approximately 40 meters per second with a fixed-wing Cessna 185. The scan look angle operated between 55 and 305 degrees. The total data coverage is approximately 98 km2. DGGS collected lidar data on June 3, 2019, initiating the GNSS base station at 08h48 and flying from 10h15 to 15h35 with a 15-minute refuel at 14h15. The sky was clear with light, easterly winds. Heavy air traffic precluded sufficient scanning of the southwestern portion of Beluga Lake and an area southeast of the Homer Airport runway (along Kachemak Drive).
    Date: 20-Jun-2020 (process 2 of 3)
    Ground survey - The Alaska Division of Mining, Land, & Water Survey Section collected 79 points in a targeted Ground Control Survey in Homer on June 19-20, 2019.
    Date: 2020 (process 3 of 3)
    Lidar dataset processing - DGGS processed raw data by first using SDCImport to apply range thresholding, reflectance thresholding, and missed-time-around (MTA) disambiguation for preliminary point cloud noise filtering. We coupled in-flight IMU and GNSS data in Inertial Explorer to produce flight trajectory data and coupled the trajectory data with the raw point cloud in Spatial Explorer. We then used Terrasolid to calibrate point cloud data using tielines for roll, pitch, and yaw of the aircraft during the survey. We completed this process first for all points, then on a per-flight-line basis. For additional calibration, we identified interswath fluctuations in preliminarily-classified ground points using overlapping tielines. We classified the point cloud in accordance with American Society for Photogrammetry and Remote Sensing (ASPRS) guidelines using project-tailored macros, resulting in a ground points class, as well as low, medium, and high vegetation (0.01-0.3 m, 0.3-5 m, and 5-60 m heights above the ground, respectively). Misclassified points were manually reclassified in post-processing QA/QC. We eliminated all low points and air points from the dataset and manually identified some buildings under dense vegetation, particularly in areas of complex terrain. We hydro-flattened the Bridge Creek Reservoir, Beluga Lake, and Lampert Lake to specified elevations. Lastly, we converted the point cloud from ellipsoidal to orthometric heights using GEOID 12B, then uniformly adjusted the dataset to maintain a mean offset of 0 m with collected ground control. All derivative products were created in ArcMap. The DTM and DSM were produced using point triangulation with nearest-neighbor interpolation. The DTM was derived from all returns for ground classified points, while the DSM used first returns for all non-noise classes. A lidar intensity image was created from first returns of all classes using mean binning.
  3. What similar or related data should the user be aware of?
    Reger, R.D., 1978, Bluff Point landslide, a massive ancient rock failure near Homer, Alaska: Geologic Report GR 61B, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: p. 5-9
    Stevens, D.S.P., Wolken, G.J., Hubbard, T.D., and Hendricks, K.A., 2018, Landslides in Alaska: Information Circular IC 65, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 2 p
    Stevens, D.S.P., 2019, The Engineering Geology section at DGGS: Information Circular IC 76, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 2 p
    Suleimani, E.N., Nicolsky, D.J., and Salisbury, J.B., 2019, Updated tsunami inundation maps for Homer and Seldovia, Alaska: Report of Investigation RI 2018-5 v. 2, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 97 p., 11 sheets

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Not applicable
  2. How accurate are the geographic locations?
    Horizontal accuracy was not measured for this collection.
  3. How accurate are the heights or depths?
    The non-vegetated vertical accuracy for classified ground point data is a root mean square error of 3.1 cm. The average pulse spacing is 18.56 cm and the average point density is 29 points per square meter. See accompanying report for more detail.
  4. Where are the gaps in the data? What is missing?
    This dataset is a partial release of the June 3, 2019 lidar project. After the refuel stop, the survey moved across Kachemak Bay to scan the north-facing flank of the Grewingk Glacier valley (the site of a 1967 landslide into the proglacial lake). Data covering the Grewingk Glacier landslide scar will be published separately. However, data quality portrayed here for Homer and Kachemak is consistent throughout the entire dataset.
  5. How consistent are the relationships among the observations, including topology?
    The relative accuracy for this dataset is 10.38 cm RMSE, calculated as the interswath consistency. Heavy air traffic precluded sufficient scanning of the southwestern portion of Beluga Lake and an area southeast of the Homer Airport runway (along Kachemak Drive). The low-quality data at the southwest end of Beluga Lake has been clipped and flattened to lake level. The tests and processing methods used to ensure data consistency are further described in the accompanying report.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints:
This report, map, and/or dataset is available directly from the State of Alaska, Department of Natural Resources, Division of Geological & Geophysical Surveys (see contact information below).
Use_Constraints:
Any hard copies or published datasets utilizing these datasets shall clearly indicate their source. If the user has modified the data in any way, the user is obligated to describe the types of modifications the user has made. The user specifically agrees not to misrepresent these datasets, nor to imply that changes made by the user were approved by the State of Alaska, Department of Natural Resources, Division of Geological & Geophysical Surveys. The State of Alaska makes no express or implied warranties (including warranties for merchantability and fitness) with respect to the character, functions, or capabilities of the electronic data or products or their appropriateness for any user's purposes. In no event will the State of Alaska be liable for any incidental, indirect, special, consequential, or other damages suffered by the user or any other person or entity whether from the use of the electronic services or products or any failure thereof or otherwise. In no event will the State of Alaska's liability to the Requestor or anyone else exceed the fee paid for the electronic service or product.
  1. Who distributes the data set? (Distributor 1 of 1)
    Alaska Division of Geological & Geophysical Surveys
    Metadata Manager
    3354 College Road
    Fairbanks, AK
    USA

    (907)451-5020 (voice)
    (907)451-5050 (FAX)
    dggspubs@alaska.gov
    Hours_of_Service: 8 am to 4:30 pm, Monday through Friday, except State holidays
    Contact_Instructions:
    Please view our website (https://www.dggs.alaska.gov) for the latest information on available data. Please contact us using the e-mail address provided above when possible.
  2. What's the catalog number I need to order this data set? RDF 2021-2
  3. What legal disclaimers am I supposed to read?
    The State of Alaska makes no expressed or implied warranties (including warranties for merchantability and fitness) with respect to the character, functions, or capabilities of the electronic data or products or their appropriateness for any user's purposes. In no event will the State of Alaska be liable for any incidental, indirect, special, consequential, or other damages suffered by the user or any other person or entity whether from the use of the electronic services or products or any failure thereof or otherwise. In no event will the State of Alaska's liability to the Requestor or anyone else exceed the fee paid for the electronic service or product.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 27-Jan-2021
Metadata author:
Alaska Division of Geological & Geophysical Surveys
Attn: Simone Montayne
Metadata Manager
3354 College Road
Fairbanks, AK
USA

(907)451-5020 (voice)
(907)451-5050 (FAX)
dggspubs@alaska.gov
Hours_of_Service: 8 am to 4:30 pm, Monday through Friday, except State holidays
Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:

Generated by mp version 2.9.50 on Tue Jan 26 22:24:35 2021