Sound velocity profile data from an AML Oceanographic MVP30 and Minos X collected in Cape Cod Bay, Massachusetts during USGS Field Activity 2019-002-FA (PNG images, SVP text, and point shapefile, GCS WGS 84)

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

Frequently anticipated questions:

What does this data set describe?

Title:
Sound velocity profile data from an AML Oceanographic MVP30 and Minos X collected in Cape Cod Bay, Massachusetts during USGS Field Activity 2019-002-FA (PNG images, SVP text, and point shapefile, GCS WGS 84)
Abstract:
Accurate data and maps of sea floor geology are important first steps toward protecting fish habitat, delineating marine resources, and assessing environmental changes due to natural or human impacts. To address these concerns the U.S. Geological Survey, in cooperation with the Massachusetts Office of Coastal Zone Management (CZM), comprehensively mapped the Cape Cod Bay sea floor to characterize the surface and shallow subsurface geologic framework. Geophysical data collected include swath bathymetry, backscatter, and seismic reflection profile data. Ground-truth data, including sediment samples, underwater video, and bottom photographs were also collected. This effort is part of a long-term collaboration between the USGS and the Commonwealth of Massachusetts to map the State’s waters, support research on the Quaternary evolution of coastal Massachusetts, the influence of sea-level change and sediment supply on coastal evolution, and efforts to understand the type, distribution, and quality of subtidal marine habitats. This collaboration produces high-resolution geologic maps and Geographic Information System (GIS) data that serve the needs of research, management and the public. Data collected as part of this mapping cooperative continue to be released in a series of USGS Open-File Reports and Data Releases (https://www.usgs.gov/centers/whcmsc/science/geologic-mapping-massachusetts-seafloor). This data release provides the geophysical and geologic sampling data collected in Cape Cod Bay during USGS Field Activities 2019-002-FA and 2019-034-FA in 2019.
Supplemental_Information:
Support for 2019-002-FA was provided to the USGS from the Massachusetts Office of Coastal Zone Management. Additional information on the field activities associated with this project are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-002-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-034-FA.
  1. How might this data set be cited?
    Ackerman, Seth D., 20220718, Sound velocity profile data from an AML Oceanographic MVP30 and Minos X collected in Cape Cod Bay, Massachusetts during USGS Field Activity 2019-002-FA (PNG images, SVP text, and point shapefile, GCS WGS 84): data release DOI:10.5066/P99DR4PN, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, Massachusetts.

    Online Links:

    This is part of the following larger work.

    Ackerman, Seth D., Foster, David S., Andrews, Brian D., Danforth, William W., Baldwin, Wayne E., Huntley, Emily C., Worley, Charles R., and Brothers, Laura L., 2022, High-resolution geophysical and geological data collected in Cape Cod Bay, Massachusetts during USGS Field Activities 2019-002-FA and 2019-034-FA: data release DOI:10.5066/P99DR4PN, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman, S.D., Foster, D.S., Andrews, B.D., Danforth, W.W., Baldwin, W.E., Huntley, E.C., Worley, C.R., and Brothers, L.L., 2022, High-resolution geophysical and geological data collected in Cape Cod Bay, Massachusetts during USGS Field Activities 2019-002-FA and 2019-034-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P99DR4PN.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.49556
    East_Bounding_Coordinate: -70.10639
    North_Bounding_Coordinate: 42.02083
    South_Bounding_Coordinate: 41.74917
  3. What does it look like?
    https://cmgds.marine.usgs.gov/data-releases/media/2021/10.5066-P99DR4PN/ce9d118ab85e4d0fbbf5411c6a1b9015/2019-002-FA_MVPSVP_data_browse.jpg (JPEG)
    Thumbnail image of sound speed profile locations collected in Cape Cod Bay, Massachusetts.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Aug-2019
    Ending_Date: 29-Aug-2019
    Currentness_Reference:
    ground condition during field activity 2019-002-FA: 20190801-20190829
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: PNG images, ASCII text, and Shapefile
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Entity point (439)
    2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.0000054863. Longitudes are given to the nearest 0.000007073695. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257224.
  7. How does the data set describe geographic features?
    2019-002-FA_MVPSVP_data.shp
    Sound velocity locations collected in Cape Cod Bay during USGS Field Activity 2019-002-FA. (Source: U.S. Geological Survey)
    Lon
    Decimal degree longitude value in GCS WGS 84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:-70.495560
    Maximum:-70.106390
    Units:degrees
    Resolution:.000001
    Lat
    Decimal degree latitude value in GCS WGS 84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:42.020830
    Maximum:41.749170
    Units:degrees
    Resolution:.000001
    MVPSVP
    Name of sound velocity profile used to distinguish between casts. Profile names are in the format: cast_2019237_001400 "cast__yyyyjjj_hhmmss", where 'cast' indicates moving vessel profiler or sound velocity cast, 'yyyy' indicates the year, 'jjj' indicates the Julian day, and 'hhmmss' indicates the time of the cast. (Source: U.S. Geological Survey) Character set
    Date
    Month/Day/Year when the sound velocity cast was collected. (Source: U.S. Geological Survey) Character set
    JD_UTC
    Julian day and UTC time when the sound velocity cast was collected in the format: JD:HH:MM; Julian day is the integer number (although recorded here in text string format) representing the interval of time in days since January 1 of the year of collection. (Source: U.S. Geological Survey) Character set
    SurveyID
    WHCMSC field activity identifier (e.g. "2019-002-FA" where 2019 is the survey year, 002 is survey number of that year, and FA is Field Activity). (Source: U.S. Geological Survey) Character set
    VehicleID
    Survey vessel name. (Source: U.S. Geological Survey) Character set
    DeviceID
    Device used to collect sound speed profile data. (Source: U.S. Geological Survey) Character set
    2019-002-FA_MVPSVP_SVP
    Sound velocity profile data in CARIS SVP ASCII format for survey 2019-002-FA (439 SVP files) (Source: U.S. Geological Survey)
    2019-002-FA_MVPSVP_Images
    Portable network graphic images of sound velocity profile data for survey 2019-002-FA (439 PNG files) (Source: U.S. Geological Survey)
    Entity_and_Attribute_Overview:
    The PNG images can be hyperlinked to their shapefile location in ArcGIS using the field called MVPSVP. The graphs show depth on the y-axis and speed of sound on the x-axis. The format of the CARIS SVP files is as follows: Header line 1:[SVP_VERSION_2] - the standard CARIS SVP header line; Header line 2:filename; Header line 3:Section YYYY-JJJ HH:MM:SS DD:MM:SS -DD:MM:SS where YYYY is the year, JJJ is the Julian day, HH:MM:SS is the UTC time, DD:MM:SS is the latitude (in degrees, minutes, seconds) and -DD:MM:SS is the longitude (in degrees, minutes, seconds). The header is followed by column data of depth (meters) and speed of sound (meters per second).
    Entity_and_Attribute_Detail_Citation: U.S. Geological Survey

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Seth D. Ackerman
  2. Who also contributed to the data set?
    The authors acknowledge our fellow participants of the Cape Cod Bay field activities 2019-002-FA (Walter Barnhardt, Luke Bennett, Eric Moore, Alex Nichols, Jake Fredericks, and Dan Kennedy) and 2019-034-FA (Dann Blackwood, Eric Moore, and Alex Nichols); the crew of the M/V Warren Jr and the R/V Tioga; and our sea floor mapping group onshore support team during these surveys (Jane Denny, PJ Bernard, Barry Irwin, and Emile Bergeron).
  3. To whom should users address questions about the data?
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov

Why was the data set created?

This dataset is used to display the locations of sound velocity profiles collected with an AML MVP30 (moving vessel profiler) and an AML Minos X SVP (sound velocity profiler) during survey 2019-002-FA in Cape Cod Bay, Massachusetts. The information contained within the sound velocity profiles is needed to account for refraction artifacts that may be present within raw swath bathymetric data. This dataset contains graphs of the sound velocity profile at each station location, as well as location in Geographic Coordinate System (GCS) WGS 84 latitude and longitude, time of day and date of collection.

How was the data set created?

  1. From what previous works were the data drawn?
    raw sound velocity data (source 1 of 1)
    U.S. Geological Survey, Unpublished Material, Sound Velocity Data.

    Type_of_Source_Media: disc
    Source_Contribution:
    Sound speed profiles were collected to correct refraction artifacts in the multibeam bathymetric data that can occur due to changes in the speed of sound throughout the water column.
  2. How were the data generated, processed, and modified?
    Date: 29-Aug-2019 (process 1 of 4)
    Sound velocity profiles were collected approximately every 1-4 hours using an AML MVP30. A computer controlled smart winch and deployment system allowed the free fall MVP profiler to be deployed while the vessel was underway at a user specified time interval. Data from the sound velocity profiler were written to a Kongsberg SIS format ASCII file (.asvp). The MVP was set to only collect data on the down-cast. Beginning on Friday August 2 at 1655 UTC, the MVP30 was replaced by an AML Minos X SVTP hand-deployed sound velocity profiler. The Minos X was deployed every 1-3 hours to collect sound velocity, pressure, and temperature profiles in the water column though the remainder of the survey. AML SeaCast software (v. 4.4) was used to read the profile data from the Minos X, export all raw cast data to an AML SeaCast (.csv) formatted file, then edit the sound velocity profile to preserve only the downcast portion of the deployment and export it to a Kongsberg SIS ASCII (.asvp) formatted file. Person who carried out this activity:
    Charles R Worley
    U.S. Geological Survey
    Physical Scientist
    384 Woods Hole Rd.
    Woods Hole, MA

    (508) 548-8700 x2250 (voice)
    (508) 457-2310 (FAX)
    cworley@usgs.gov
    Date: 24-Jan-2020 (process 2 of 4)
    A Python script (plotMVPsql_2019_002_py3.py run from the shell script do_MVPplots) was used to read the ASVP data, filter outlier data, and reformat all of the parsed ASVP data into a final sound velocity file in CARIS SVP format that is ready for import into CARIS HIPS. The contact person for this and all subsequent processing steps below is Seth Ackerman. Person who carried out this activity:
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov
    Date: 05-May-2021 (process 3 of 4)
    After additional editing of the sound velocity data in CARIS HIPS (version 11.3), the final profiles were exported to two separate CARIS HIPS (.svp) files (one each for legs 1 and 2 of the survey). These corrected CARIS SVP files were then split into individual files for each sound velocity cast using the terminal 'csplit' command. >> csplit -f Leg1_ -n3 -k Leg1_SVP_Master.svp '/^Section/' '{300}' >> csplit -f Leg2_ -n3 -k Leg2_SVP_Master.svp '/^Section/' '{300}' Then the Python script MVP_plot_intoSQL_5May2021.py was used to create a plot for each sound velocity cast as a PNG image graph with speed of sound (meter/second) versus depth (meters). Position, Date, Time, and Profile ID were pulled from the SVP header line and written into the image for reference. The image files are named based on the date and time each sound velocity cast was collected. The same script parses the position, Julian Day, time, and Profile ID and entered it into a geospatial SQLite (version 3.36) database using the pyspatialite interface. The geographic positions were used to create point geometries for the station locations, and additional fields indicating survey ID, vessel ID, and device ID were added within the Python script. The individual .svp files (created by the csplit commands above) were then renamed to match the file names of the PNG files (based on the day and time of collection) using the following script: >> for f in Leg*.svp; do x=`awk 'NR==1{print "cast_"substr($2,1,4)substr($2,6,3)"_"substr($3,1,2)substr($3,4,2)substr($3,7,2)".svp"}' $f`; echo mv -v $f $x | sh; done And finally the CARIS SVP header was restored using the following command line scripts: >> for f in *.svp; do x=`echo "$f" ; cat $f`; echo "$x" > $f; done >> for f in *.svp; do x=`echo "[SVP_VERSION_2]" ; cat $f`; echo "$x" > $f; done
    Date: 19-Nov-2021 (process 4 of 4)
    The sound velocity cast locations were exported from the SQLite database as Geographic Coordinate System (GCS, latitude and longitude) WGS 84 point features in ESRI Shapefile format using Spatialite-tools (version 5.0.1) using the spatialite_tool command in Terminal: >> spatialite_tool -e -shp 2019-002-FA_MVPSVP_data -d ./2019-002-FA-SQLdb_NEWSVP.sqlite -t MVPNav_pt -g geom_MVPnav -c CP1252 -s 4326 --type POINT
  3. What similar or related data should the user be aware of?
    Fofonoff, N., and Millard, R., 1983, Algorithms for Computation of Fundamental Properties of Seawater: UNESCO Tech. Pap. Mar. Sci. 44.

    Online Links:

    Pendleton, E.A., Baldwin, W.E., Barnhardt., W.A., Ackerman, S.D., Foster, D.S., Andrews, B.D., and Schwab, W.C., 2013, Shallow Geology, Sea-floor Texture, and Physiographic Zones of the Inner Continental Shelf from Nahant to Northern Cape Cod Bay, Massachusetts: Open-File Report 2012-1157, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Andrews, B.D., Ackerman, S.D., Baldwin, W.E., and Barnhardt, W.A., 2010, Geophysical and Sampling Data from the Inner Continental Shelf: Northern Cape Cod Bay, Massachusetts: Open-File Report 2010-1006, U.S. Geological Survey, Coastal and Marine Geology Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    Ackerman, Seth D., Foster, David S., Danforth, William W., and Huntley, Emily C., 2019, High-resolution geophysical and sampling data collected off Town Neck Beach in Sandwich, Massachusetts, 2016: data release DOI:10.5066/P9HZHXXV, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman S.D., Foster D.S., Danforth W.W., and Huntley, E.C., 2019, High-resolution geophysical and sampling data collected off Town Neck Beach in Sandwich, Massachusetts, 2016: U.S. Geological Survey data release, https://doi.org/10.5066/P9HZHXXV.

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?
    Navigation data were acquired using the WGS 84 coordinate system with an Applanix POS MV Wavemaster (model 220, V5), which blends Global Navigation Satellite Systems (GNSS) with acceleration data from a Motion Reference Unit (MRU) and GPS azimuthal heading. The POS MV was configured with two AeroAntenna Technologies GPS antennas located at either end of a 2-m baseline, which was oriented fore and aft and mounted atop the MBES pole, approximately midships on the port side of vessel. Positioning data from these GPS receivers were recorded using HYPACK software version 19.0.6.0 during the entire geophysical survey and positions were used for MVP and SVP deployment locations. DGPS positions are horizontally accurate to 0.5 - 2 meters. However, offsets from the location of the MVP30 deployment point and the GPS antenna were not measured, and therefore the horizontal accuracy of the sound velocity profile locations is considered to be within 20 m.
  3. How accurate are the heights or depths?
    MVP30 tow fish depths are calculated by the MVP acquisition software (version 2.391) and the Minos X depths are calculated by the AML SeaCast software (version 4.4); both softwares convert pressure sensor readings to depth using the standard formulas described in Fofonoff, N.P. and Millard, R.C., Jr., 1988, Algorithms for computation of fundamental properties of seawater, UNESCO Technical Papers in Marine Science, No. 44. The depths are estimated to be accurate to within 1 meter.
  4. Where are the gaps in the data? What is missing?
    A total of 439 sound velocity profiles were collected during cruise 2019-002-FA and are included in this dataset. Profiles were renamed as a result of the extra processing done after sound velocity profile edits were done in CARIS HIPS (see process steps). The new file naming convention is based on the day and time the data were collected (see Entity and Attribute Information). Data were collected on the following dates: 20190801-20190829 (Julian day 213-241).
  5. How consistent are the relationships among the observations, including topology?
    Sound velocity profiles were acquired with an AML Oceanographic MVP30 Moving Vessel Profiler (MVP) or an AML Minos X Sound Velocity Profiler (SVP).

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints none
Use_Constraints Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. Please recognize the U.S. Geological Survey as the originator of the dataset.
  1. Who distributes the data set? (Distributor 1 of 1)
    Seth Ackerman
    U.S. Geological Survey
    Geologist
    384 Woods Hole Rd.
    Woods Hole, MA
    USA

    508-548-8700 x2315 (voice)
    508-457-2310 (FAX)
    sackerman@usgs.gov
  2. What's the catalog number I need to order this data set? Sound velocity profile data collected in Cape Cod Bay, Massachusetts during USGS Field Activity 2019-002-FA, using an AML Oceanographic Moving Vessel Profiler and an AML Minos X sound velocity profiler: includes the shapefile 2019-002-FA_MVPSVP_data.shp, 439 PNG images representing all sound speed profiles graphically (2019-002-FA_MVPSVP_Images.zip), 439 .svp ASCII files that represent all sound speed profile data (2019-002-FA_MVPSVP_SVP.zip), a browse graphic (2019-002-FA_MVPSVP_data_browse.jpg) and a Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file (2019-002-FA_MVPSVP_data_meta.xml).
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), and have been processed successfully on a computer system at the 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. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    This zip file contains data available in shapefile, SVP and PNG formats. The user must have software capable of reading shapefile format to use these data. The SVP files can be read with a text editor. PNG files can be viewed with any PNG image viewing software. The zip files must be uncompressed in order to view the images.

Who wrote the metadata?

Dates:
Last modified: 23-Apr-2024
Metadata author:
Seth Ackerman
U.S. Geological Survey
Geologist
384 Woods Hole Rd.
Woods Hole, MA
USA

508-548-8700 x2315 (voice)
508-457-2310 (FAX)
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. (updated on 20240423)
Metadata standard:
Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/DRB_data_release/DRB_P99DR4PN/2019-002-FA_MVPSVP_data_meta.faq.html>
Generated by mp version 2.9.51 on Thu Jun 27 10:43:57 2024