Point clouds showing erosion in an approximately 13 km long section of the Big Sur coast, California, between two flights and projected onto topography from the second flight

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

Frequently anticipated questions:


What does this data set describe?

Title:
Point clouds showing erosion in an approximately 13 km long section of the Big Sur coast, California, between two flights and projected onto topography from the second flight
Abstract:
Presented here are point clouds of approximately 13 km of the Big Sur coastline each showing erosion (as positive values) between two dates. The point cloud coordinates reflect topography at the later date. Change detection was computed using point clouds published in this data release and developed with structure-from-motion on aerial photography collected by the U.S. Geological Survey (USGS) using an oblique plane-mounted camera system. Ground points were identified in these point clouds using LAStools and manual reclassification of some protruding rocks as ground. Non-ground points were then removed, and the point clouds were clipped to an area of interest (AOI) of the cliff face using LASTools. We used the Multiscale Model-to-Model Cloud Comparison (M3C2) tool to calculate change in the cliff face between two flights. The M3C2 point cloud is a subsampled (at 0.25-m resolution) version of the point cloud of the second flight and M3C2 distances reflect erosion that occurred between the previous flight and this flight. This point cloud was then filtered using a combination of the Visible Atmospherically Resistant Index (VARI) and manual assessment to eliminate changes that do not reflect erosion, such as vegetation changes. It was then additionally filtered to include only points that the M3C2 algorithm considered significant (low uncertainty). Point cloud contains XYZ data and the following scalar fields: G-R/G+R-B (VARI), M3C2 distance, distance uncertainty, and significant change. Point cloud coordinates are in NAD83 UTM Zone 10 meters. The AOI was created in ArcGIS Pro 3.3.1. M3C2 distances, VARI calculation, and filtering were calculated in CloudCompare v2.12.4. Note that some flight dates represented in the topographic point cloud dataset will not have an associated M3C2 file because the product showed no erosion but substantial vegetation noise and was thus excluded.
Supplemental_Information:
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this Federal Geographic Data Committee-compliant metadata file is intended to document the dataset in nonproprietary form, as well as in Esri format, this metadata file may include some Esri-specific terminology.
  1. How might this data set be cited?
    Dow, Helen W., Warrick, Jonathan A., and Ritchie, Andrew C., 20250903, Point clouds showing erosion in an approximately 13 km long section of the Big Sur coast, California, between two flights and projected onto topography from the second flight: data release DOI:10.5066/P13FEC44, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Dow, Helen W., Warrick, Jonathan A., and Ritchie, Andrew C., 2025, Topographic point clouds and change analysis for the Big Sur, California coastline from structure-from-motion photogrammetry from aerial photographs, 2017–2023: data release DOI:10.5066/P13FEC44, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: Dow, H.W., Warrick, J.A., and Ritchie, A.C., 2025, Topographic point clouds and change analysis for the Big Sur, California coastline from structure-from-motion photogrammetry from aerial photographs, 2017–2023: U.S. Geological Survey data release, https://doi.org/10.5066/P13FEC44.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -121.659423
    East_Bounding_Coordinate: -121.583232
    North_Bounding_Coordinate: 36.147515
    South_Bounding_Coordinate: 36.042181
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 25-Jan-2017
    Ending_Date: 08-Jun-2023
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: point cloud digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference:
      An approximately 13 km (8 miles) section of the Big Sur coast, Monterey County, California, from Anderson Canyon bridge to Gamboa Point.
      This is a Point 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: 10
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -123.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.01
      Ordinates (y-coordinates) are specified to the nearest 0.01
      Planar coordinates are specified in METERS
      The horizontal datum used is NAD83.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name:
      North American Vertical Datum of 1988 (EPSG:5703), derived using GEOID18
      Altitude_Resolution: 0.01
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    The attribute information associated with point cloud follows the LAZ file standard. Attributes include location (northing, easting, and elevation in the NAD83/UTM zone 10N (EPSG:26910) horizontal and NAVD88 vertical coordinate systems), VARI (G-R/G+R-B), and M3C2 outputs (M3C2 distance, distance uncertainty, and significant change).
    Entity_and_Attribute_Detail_Citation:
    American Society for Photogrammetry and Remote Sensing (ASPRS; 2013, https://www.asprs.org/committee-general/laser-las-file-format-exchange-activities.html) and Isenburg (2013, https://doi.org/10.14358/PERS.79.2.209)

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Helen W. Dow
    • Jonathan A. Warrick
    • Andrew C. Ritchie
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA
    United States

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

Data were produced to investigate the magnitude, patterns, and drivers of seacliff erosion in Big Sur as part of the USGS Remote Sensing Coastal Change (RSCC) Project.

How was the data set created?

  1. From what previous works were the data drawn?
    Structure-from-motion point clouds (source 1 of 1)
    Dow, Helen W., Warrick, Jonathan A., and Ritchie, Andrew C., 2025, Structure-from-motion point clouds of an approximately 13 km long section of the Big Sur coast, California for 33 flights between 2017-01-25 and 2023-06-08.

    Online Links:

    Type_of_Source_Media: Digital
    Source_Contribution:
    We used these point clouds to measure erosion between each flight using the Multiscale Model-to-Model Cloud Comparison tool (Lague and others, 2013).
  2. How were the data generated, processed, and modified?
    Date: 2025 (process 1 of 3)
    The point clouds were filtered and clipped to remove points representing tree canopy and not on the cliff face: 1. LAStools lasground tool was used on both point clouds to classify points as ground and non-ground points using the following command and settings: lasground_new -i temp_tiles\tile*.laz ^ -step 3.0 ^ -nature -hyper_fine ^ -bulge 1.0 ^ -offset 1.0 ^ -odir temp_tiles_ground -olaz ^ -cores %CORES% 2. Protruding rocks were reclassified as ground points using LAStools and a shapefile delineating the misclassified rocks. 3. Non-ground points were removed. 4. The point clouds were clipped to an AOI of the cliff face using LAStools. Data sources used in this process:
    • Structure-from-motion point clouds
    Data sources produced in this process:
    • processed point clouds
    Date: 2025 (process 2 of 3)
    The Multiscale Model-to-Model Cloud Comparison tool (Lague and others, 2013) was used in CloudCompare v2.12.4 to calculate distance between the two point clouds, using the second-flight point cloud subsampled at 0.25-m resolution as core points and setting the diameter for normals calculation and projected cylinder to 3 m and maximum depth to 20 m. Data sources used in this process:
    • processed point clouds
    Data sources produced in this process:
    • full M3C2 point clouds
    Date: 2025 (process 3 of 3)
    The M3C2 point clouds were filtered and clipped to reflect erosional events and not vegetation changes with the following steps: 1. The Visible Atmospherically Resistant Index or VARI, (G-R)/(G+R-B), was calculated on the core points using RGB values and interpolated onto the M3C2 point cloud. 2. Computed a histogram-based 20th percentile threshold of VARI values across the point cloud and removed all points whose VARI exceeds that threshold, effectively filtering to retain only the lowest 20 percent of VARI values. 3. All points not marked as significant change = 1 in the M3C2 output (such as, low uncertainty) were removed. 4. The final point cloud was manually checked against the first and second flight and the unfiltered M3C2 product. Any erosion that was filtered out was restored and any remaining erosion noise was removed. 5. Step 3 was repeated to remove any insignificant points that were spuriously added during the manual check. Data sources used in this process:
    • full M3C2 point clouds
  3. What similar or related data should the user be aware of?
    Lague, Dimitri, Brodu, Nicolas, and Leroux, Jérôme, 2013, Accurate 3D comparison of complex topography with terrestrial laser scanner: Application to the Rangitikei canyon (N-Z).

    Online Links:

    Other_Citation_Details:
    Lague D, Brodu N, Leroux J (2013) Accurate 3D comparison of complex topography with terrestrial laser scanner: Application to the Rangitikei canyon (N-Z). ISPRS J Photogramm Remote Sens 82:10–26. https://doi.org/10.1016/j.isprsjprs.2013.04.009

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

  1. How well have the observations been checked?
    No formal attribute accuracy tests were conducted
  2. How accurate are the geographic locations?
    Total 3D uncertainty is the same as the point cloud this change detection product is based on and is estimated at 0.5 m.
  3. How accurate are the heights or depths?
    Total 3D uncertainty is the same as the point cloud this change detection product is based on and is estimated at 0.5 m.
  4. Where are the gaps in the data? What is missing?
    Data set is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    Coordinates recorded for each point in the point cloud describe discrete positions in space at the time of capture and change in space between two data collection days. This final point cloud was checked for accuracy by rotating the point cloud to view from multiple angles to ensure that obvious spurious points do not cause artifacts in measurements or derivative products. Although some outlying points were eliminated during processing, there may still be points that do not represent ground features but are instead artifacts generated by erroneous tie points or spurious matches in the photogrammetric process.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints No access constraints
Use_Constraints USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey as the originator(s) of the dataset and in products derived from these data.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - CMGDS
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov
  2. What's the catalog number I need to order this data set? These data are available in LAZ format contained in a single zip file (BigSur_M3C2_PointClouds.zip) accompanied by CSDGM FGDC-compliant metadata.
  3. What legal disclaimers am I supposed to read?
    Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data on any other system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: This zip file contains 27 point clouds in LAZ format (LAS 1.2 specification). in format LAZ (version LAS 1.2) Size: 514.8
      Network links: https://doi.org/10.5066/P13FEC44
    • Cost to order the data: None.

  5. What hardware or software do I need in order to use the data set?
    This zip file contains point clouds in LAZ format (LAS 1.2 specification). The user must have software capable of uncompressing the .zip compressed file and displaying or processing the .laz format file.

Who wrote the metadata?

Dates:
Last modified: 03-Sep-2025
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA
United States

831-427-4747 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/CMGDS_DR_tool/DR_P13FEC44/BigSur_M3C2_metadata.faq.html>
Generated by mp version 2.9.51 on Tue Sep 9 17:04:02 2025