USGS CoastCam at Sand Key, Florida: Intrinsic and Extrinsic Calibration Data (Camera 2)

Frequently anticipated questions:

• What does this data set describe?
  1. How might this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
• Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
• Why was the data set created?
• How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  3. What similar or related data should the user be aware of?
• How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
• How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
• Who wrote the metadata?

What does this data set describe?

1. How might this data set be cited?
   Brown, Jenna A., Birchler, Justin J., Palmsten, Margaret L., Swanson, Eric, Johnson, Emily L., and Buckley, Mark, 20240510, USGS CoastCam at Sand Key, Florida: Intrinsic and Extrinsic Calibration Data (Camera 2):.

   This is part of the following larger work.
   Brown, Jenna A., Birchler, Justin J., Palmsten, Margaret L., Swanson, Eric, Johnson, Emily L., and Buckley, Mark, 20240510, USGS CoastCam at Sand Key, Florida: Imagery and Calibration Data: U.S. Geological Survey data release doi:10.5066/P146YVZF, U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center, St. Petersburg, Florida.

   Online Links:

   • https://doi.org/10.5066/P146YVZF

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -82.86191282
   East_Bounding_Coordinate: -82.81953572
   North_Bounding_Coordinate: 27.97774890
   South_Bounding_Coordinate: 27.93943384
   

3. What does it look like?

   sandkey_c2_calibrationIOEO_exampleImagery.zip (JPEG)

   Zip file containing the following example Joint Photographic Experts Group (JPEG) images: A) Image used in intrinsic orientation (IO) calibration (sandkey_c2_20180413_IO_01.jpg) and B) Image used in extrinsic orientation (EO) calibration (sandkey_c2_20180419_GCP_image_annotated.jpg) and the target numbers for use in the Coastal Imaging Research Network (CIRN) Toolbox that correspond to the numbers in the sandkey_c2_20180419_EO_GCPsurvey.csv (file available in sandkey_c2_20180419_EO.zip).

4. Does the data set describe conditions during a particular time period?

   Calendar_Date: 13-Apr-2018

   Currentness_Reference:

   ground condition

5. What is the general form of this data set?

   Geospatial_Data_Presentation_Form: tabular digital data, raster 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: 17
      Transverse_Mercator:

      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -81.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      

      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 1
      Ordinates (y-coordinates) are specified to the nearest 1
      Planar coordinates are specified in meters
      The horizontal datum used is NAD83_National_Spatial_Reference_System_2011.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      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?

   sandkey_c2_20180413_IO.yaml

   YAML file containing the solved intrinsic orientation (IO) from step A in the Camera Calibration procedures outlined in Bruder and Brodie (2020). (Source: USGS)

   NU

   the number of pixel columns (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	2448
   Maximum:	2448
   Units:	pixel

   NV

   the number of pixel rows (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	2048
   Maximum:	2048
   Units:	pixel

   coU

   U component of principal point (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	1223.5
   Maximum:	1223.5
   Units:	pixel

   coV

   V component of principal point (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	1023.5
   Maximum:	1023.5
   Units:	pixel

   fx

   U component of focal length in pixels (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	2266.8051636784126
   Maximum:	2266.8051636784126
   Units:	pixels

   fy

   V component of focal length in pixels (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	2215.4085846383377
   Maximum:	2215.4085846383377
   Units:	pixels

   d1

   First radial distortion coefficient (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	-0.16009436427277812
   Maximum:	-0.16009436427277812

   d2

   Second radial distortion coefficient (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	0.017466106905264379
   Maximum:	0.017466106905264379

   d3

   Thrid radial distortion coefficient (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	0.069413829075082922
   Maximum:	0.069413829075082922

   t1

   First tangential distortion coefficient (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	-0.010543634060619429
   Maximum:	-0.010543634060619429

   t2

   Second tangential distortion coefficient (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	-0.00938964262142645
   Maximum:	-0.00938964262142645

   sandkey_c2_20180419_EO_GCPsurvey.csv

   CSV file containing the location (x,y,z) of the ground control points (black and white targets) in the CoastCam field of view. (Source: USGS)

   GCP

   Number of each GCP that can be found in sandkey_c2_20180419_GCP_image_annotated.jpg so that targets can be labeled correctly in Step B of Camera Calibration steps in Bruder and Brodie (2020). (Source: U.S. Geological Survey)

   Range of values
   Minimum:	1
   Maximum:	13

   Easting (NAD83, UTM 17N)

   Real-Time Kinematic (RTK) X-coordinates in NAD83(2011)/UTM Zone 17N (Source: U.S. Geological Survey)

   Range of values
   Minimum:	319009.7376
   Maximum:	319158.0446
   Units:	meters

   Northing (NAD83, UTM 17N)

   Real-Time Kinematic (RTK) Y-coordinates in NAD83(2011)/UTM Zone 17N (Source: U.S. Geological Survey)

   Range of values
   Minimum:	3091852.993
   Maximum:	3092158.831
   Units:	meters

   Elevation (NAVD88, orthometric)

   Real-Time Kinematic (RTK) Z-coordinates in NAD83(2011)/UTM Zone 17N referenced to NAVD88, in meters. A positive z value is the up direction. (Source: U.S. Geological Survey)

   Range of values
   Minimum:	0.689
   Maximum:	2.147
   Units:	meters

   Latitude (NAD83)

   Latitude (decimal degrees) in NAD83 (2011) (Source: U.S. Geological Survey)

   Range of values
   Minimum:	27.93941912
   Maximum:	27.94219466
   Units:	decimal degrees

   Longitude (NAD83)

   Longitude (decimal degrees) in NAD83(2011) (Source: U.S. Geological Survey)

   Range of values
   Minimum:	-82.83957534
   Maximum:	-82.83811376
   Units:	decimal degrees

   Elevation (NAD83, ellipsoidal)

   Real-Time Kinematic (RTK) Z-coordinates in NAD83(2011)/UTM Zone 17N referenced to NAVD88, in meters. A positive z value is the up direction. (Source: U.S. Geological Survey)

   Range of values
   Minimum:	-23.8566
   Maximum:	-22.3940
   Units:	meters

   gcpUsed

   Indicates whether GCP was used to solve for extrinsic orientation. (Source: U.S. Geological Survey)

   Value	Definition
   0	Not used
   1	Used

   Description

   Location of each ground control point (GCP) placed within the camera's field of view (FOV) to solve for extrinsic orientation. (Source: U.S. Geological Survey) GCP locations within the camera's FOV

   sandkey_c2_20180419_EO.yaml

   YAML file containing the solved extrinsic orientation (EO) from Step C in the Camera Calibration procedures outlined in Bruder and Brodie (2020). (Source: USGS)

   x

   camera X-coordinate, Easting in NAD83(2011)/UTM Zone 17N of camera position on rooftop. (Source: U.S. Geological Survey)

   Range of values
   Minimum:	319032.382864662
   Maximum:	319032.382864662
   Units:	meters

   y

   camera Y-coordinate, Northing in NAD83(2011)/UTM Zone 17N of camera position on rooftop. (Source: U.S. Geological Survey)

   Range of values
   Minimum:	3091814.727631580
   Maximum:	3091814.727631580
   Units:	meters

   z

   camera Z-coordinate, elevation referenced to NAVD88 in meters of GEOID12B. (Source: U.S. Geological Survey)

   Range of values
   Minimum:	38.349157895
   Maximum:	38.349157895
   Units:	meters

   azimuth

   The horizontal direction the camera is pointing and positive clockwise (CW) from World Y Axis. (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	359.663133
   Maximum:	359.663133
   Units:	Angle units in degrees

   tilt

   The up/down tilt of the camera. 0 is the camera looking nadir, 90 is the camera looking at the horizon right side up, and 180 is looking directly up. (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	70.268933
   Maximum:	70.268933
   Units:	Angle units in degrees

   roll

   The side-to-side tilt of the camera. 0 degrees is a horizontal flat camera. Looking from behind the camera, counterclockwise (CCW) rotation of the camera would result in a positive roll. (Source: Bruder and Brodie (2020))

   Range of values
   Minimum:	0
   Maximum:	0
   Units:	Angle units in degrees

   Entity_and_Attribute_Overview:

   There are a total of 30 intrinsic orientation (IO) JPEG images. The filename for each IO image is formatted as "sandkey_c2_20180413_IO_##", where the number (##) is the original photo ID. There are 15 extrinsic orientation (EO) JPEG images (sandkey_c2_20180419_GCP_image_raw.jpg, sandkey_c2_20180419_GCP_image_annotated.jpg, and sandkey_c2_20180419_GCP##.jpg for GCPs 1-13). These images have EXIF and other imagery header information encoded within each file, see the process steps for more information.

   Entity_and_Attribute_Detail_Citation:

   The entity and attribute information were generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

   Entity_and_Attribute_Overview:

   To place the photos taken by the CoastCam into real world coordinates and to rectify them into a planar view, objects within the field of view of the camera must be located. The elevation and position of the lenses in the CoastCam setup were measured with the RTK GPS. The CoastCam took pictures of the position of each target within the camera view. The '_EO' zip folder contains the GCP CSV file, the resultant EO parameters in a YAML file, 'raw' and 'annotated' images showing all the GCPs, and individual images of the target at each GCP location. The CSV file (sandkey_c2_20180419_EO_GCPsurvey.csv) with all the measurements were populated and GCP numbers were hand labeled on the annotated images (sandkey_c2_20180419_GCP_image_annotated.jpg) so that the targets could be labeled correctly in Step B of the Camera Calibration steps in Bruder and Brodie (2020). There are a total of 15 JPEGs. Images have EXIF and other imagery header information encoded within each file, see the process steps for more information.

   Entity_and_Attribute_Detail_Citation:

   The entity and attribute information were generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
   • Jenna A. Brown
   • Justin J. Birchler
   • Margaret L. Palmsten
   • Eric Swanson
   • Emily L. Johnson
   • Mark Buckley
2. Who also contributed to the data set?
3. To whom should users address questions about the data?
   Justin J. Birchler

   U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center

   Physical Scientist

   600 4th Street South

   Saint Petersburg, FL
   

   USA

   727-502-8019 (voice)

   jbirchler@usgs.gov

Why was the data set created?

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: 13-Apr-2018 (process 1 of 4)

   The CoastCam was used to take IO photos. This involves slightly tilting a printed checkerboard with 2.7-centimeter (cm) squares in various parts of the cameras field of view. An example image can be found in sandkey_c1_calibrationIOEO_exampleImagery.zip. There are a total of 30 IO images (sandkey_c2_20180413_IO.zip) used for the intrinsic calibration. These were used in step A in the Camera Calibration procedures outlined in Bruder and Brodie (2020). The resultant parameters are stored in a YAML file located in sandkey_c2_20180413_IO.zip. Image file naming format follows “sandkey_c2_20180413_IO_##”, where sandkey is the site name, c2 is the camera name, 20180413 is the date the images were taken (YYYYMMDD format), IO is Intrinsic Orientation, and ## is the original unique ID from the camera. Person who carried out this activity:
   

   Justin J. Birchler

   U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center

   Physical Scientist

   600 4th Street South

   Saint Petersburg, FL
   

   USA

   727-502-8019 (voice)

   jbirchler@usgs.gov

   Data sources produced in this process:

   • sandkey_c2_20180413_IO_##.jpg
   • sandkey_c2_20180413_IO.yaml

   Date: 29-Feb-2024 (process 2 of 4)

   Extrinsic orientation (EO) calibration ground control points (GCPs) were surveyed with a Spectra Precision SP80 Global Navigation Satellite System (GNSS) Real-Time Kinematic (RTK) receiver. GCPs were collected on 20180419. To place the photos taken by the CoastCam into real world coordinates and to rectify them into a planar view, objects within the field of view of the camera must be located. To do so, the elevation and position of the camera lenses in the CoastCam setup were measured with the RTK GPS. Then, a single large square target (1.2 m by 1.2 m) painted white and black in opposite quadrants was propped up to face the CoastCam setup at multiple locations within the camera field-of-view to collect ground control points. At each GCP location, a snapshot was taken with the camera of the position of the target (sandkey_c2_20180419_GCP##.jpg); additionally, the bottom-center of the target (between black and white, at ground level) was measured with the RTK GPS equipment. A single image showing all GCP locations (sandkey_c2_20180419_GCP_image_raw.jpg) was made by creating a “dark” image using all of the snapshots of the target. The survey locations of the GCPs in the CSV file was used to hand label the raw image to generate an annotated image (sandkey_c2_20180419_GCP_image_annotated.jpg) so that the targets could be labeled correctly in Step B of the Camera Calibration steps in Bruder and Brodie (2020). The pixel coordinates of each GCP within the raw images (hand-selected at bottom-center of targets), solved in Step B of Bruder and Brodie (2020), the GPS positions from the CSV files, and the IO parameters in the IO YAML file were used in Step C of the Camera Calibration steps in Bruder and Brodie (2020) to solve for the EO parameters. The resultant parameters for the EO calibration are stored in a YAML file located in “sandkey_c2_20180419_EO.zip”. Person who carried out this activity:
   

   Justin J. Birchler

   U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center

   Physical Scientist

   600 4th Street South

   Saint Petersburg, FL
   

   USA

   727-502-8019 (voice)

   jbirchler@usgs.gov

   Data sources used in this process:

   • sandkey_c2_20180419_EO.yaml
   • sandkey_c2_20180419_EO_GCPsurvey.csv
   • sandkey_c2_20180419_GCP_image_raw.jpg

   Data sources produced in this process:

   • sandkey_c2_20180419_GCP_image_annotated.jpg
   • sandkey_c2_20180419_EO.yaml

   Date: 13-Mar-2024 (process 3 of 4)

   All intrinsic calibration images were given additional information required by the USGS to the exchangeable image file format (EXIF) and other imagery headers using PyExifTool Python library (https://pypi.org/project/PyExifTool/, version: 0.5.6). All intrinsic photos were given EXIF header information in the directory with all the photos by assigning all the tags in a Python dictionary object to each photo using PyExifTool. The following describes the Python dictionary object with each entry in the dictionary being a tag-value pair: tags = { 'Copyright': 'Public Domain', 'CopyrightNotice': 'Public Domain - please credit U.S. Geological Survey', 'Artist': 'USGS SPCMSC', 'Make': 'FLIR','Model': 'BFLY-PGE-50S5C-C','UserComment': UserComment, 'GPSLatitude': '27.9391', 'GPSLongitude': '-82.8393', 'GPSMapDatum': 'EPSG:6318 (NAD83_National_Spatial_Reference_System_2011)', 'GPSLatitudeRef': 'N', 'GPSLongitudeRef': 'W', 'Credit': 'U.S. Geological Survey', 'Contact': 'gs-g-spcmsc_data_inquiries@usgs.gov', 'UsageTerms': "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", 'AttributionURL': 'https://doi.org/10.5066/P146YVZF ', 'Contributor': 'Jenna A. Brown, Justin J. Birchler, Margaret L. Palmsten, Eric Swanson, Emily L. Johnson, Mark Buckley', 'XMP-photoshop:Credit': 'U.S. Geological Survey', 'iptcCore:CreatorWorkEmail': 'gs-g-spcmsc_data_inquiries@usgs.gov','Rights': 'Public Domain', 'Keywords' : "Sand Key, Florida, CoastCam, USGS, intrinsic calibration, snapshot, remote sensing ", 'ImageDescription': 'This image was captured from a stationary mounted camera at Sand Key, Florida. Field Activity Number: 2018-302-DD (https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-302-DD) Other FANs referenced in calibration metadata: https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-328-FA, 'Description': 'This image was captured from a stationary mounted camera at Sand Key, Florida. Field Activity Number: 2018-302-DD (https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-302-DD) Other FANs referenced in calibration metadata: https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-328-FA}. The UserComment EXIF metadata field was used to store the camera intrinsics and extrinsics in the image metadata. The UserComment has a nested dictionary structure. The highest-level dictionary contains two nested dictionaries as well as a note explaining the structure of the UserComment field. One nested dictionary contains the actual intrinsic and extrinsic data variables. The other nested dictionary contains text descriptions for each of the variables in the dictionary of data variables. To read out the imagery header information to a CSV file the command is: 'exiftool -csv *.jpg > allheaders.csv'. Specific tags may be specified with this command, if preferred. Person who carried out this activity:
   

   Justin J. Birchler

   U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center

   Physcical Scientist

   600 4th Street South

   Saint Petersburg, FL
   

   USA

   727-502-8019 (voice)

   jbirchler@usgs.gov

   Data sources produced in this process:

   • sandkey_c2_20180413_IO_##.jpg

   Date: 13-Mar-2024 (process 4 of 4)

   All extrinsic calibration ground control point images were given additional information required by the USGS to the exchangeable image file format (EXIF) and other imagery headers using PyExifTool Python library (https://pypi.org/project/PyExifTool/, version: 0.5.6). All extrinsic photos were given EXIF header information in the directory with all the photos by assigning all the tags in a Python dictionary object to each photo using PyExifTool. The following describes the Python dictionary object with each entry in the dictionary being a tag-value pair: tags = { 'Copyright': 'Public Domain', 'CopyrightNotice': 'Public Domain - please credit U.S. Geological Survey', 'Artist': 'USGS SPCMSC', 'Make': 'FLIR','Model': 'BFLY-PGE-50S5C-C','UserComment': UserComment, 'GPSLatitude': '27.9391', 'GPSLongitude': '-82.8393', 'GPSMapDatum': 'EPSG:6318 (NAD83_National_Spatial_Reference_System_2011)', 'GPSLatitudeRef': 'N', 'GPSLongitudeRef': 'W', 'Credit': 'U.S. Geological Survey', 'Contact': 'gs-g-spcmsc_data_inquiries@usgs.gov', 'UsageTerms': "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", 'AttributionURL': 'https://doi.org/10.5066/P146YVZF ', 'Contributor': 'Jenna A. Brown, Justin J. Birchler, Margaret L. Palmsten, Eric Swanson, Emily L. Johnson, Mark Buckley', 'XMP-photoshop:Credit': 'U.S. Geological Survey', 'iptcCore:CreatorWorkEmail': 'gs-g-spcmsc_data_inquiries@usgs.gov','Rights': 'Public Domain', 'Keywords' : "Sand Key, Florida, CoastCam, USGS, extrinsic calibration, remote sensing, ground control point", 'ImageDescription': 'This image was captured from a stationary mounted camera at Sand Key, Florida. Field Activity Number: 2018-302-DD (https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-302-DD) Other FANs referenced in calibration metadata: https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-328-FA, 'Description': 'This image was captured from a stationary mounted camera at Sand Key, Florida. Field Activity Number: 2018-302-DD (https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-302-DD) Other FANs referenced in calibration metadata: https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-328-FA}. The only tag which can have a different value from image to image is GPSDateStamp. Depending on the date the photo was captured, the value in the GPSDatestamp tag changes. The UserComment EXIF metadata field was used to store the camera intrinsics and extrinsics in the image metadata. The UserComment has a nested dictionary structure. The highest-level dictionary contains two nested dictionaries as well as a note explaining the structure of the UserComment field. One nested dictionary contains the actual intrinsic and extrinsic data variables. The other nested dictionary contains text descriptions for each of the variables in the dictionary of data variables. To read out the imagery header information to a CSV file the command is: 'exiftool -csv *.jpg > allheaders.csv'. Specific tags may be specified with this command, if preferred. Person who carried out this activity:
   

   Justin J. Birchler

   U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center

   Physical Scientist

   600 4th Street South

   Saint Petersburg, FL
   

   USA

   727-502-8019 (voice)

   jbirchler@usgs.gov

   Data sources produced in this process:

   • sandkey_c2_20180419_GCP_image_raw.jpg
   • sandkey_c2_20180419_GCP_image_annotated.jpg
   • sandkey_c2_20180419_ GCP##.jpg

3. What similar or related data should the user be aware of?
   Bruder, Brittany L., and Brodie, Katherine L., 20200909, CIRN Quantitative Coastal Imaging Toolbox: Elsevier SoftwareX, Online.

   Online Links:

   • https://doi.org/10.1016/j.softx.2020.100582

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

1. How well have the observations been checked?
   Extrinsic orientation (EO) calibration ground control points (GCPs) were surveyed with a Spectra Precision SP80 Global Navigation Satellite System (GNSS) Real-Time Kinematic (RTK) receiver. Calibration success can be examined using the CIRN Toolbox (Bruder and Brodie, 2020) where parameters azimuth, tilt, and roll have errors less than 2 degrees. Accuracy of the extrinsic calibration was also tied to human ability to locate targets in the imagery. The camera systems were liable to move over time via wind, wear, and human interactions cleaning the camera – all of which may change the camera calibration parameters. Calibration data is stored in YAML files named with the calibration date..
2. How accurate are the geographic locations?
   RTK equipment with decimeter horizontal accuracy collected data in field activity 2018-328-FA was used to validate the extrinsic camera calibration. The precise locations of the targets are used in the CIRN Quantitative Coastal Imaging Toolbox steps B and C (Bruder and Brodie, 2020). Horizontal coordinates are referenced to the North American Datum of 1983 (National Spatial Reference System 2011) Universal Transverse Mercator Zone 17 North (NAD83(2011)/UTM Zone 17N) coordinate system.
3. How accurate are the heights or depths?
   RTK equipment with centimeter vertical accuracy collected in field activity 2018-328-FA was used to validate the extrinsic camera calibration. The precise locations of the targets are used in the CIRN Quantitative Coastal Imaging Toolbox steps B and C (Bruder and Brodie, 2020). Vertical positions are referenced to the North American Vertical Datum of 1988 (NAVD88) coordinate system.
4. Where are the gaps in the data? What is missing?
   All calibration images and surveyed GCPs are provided even if not all are necessary for calibrating the camera.
5. How consistent are the relationships among the observations, including topology?
   The camera system installed (FLIR Blackfly 5.0MP Color GiGE PoE, BFLY-PGE-50S5C-C) had an intrinsic and extrinsic calibration process. The EO process was completed on 20180419 and consists of a YAML file of resultant EO parameters, a comma-separated values (CSV) file of GCP locations and description, and two JPEG images, one labeled as 'raw' and the other as 'annotated'. The intrinsic orientation (IO) calibration consists of 30 images that collectively covered the entire image frame and the extrinsic calibration uses one “darkest” photo with GCP targets that have surveyed location information. These were used in the CIRN Toolbox steps A through C. Results of the intrinsic and extrinsic calibrations are stored in separate YAML files (sandkey_c2_20180413_IO.yaml, and sandkey_c2_20180419_EO.yaml).

How can someone get a copy of the data set?

1. Who distributes the data set? (Distributor 1 of 1)
   
   USGS SPCMSC Data Management Group

   U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center

   600 4th Street South

   St. Petersburg, Florida
   

   USA

   727-502-8000 (voice)

   gs-g-spcmsc_data_inquiries@usgs.gov
2. What's the catalog number I need to order this data set? sandkey_c2_20180413_IO.yaml, sandkey_c2_20180413_IO_##.jpg, sandkey_c2_20180419_EO.yaml, sandkey_c2_20180419_EO_GCPsurvey.csv, sandkey_c2_20180419_GCP_image_annotated.jpg, sandkey_c2_20180419_GCP_image_raw.jpg, sandkey_c2_20180419_GCP##.jpg
3. What legal disclaimers am I supposed to read?
   This publication was prepared by an agency of the United States Government. 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. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although these data have been processed successfully on a computer system at 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. The USGS or the U.S. Government shall not be held liable for improper or incorrect use of the data described and/or contained herein.
4. How can I download or order the data?
   • Availability in digital form:

     Data format:	JPEG, YAML, comma-delimited text
     Network links:	https://coastal.er.usgs.gov/data-release/doi-P146YVZF/data/sandkey_c2_20180413_IO.zip https://coastal.er.usgs.gov/data-release/doi-P146YVZF/data/sandkey_c2_20180419_EO.zip https://coastal.er.usgs.gov/data-release/doi-P146YVZF/data/sandkey_c2_calibrationIOEO_exampleImagery.zip

   • Cost to order the data: None

Who wrote the metadata?

Dates:

Last modified: 10-May-2024

Metadata author:

USGS SPCMSC Data Management Group

U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center

600 4th Street South

Saint Petersburg, FL

USA

727-502-8000 (voice)

gs-g-spcmsc_data_inquiries@usgs.gov

Metadata standard:

Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)