Skydio elevation model, orthomosaic, imagery, and GCP data collected during UAS operations at Marconi Beach, CACO, Wellfleet, MA on September 25, 2024

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

Frequently anticipated questions:

What does this data set describe?

Title:
Skydio elevation model, orthomosaic, imagery, and GCP data collected during UAS operations at Marconi Beach, CACO, Wellfleet, MA on September 25, 2024
Abstract:
Surveys with Uncrewed Systems (UxS) were used to collect remote sensing data at Marconi Beach on Cape Cod National Seashore, Wellfleet, Massachusetts after the area experienced multiple erosion events after fall storms in 2024 and the loss of National Park Service beach access stairs. The USGS has a stationary camera system (CoastCam) and meteorological station north of the parking lot on the bluff to observe waves and total water levels. UxS were approved to map the coast in view of the CoastCam and where the Park Service stairs were destroyed to help evaluate the conditions of the site and monitor landscape change from storm impacts. The data products will also help validate the CoastCam imagery datasets. Between September 2024 and March 2025, USGS personnel surveyed five times and collected natural (RGB) color images, lidar data, GPS data, and bathymetric data to produce elevation maps and orthomosaics.
  1. How might this data set be cited?
    Over, Jin-Si R., and Brosnahan, Sandra M., 20251126, Skydio elevation model, orthomosaic, imagery, and GCP data collected during UAS operations at Marconi Beach, CACO, Wellfleet, MA on September 25, 2024: data release DOI:10.5066/P1Z9NCQX, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Over, Jin-Si R., Brosnahan, Sandra M., Cramer, Jennifer M., Sherwood, Chris R., and Traykovski, Peter A., 2025, Topographic and bathymetric data, aerial imagery, and GPS data collected during UxS operations at Marconi Beach, Cape Cod National Seashore, Massachusetts between September 2024 and March 2025: data release DOI:10.5066/P1Z9NCQX, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Over, J.R., Brosnahan, S.M., Cramer, J.M., Sherwood, C.R., and Traykovski, P.A., 2025, Topographic and bathymetric data, aerial imagery, and GPS data collected during UxS operations at Marconi Beach, Cape Cod National Seashore, Massachusetts between September 2024 and March 2025: U.S. Geological Survey data release, https://doi.org/10.5066/P1Z9NCQX.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -69.96526389
    East_Bounding_Coordinate: -69.96167778
    North_Bounding_Coordinate: 41.89761389
    South_Bounding_Coordinate: 41.88827222
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/67854ebad34ec3ce63796a29?name=2024-024-FA_Marconi_Sep_BrowseGraphic.png&allowOpen=true (JPEG)
    Data and products of Marconi Beach in September 2024: Digital elevation model, orthomosaic, and example images (oblique and nadir).
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 25-Sep-2024
    Currentness_Reference:
    Ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: raster and tabular digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the 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: 19
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -69.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 0.001
      Ordinates (y-coordinates) are specified to the nearest 0.001
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum of 1983 (National Spatial Reference System 2011).
      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
      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?
    2024024FA_Marconi_Sep_ImageLocations.csv
    The CSV file contains the approximate position of the SX10 images at the moment of each capture. (Source: producer defined)
    ImageName
    File names of individual images, see the Process Description for file naming convention. (Source: USGS) Character string.
    GPSDateTime
    Date and UTC time in YYYY:MM:DD HH:MM:ss (Source: Processor defined) Character string.
    Latitude NAD83[2011]
    Latitude (x) of UAS based on time of each image capture. Positive values represent North coordinates. (Source: USGS)
    Range of values
    Minimum:41.88827222
    Maximum:41.89761389
    Units:decimal degrees
    Longitude NAD83[2011]
    Longitude (y) of UAS based on time of each image capture. Negative values represent West coordinates. (Source: USGS)
    Range of values
    Minimum:-69.96526389
    Maximum:-69.96167778
    Units:decimal degrees
    Ellipsoid height NAD83[2011]
    Altitude of the UAS position at the time of each image capture relative to the NAD83(2011) reference ellipsoid GRS80. (Source: USGS)
    Range of values
    Minimum:-2.249
    Maximum:67.554
    Units:meters
    Easting 19N
    Post-processed X-coordinate of UAS position at the time of each image capture relative to NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:419930.576
    Maximum:420216.670
    Units:meters
    Northing 19N
    Post-processed Y-coordinate of UAS position at the time of each image capture relative to NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4637819.069
    Maximum:4638858.295
    Units:meters
    Orthometric height NAVD88
    Post-processed Z-coordinate of the UAS at the time of each image capture relative to NAVD88 with GEOID 18 applied. (Source: USGS)
    Range of values
    Minimum:25.553
    Maximum:95.354
    Units:meters
    2024024FA_Marconi_Sep_AeroPoints.csv
    Ground control point positions, elevations, and attributes (Source: USGS)
    FAN
    USGS Field Activity Number (Source: USGS)
    ValueDefinition
    2024-024-FAYear, USGS ID, and Field Activity
    Date
    Calendar date of collection (Source: USGS)
    ValueDefinition
    20240925YYYYMMDD
    Point ID
    Unique point identification number. (Source: Processor defined)
    Range of values
    Minimum:1
    Maximum:5
    Attributes
    Unique identifier for ground control points. Prefix AP-### refers to AeroPoint and the last 3 digits of its identifying code. (Source: producer defined) Character string.
    Latitude NAD83[2011]
    Post-processed latitude of AeroPoint position (NAD83[2011]). (Source: USGS)
    Range of values
    Minimum:41.89114597
    Maximum:41.89330016
    Units:decimal degrees
    Longitude NAD83[2011]
    Post-processed longitude of AeroPoint position (NAD83[2011]). (Source: USGS)
    Range of values
    Minimum:-69.96358921
    Maximum:-69.96282441
    Units:decimal degrees
    Ellipsoid height NAD83[2011]
    Post-processed height in meters of AeroPoint in relation to the NAD83(2011) reference ellipsoid GRS80. (Source: USGS)
    Range of values
    Minimum:-14.466
    Maximum:-10.877
    Units:meters
    Easting 19N
    Post-processed interpolated X-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:420063.602
    Maximum:420125.004
    Units:meters
    Northing 19N
    Post-processed interpolated Y-coordinate of AeroPoint in NAD83(2011)/UTM Zone 19N. (Source: USGS)
    Range of values
    Minimum:4638138.548
    Maximum:4638378.294
    Units:meters
    Orthometric height NAVD88
    Post-processed Z-coordinate of AeroPoint using NAVD88 with GEOID 18 applied. (Source: USGS)
    Range of values
    Minimum:13.235
    Maximum:16.922
    Units:meters
    Xvar mm
    Variance in the X-coordinate from post-processing (Source: producer defined)
    Range of values
    Minimum:2.4
    Maximum:5.7
    Units:millimeters
    Yvar mm
    Variance in the Y-coordinate from post-processing (Source: producer defined)
    Range of values
    Minimum:3.4
    Maximum:6.0
    Units:millimeters
    Zvar mm
    Variance in the Z-coordinate from post-processing (Source: producer defined)
    Range of values
    Minimum:6.9
    Maximum:13.1
    Units:millimeters
    Baseline distance km
    Distance of AeroPoint from nearest Propellor network base station (Source: Propeller)
    Range of values
    Minimum:0.06
    Maximum:11.80
    Units:kilometers
    2024024FA_Marconi_Sep_SX10_DSM_5cm.tif
    Cloud-optimized digital surface model created using SfM. Pixel resolution is 5 cm. No-data value is –999. (Source: USGS)
    Value
    Surface elevation in EPSG:5703 using GEOID 18. (Source: producer defined)
    Range of values
    Minimum:-0.016
    Maximum:23.667
    Units:meters
    2024024FA_Marconi_Sep_SX10_Ortho_5cm.tif
    Cloud-optimized true-color (RGB) orthomosaic. (Source: USGS)
    Band_1
    Red wavelength band (Source: Agisoft Metashape)
    Range of values
    Minimum:0
    Maximum:255
    Band_2
    Green wavelength band (Source: Agisoft Metashape)
    Range of values
    Minimum:0
    Maximum:255
    Band_3
    Blue wavelength band (Source: Agisoft Metashape)
    Range of values
    Minimum:0
    Maximum:255
    Entity_and_Attribute_Overview:
    The filenames are formatted as "2024024FA_Marconi_Sep_sensor/product_resolution.*** ", where 2024024 is the USGS Field activity ID, location is Marconi Beach (Marconi), Sep is month of data collection, sensors are Skydio (SX10) and AeroPoints and products include orthomosaic and DSM.
    Entity_and_Attribute_Detail_Citation: USGS Field Activity 2024-024-FA

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Jin-Si R. Over
    • Sandra M. Brosnahan
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Jin-Si R. Over
    U.S. Geological Survey, Northeast Region, Woods Hole Coastal and Marine Science Center
    Geographer
    384 Woods Hole Rd.
    Woods Hole, MA

    508-548-8700 x2297 (voice)
    jover@usgs.gov

Why was the data set created?

The natural-color imagery from a Skydio uncrewed aerial system (UAS) and AeroPoint data collected from September are used to create structure-from-motion (SfM) products: a digital surface model and orthomosaic. The products from this date were produced to evaluate the effects of the nor’easter on September 22, 2024 that destroyed the stairs and will help monitor landscape change from storm impacts. Supplemental_Information: For more information about the WHCMSC Field Activity, see https://cmgds.marine.usgs.gov/services/activity.php?fan=2024-024-FA. Images can be viewed or downloaded on the USGS Imagery Data System here https://cmgds.marine.usgs.gov/idsviewer/data_release/10.5066-P1Z9NCQX in the collection 2024_Marconi_Sep_SX10. Note that the bounding coordinates are for the entire area mapped and not individual files, the orthomosaic and digital surface model cover a smaller area.

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: 25-Sep-2024 (process 1 of 5)
    GROUND CONTROL: Five AeroPoint2 GCPs were spaced out over the field site and left on for at least 30 minutes to collect GNSS data. After collection the AeroPoint2s data were uploaded via a Wi-Fi connection and run through a post-processing kinematic algorithm of the Propeller Correction network to get corrected positions. The data were exported in NAD83(2011) (EPSG:6318) to produce latitude, longitude, and ellipsoid heights, and then NAD83(2011)/UTM zone 19N (EPSG:6348) and NAVD88 (EPSP:5703) with GEOID 18 to produce easting and northing and orthometric heights. These were exported to a CSV file and named 2024024FA_Marconi_Sep_AeroPoints.csv. Step processed by S. Brosnahan, J. Over, and C. Sherwood.
    Date: 25-Sep-2024 (process 2 of 5)
    UAS FLIGHTS: The Skydio X10 is a small UAS with an integrated VT300-L camera system. The radiometric thermal camera is a FLIR Boson+ with less than 30 millikelvin sensitivity and takes a 0.3 megapixel (MP) image. The Skydio X10 also has two RGB cameras, one has a 50-degree field of view (narrow) that takes a 64 MP image and the second has a 93-degree field of view (wide) that takes a 50 MP image. A flight in auto mapping mode was flown at 5 m/s at 60 meters above ground level (AGL) with 70% desired sidelap and overlap and 1.21 cm ground sampling distance using only the wide camera. A second flight was flown manually between 55-65 meters AGL with the wide camera tilted to look at the bluff obliquely, the speed varied between 2-7 m/s. Note, the SX10 geotagged positions embedded in the imagery Exif information were in native WGS84 (EPSG:4326) and GEOID EGM96 (EPSG:5773). The positions were converted to EPSG:6348 and EPSG:5703 in the processing software and the converted positions are reported in the imagery locations file (2024024FA_Marconi_Sep_ImageLocations.csv) and represented in the final SfM products. Step processed by S. Brosnahan.
    Date: 04-Jan-2025 (process 3 of 5)
    RAW IMAGERY: All images were processed to add additional information required by the USGS to the EXIF headers using ExifTools (https://exiftool.org/, version: 12.06), and the files were renamed to a unique identifier using Namexif (http://www.digicamsoft.com/softnamexif.html, version 2.1) to avoid any possibility of duplicate names. 1. ExifTools was used to tag each photo headers following the Imagery Data System Exif Guidance. Attributes (e.g. Credit, Copyright, UsageTerms, ImageDescription, Artist, etc) were stored in a csv file and written to each image with the command:' exiftool -csv="C:\directory\name\EXIF.csv" C:\directory\name\of\photos *.JPG ' To read out the photo information to a csv when in the directory with the photos the command is: exiftool -csv *.JPG > directory/name/allheaders_out.csv 2. All the images were renamed with Namexif (https://us.digicamsoft.com/softnamexif.html v 2.2 accessed April 2020) to ensure unique filenames and compliance with the USGS Coastal and Marine Hazards and Resources Program's best practices for image naming convention. Images were renamed with the field survey ID prefix; flight number, and ID that distinguishes USGS cameras by make/camera number, the image acquisition date, coordinated universal time (UTC) in ISO8601 format, and a suffix with the original image name. For example, image name '2024024FA_f01SX10c_20240925T165822Z_IMG_####_#', 2024024FA is the field activity ID; f01 is the flight number; SX10c are the Skydio RGB images; 20240925 is the UTC date in the format YYYYMMDD, and a 'T' is used to separate UTC date from UTC time in format HHMMSS followed by a Z. The IMG_#### is the original raw photo name appended to the end of the new filename. 3. Images are validated and uploaded onto the Imagery Data System. 4. The 2024024FA_Marconi_Sep_ImageLocations.csv was created with the exif command: exiftool –ImageName –GPSDateTime –csv *.JPG > .\2024024FA_Marconi_Sep_ImageLocations.csv Step processed by J. Over.
    Date: 15-Jan-2025 (process 4 of 5)
    PHOTOGRAMMETRY: The SfM products were created in Agisoft Metashape v. 2.1.4 using the following general steps (see Over and others, 2021 for a more detailed SfM methodology explanation) 1. A project was created and imagery, geotagged from UAS FLIGHTS, was imported and assigned the WGS84 (EPSG:4326) and GEOID EGM96 (EPSG:5773) reference systems and then were immediately converted to EPSG: 6318 and then EPSG:6348 and EPSG:5703. These converted positions were added to the 2024024FA_Marconi_Sep_ImageryLocations.csv. 2. Photos were aligned at a low accuracy and then GCPs were automatically detected in the point cloud. GCP positions (2024024FA_Marconi_Sep_AeroPoints.csv) were added to the project in the reference systems EPSG:6348 and EPSG:5703 using GEOID 18. The horizontal and vertical accuracies for the GCPs were set to 0.01/0.02 m, respectively, and the camera positions for the images were turned off. The photos were then re-aligned with high accuracy (the pixels were not subsampled) using a keypoint limit of 60,000 and unlimited tie points. 3. The alignment process matched pixels between images to create point clouds and put the imagery into a relative spatial context using the GCPs. The resultant point clouds were filtered using one iteration of the 'Reconstruction uncertainty' filter at a level of 13, one iteration of the 'Projection accuracy' filter at a level of 3, and three iterations of the 'Reprojection accuracy' filter to get to a level of 1. With each filter, iteration points are selected, deleted, and then the camera model was optimized to refine the focal length, cx, cy, k1, k2, k3, p1, and p2 camera model coefficients. 4. At this point, for each project multiple ‘chunks’ were created so that independent high quality dense clouds with a low-frequency filtering algorithm could be made. The dense point clouds were then edited by visual inspection to remove points with a low confidence near the edges and near water bodies. 5. The working region was resized to smaller area surrounding the focus area and AeroPoint2s. A interpolated DSM was built from the dense point cloud and then an orthomosaic was built from the DSM with refined seamlines. The SX10 orthomosaic is a 3-band orthomosaic exported at 5 cm resolution (2024024FA_Marconi_Sep_SX10_Ortho_5cm.tif). A non-interpolated DSM was built from the dense point cloud and exported at 5 cm resolution (2024024FA_Marconi_Sep_SX10_DSM_5cm.tif). Step processed by J. Over.
    Date: 15-Jan-2025 (process 5 of 5)
    CLOUD OPTIMIZATION: All GeoTIFF products were Deflate compressed and turned into a cloud-optimized GeoTIFFs (COG) using gdal_translate with the following command: for %i in (.\*.tif) do gdal_translate %i .\cog\%~ni.tif -of COG -stats -co BLOCKSIZE=256 -co COMPRESS=DEFLATE -co PREDICTOR=YES -co NUM_THREADS=ALL_CPUS -co BIGTIFF=YES (v. 3.1.4 accessed October 20, 2020 https://gdal.org/). Where i is the name of each GeoTIFF section. Step processed by J. Over. Person who carried out this activity:
    Jin-Si R. Over
    U.S. Geological Survey, Woods Hole Coastal and Marine Science Center
    Geographer
    U.S. Geological Survey
    Woods Hole, MA

    508-548-8700 x2297 (voice)
    jover@usgs.gov
  3. What similar or related data should the user be aware of?
    Over, Jin-Si R., Ritchie, Andrew C., Kranenburg, Christine J., Brown, Jenna A., Buscombe, Daniel D., Noble, Tom, Sherwood, Christopher R., Warrick, Jonathan A., and Wernette, Phillipe A., 2021, Processing coastal imagery with Agisoft Metashape Professional Edition, version 1.6-Structure from motion workflow documentation: Open-File Report 2021-1039, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    This publication includes the general methodology for processing imagery in Metashape to produce digital surface models and ortho products.

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

  1. How well have the observations been checked?
    GPS: The AeroPoint2 GCPs have an internal reported variance provided in 2024024FA_Marconi_Sep_AeroPoints.csv, the global accuracy was calculated and reported below by adding the variance to two times the longest baseline distance.
    GeoTIFFs: The horizontal and vertical accuracy of the products (2024024FA_Marconi_Sep_SX10_Ortho_5cm.tif and 2024024FA_Marconi_Sep_SX10_DSM_5cm.tif) were assessed using the AeroPoint2 ground control points (GCPs). It should also be noted that accuracy estimates of the products are for areas of bare ground or low vegetation where GCPs were placed. Additional sources of error, such as moving objects, may cause accuracy estimates to exceed estimates in localized portions of the products. The vertical bias of the structure from motion (SfM) elevation surface away from the AeroPoint2s was evaluated against the USGS 3DEP (https://www.usgs.gov/3d-elevation-program) surface.
  2. How accurate are the geographic locations?
    Images: The SX10 individual image xy accuracies were tagged by the UAS GPS and embedded in the Exif information and were less than 1 meter.
    GPS: AeroPoint2 x and y global accuracy is 3 cm.
    SfM: The orthomosaic and DSM were spatially georeferenced using AeroPoint2 GCPs (n=5) and created using SfM in Agisoft Metashape. The horizontal RMSE of the GCPs as reported from the Metashape project was x/y 0.023/0.014 m.
  3. How accurate are the heights or depths?
    Images: The SX10 images were geotagged by the UAS and had a z accuracy around 2 meters.
    GPS: AeroPoint global vertical accuracy is 4 cm.
    SfM: The SfM DSM was assessed against the elevations of the AeroPoint2s, and the vertical RMSE of the GCPs (n=5) as reported from the Metashape projects was 0.029. The DSM was also compared to the USGS 3DEP surface. Values are within 20 cm but start to increase towards the edges away from the AeroPoint2s.
  4. Where are the gaps in the data? What is missing?
    Imagery: The SX10 cameras triggered automatically every 2 seconds for the nadir flight, camera was triggered manually for the oblique flight and timing varies. Images at takeoff and landing were removed. A total of 367 SX10 images were used in the photogrammetry processing. Products: The GeoTIFF products are cloud-optimized and Deflate compressed. The total area covered by the UAS photos was much larger than where the AeroPoint2 GCPs were placed (n=5), leading to less accurate results on the outer edges of the SfM surfaces, beyond (~100 meters) the GCP placement. To reduce the extent of the errors the extent of the final product was cropped to a smaller area covered by the AeroPoint2s but still encompasses the areas in view of the CoastCam.
  5. How consistent are the relationships among the observations, including topology?
    There were 2 UAS flights and five AeroPoint2 GCPs. The first flight (18 min) used the Skydio X10 (SX10) to collect RGB nadir images, the second flight (15 min) was used to collect oblique images. The images were processed using SfM to produce a true-color orthomosaic (Ortho) and digital surface model (DSM).

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. Please see 'Distribution Information' for details.
Use_Constraints These data are marked with a Creative Commons CC0 1.0 Universal License. These data are in the public domain and do not have any use constraints. Users are advised to read the dataset's metadata thoroughly to understand appropriate use and data limitations. Please recognize the U.S. Geological Survey (USGS) as the source of this information. These data are not intended for navigational use.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - ScienceBase
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? Aerial imaging and mapping of Marconi Beach includes the imagery, SfM products, and AeroPoint2 ground control points.
  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 for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Not for navigational use.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 26-Nov-2025
Metadata author:
Jin-Si R. Over
U.S. Geological Survey, Northeast Region
Geographer
U.S. Geological Survey
Woods Hole, MA

508-548-8700 x2297 (voice)
whsc_data_contact@usgs.gov
Contact_Instructions:
The metadata contact email address is a generic address in the event the person is no longer with USGS.
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P1Z9NCQX/2024-024-FA_Marconi_Sep_metadata.faq.html>
Generated by mp version 2.9.51 on Mon Dec 1 10:15:44 2025