Photogrammetry-derived orthoimagery and elevation data for Kivalina, Alaska, collected June 7, 2922

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

Frequently anticipated questions:


What does this data set describe?

Title:
Photogrammetry-derived orthoimagery and elevation data for Kivalina, Alaska, collected June 7, 2922
Abstract:
Photogrammetry-derived orthoimagery and elevation data for Kivalina, Alaska, collected June 7, 2922, Raw Data File 2022-12, uses low-altitude aerial images, collected from an unmanned aerial vehicle (UAV) on June 7, 2022, and Structure-from-Motion (SfM) photogrammetry to produce a digital surface model (DSM) and orthoimagery for the community of Kivalina, Alaska. The orthoimage and elevation data are for assessing coastal hazards and changes. We used Trimble Business Center to process the Global Navigation Satellite System (GNSS) data used for positional control and NOAA VDatum to adjust elevation data. We used Agisoft Metashape to process photogrammetry data. These products are released as a Raw Data File with an open end-user license. All files can be downloaded from the Alaska Division of Geological & Geophysical Surveys website (http://doi.org/10.14509/30902).
Supplemental_Information:
digital surface model:    The DSM represents surface elevations such as the height of vegetation and buildings. We filtered the dense cloud to remove low confidence points with less than three contributing image renderings containing distance information. Since water bodies can introduce noise, we manually delineated the beach boundaries to restrict the DSM to land only. Boundaries were identified using both visual selection from collected aerial images and point confidence. The DSM is a single-band, 32-bit floating point GeoTIFF file with a GSD of 0.031 m. The No Data value is set to -3.4028231 x 10^38.	
orthoimagery:    The orthoimage is a three-band (red, green, blue), 8-bit unsigned GeoTIFF file with a GSD of 0.016 m per pixel; the No Data value is set to 256.
  1. How might this data set be cited?
    Horen, K.C., and Siemsen, Z.J., 2022, Photogrammetry-derived orthoimagery and elevation data for Kivalina, Alaska, collected June 7, 2922: Raw Data File RDF 2022-12, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 5 p.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -164.550548
    East_Bounding_Coordinate: -164.524463
    North_Bounding_Coordinate: 67.731827
    South_Bounding_Coordinate: 67.722733
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 22-Jul-2022
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: data
  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: 3
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -165
      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 (2011).
      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.257222101.
      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?
    digital surface model
    The DSM represents surface elevations such as the height of vegetation and buildings. We filtered the dense cloud to remove low confidence points with less than three contributing image renderings containing distance information. Since water bodies can introduce noise, we manually delineated the beach boundaries to restrict the DSM to land only. Boundaries were identified using both visual selection from collected aerial images and point confidence. The DSM is a single-band, 32-bit floating point GeoTIFF file with a GSD of 0.031 m. The No Data value is set to -3.4028231 x 10^38. (Source: DGGS)
    orthoimagery
    The orthoimage is a three-band (red, green, blue), 8-bit unsigned GeoTIFF file with a GSD of 0.016 m per pixel; the No Data value is set to 256. (Source: 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 products were funded by the National Coastal Resilience Fund. We thank the City and Native Village of Kivalina for supporting the creation of these data products.
  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?

The orthoimage and elevation data were collected for assessing coastal hazards and changes.

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: 22-Jul-2022 (process 1 of 3)
    Aerial photogrammetric survey - DGGS used a DJI Phantom 4 RTK UAV with a FC6310R camera model (8.8 mm lens) to collect 20-megapixel JPEG photographs (5472 x 3648 pixels per image). We flew the aerial survey with 70 percent sidelap and 80 percent frontlap, 91 m above ground-level at 6.5 m/s, with nadir orientation stabilized using a 3-axis gimbal. This resulted in images covering 0.56 km2 with ground sampling distance (GSD) of 0.016 m. DGGS conducted flights on June 7, 2022, from approximately 7:45 PM to 8:30 PM AKDT. The operator returned the UAV two times to change batteries. The weather throughout the survey was clear with light wind. No abnormalities were observed during the flights.
    Date: 2022 (process 2 of 3)
    Ground survey - DGGS set up a GNSS base station using the Trimble R10 receiver sampling at 5 Hz. The base was installed over known benchmark KVL A with a published solution (found at https://www.ngs.noaa.gov/cgi-bin/ds_mark.prl?PidBox=DN5562). This provided real-time kinematic (RTK) corrections to the Trimble R8s GNSS receiver (ground rover). The corrected base position was derived using the Canadian Spatial Reference System Precision Point Positioning (CSRS-PPP) service (found at https://webapp.csrs-scrs.nrcan-rncan.gc.ca/geod/tools-outils/ppp.php). The R8s' positions were updated using post-processed kinematic (PPK) corrections in Trimble Business Center. DGGS measured 19 photo-identifiable ground control points (GCPs) with the ground rover, 11 of which were utilized for georeferencing during processing. The remaining eight were reserved for quality control checks.
    Date: 2022 (process 3 of 3)
    Photogrammetric dataset processing - During the survey, the UAV maintained RTK connection. Within the UAV GNSS receiver settings, the lever arm correction is automatically applied and camera GNSS coordinates are written to the image metadata in WGS84 ellipsoid. Yaw, pitch, and roll information are not written to the image metadata. During processing we update UAV positions using an X, Y, and Z shift from the initial to corrected base position. DGGS processed using Agisoft Metashape Professional software (Version 1.6.3 build 10732). We masked image corners where shadows and image warping were disruptive. Processing steps included aligning images, identifying GCPs, manually cleaning sparse point cloud, optimizing the bundle block adjustment (refining camera position and lens distortion parameters), constructing the dense point cloud, building the DSM, and creating the orthomosaic image. During processing, we used 11 GCPs to create the model, leaving eight GCPs as horizontal and vertical check points.
  3. What similar or related data should the user be aware of?
    Buzard, R.M., Overbeck, J.R., and Maio, C.V., 2019, Community-based methods for monitoring coastal erosion: Information Circular IC 84, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 35 p
    Overbeck, J.R., 2018, Coastal flooding & erosion in Alaska: Information Circular IC 68, Alaska Division of Geological & Geophysical Surveys, Fairbanks, Alaska, United States.

    Online Links:

    Other_Citation_Details: 2 p

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?
    We quantify the horizontal accuracy of the DSM and orthoimage by comparing the known locations of eight photo-identifiable check points measured with GNSS against their modeled locations in the photogrammetric products. These are independent checkpoints not used in processing. X and Y errors are calculated as the root-mean-square (RMS) error of offsets. The total horizontal error is the root-sum-square error of X and Y RMS errors, 0.042 m. See accompanying report for a table of checkpoints and further discussion of factors impacting the certainty of data locations.
  3. How accurate are the heights or depths?
    We assess the vertical accuracy of the DSM using the same check points. The RMS error of Z offsets is 0.066 m. The total error of the DSM (X, Y, and Z) is 0.078 m. See the accompanying report for check points and additional detail.
  4. Where are the gaps in the data? What is missing?
    This data relaease is complete.
  5. How consistent are the relationships among the observations, including topology?
    DGGS visually inspected the orthoimage for data errors such as shifts, seamline mismatches, and water noise overlapping land. There were no significantly erroneous areas that required repair. Visual errors common to these SfM photogrammetry products include discontinuous powerlines, blurriness near high-angle features like buildings, and distortion at water boundaries. Bright objects like metal roofs and white paint can cause overexposure, leading to spurious elevation points.

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 2022-12
  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-Oct-2022
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 Thu Oct 27 13:39:52 2022