Sound velocity profile data from an AML Oceanographic MVP30 collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-FA (PNG images, CSV text, ASVP 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 collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-FA (PNG images, CSV text, ASVP text, and point shapefile, GCS WGS 84)
Abstract:
The natural resiliency of the New Jersey barrier island system, and the efficacy of management efforts to reduce vulnerability, depends on the ability of the system to recover and maintain equilibrium in response to storms and persistent coastal change. This resiliency is largely dependent on the availability of sand in the beach system. In an effort to better understand the system's sand budget and processes in which this system evolves, high-resolution geophysical mapping of the sea floor in Little Egg Inlet and along the southern end of Long Beach Island near Beach Haven, New Jersey was conducted from May 31 to June 10, 2018, followed by a sea floor sampling survey conducted from October 22 to 23, 2018, as part of a collaborative effort between the U.S. Geological Survey and Stockton University. Multibeam echo sounder bathymetry and backscatter data were collected along 741 kilometers of tracklines (approximately 200 square kilometers) of the coastal sea floor to regionally define its depth and morphology, as well as the type and distribution of sea-floor sediments. Six hundred ninety-two kilometers of seismic-reflection profile data were also collected to define the thickness and structure of sediment deposits in the inlet and offshore. These new data will help inform future management decisions that affect the natural and recreational resources of the area around and offshore of Little Egg Inlet. These mapping surveys provide high-quality data needed to build scientific knowledge of the evolution and behavior of the New Jersey barrier island system.
Supplemental_Information:
Additional information on the field activities associated with this project are available at https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-001-FA and https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-049-FA.
  1. How might this data set be cited?
    U.S. Geological Survey, 20210422, Sound velocity profile data from an AML Oceanographic MVP30 collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-FA (PNG images, CSV text, ASVP text, and point shapefile, GCS WGS 84): data release DOI:10.5066/P9C3J33K, 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., Barnhardt, Walter A., Worley, Charles R., Nichols, Alex R., Baldwin, Wayne E., and Evert, Steve, 2021, High-resolution geophysical and geological data collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activities 2018-001-FA and 2018-049-FA: data release DOI:10.5066/P9C3J33K, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: Ackerman, S.D., Barnhardt, W.A., Worley, C.R., Nichols, A.R., Baldwin, W.E., and Evert, S., 2021, High-resolution geophysical and geological data collected in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activities 2018-001-FA and 2018-049-FA: U.S. Geological Survey data release, https://doi.org/10.5066/P9C3J33K.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -74.464691
    East_Bounding_Coordinate: -74.196505
    North_Bounding_Coordinate: 39.55792
    South_Bounding_Coordinate: 39.379681
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5f5f947682ce3550e3bff211/?name=2018-001-FA_MVP_data_browse.jpg (JPEG)
    Thumbnail image of sound speed profile locations offshore of Long Beach Island, NJ.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 31-May-2018
    Ending_Date: 10-Jun-2018
    Currentness_Reference:
    ground condition during field activity 2018-001-FA: 20180531-20180610
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  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 (237)
    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?
    2018-001-FA_MVP_data.shp
    Sound velocity locations collected off southern Long Beach Island, New Jersey during USGS Field Activity 2018-001-FA. (Source: U.S. Geological Survey)
    Lon
    Decimal degree longitude value in GCS WGS 84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:-74.464691
    Maximum:-74.196505
    Units:degrees
    Resolution:.000001
    Lat
    Decimal degree latitude value in GCS WGS 84. (Source: U.S. Geological Survey)
    Range of values
    Minimum:39.379681
    Maximum:39.55792
    Units:degrees
    Resolution:.000001
    MVP
    Name of velocity profile used to distinguish between casts. Profile names are in the format: "MVP30__nnnn", where 'MVP30' refers to the MVP30 moving vessel profiler and 'nnnn' indicates the cast number, 0001 to 0240 for this survey. (Source: U.S. Geological Survey) Character set
    Date
    Month/Day/Year when the MVP cast was collected. (Source: U.S. Geological Survey) Character set
    JD_UTC
    Julian day and UTC time when the MVP 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. "2018-001-FA" where 2018 is the survey year, 001 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
    2018-001-FA_MVP_ASVP
    Sound velocity profile data in Caris SVP ASCII format for survey 2018-001-FA (237 ASVP files) (Source: U.S. Geological Survey)
    2018-001-FA_MVP_Images
    Portable network graphic images of sound velocity profile data for survey 2018-001-FA (237 PNG files) (Source: U.S. Geological Survey)
    Entity_and_Attribute_Overview:
    The PNG images can be hyperlinked to their shapefile location in ArcGIS. The graphs show depth on the y-axis and speed of sound on the x-axis. The format of the ASVP files is as follows: Heading: SoundVelocity (file type), 1.00 (file format version number), cast number in filename (XXX), date/time of file creation ( YYYYMMDDhhmm), latitude (decimal degrees), longitude (decimal degrees), radii around the lat/long position for which the profile is valid (set to 1 meter), date of profile start ( YYYYMMDDhhmm), date of profile stop ( YYYYMMDDhhmm), source instrument of the profile (MVP P where P stands for Probe), number of values in the profile. The header is followed by column data of depth (meters) and speed of sound (meters per second). The CSV file contains the following columns of data: Lon, Lat, MVP, Date, JD_UTC, SurveyID, VehicleID, DeviceID which correspond to the attributes of the same name in the shapefile.
    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)
    • U.S. Geological Survey
  2. Who also contributed to the data set?
  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 (SVP) (also referred to as sound speed profiles) collected during a 2018 USGS cruise in Little Egg Inlet and offshore the southern end of Long Beach Island, NJ, during USGS Field Activity 2018-001-FA. 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: 10-Jun-2018 (process 1 of 3)
    Sound velocity profiles were collected approximately every 30 minutes using an AML Oceanographic Moving Vessel Profiler (MVP). 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. 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 3)
    A Python script (plotMVPsql_2018_001.py) was used to read the ASVP data and plot the sound speed profile as speed of sound (meter/second) versus depth (meters). Position, Date, Time, and Profile ID were pulled from the ASVP header and written into the image (PNG) for reference. Within the same script, the Position, Julian day, Time, and Profile ID were also imported to a geospatial SQLite (version 3.27.1) 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. Lastly, the Python script also reformats the parsed ASVP data into a 'master' sound velocity file 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: 24-Jan-2020 (process 3 of 3)
    The MVP cast locations were exported from the SQLite database as an ESRI Shapefile format in Geographic Coordinate System (GCS, latitude and longitude) WGS 84 using Spatialite-tools (version 4.3.0_3) and the terminal command: 
    > spatialite_tool -e -shp 2018-001-FA_MVP_data -d ./2018-001-FA-SQLdb_NEW.sqlite -t MVPNav_pt -g geom_MVPnav -c CP1252 -s 4326 --type POINT
    The MVP cast locations were exported from the SQLite database as a CSV text file using the GDAL (version 2.4.0) and the terminal command: 
    > ogr2ogr -f "CSV" 2018-001-FA_MVP_data.csv 2018-001-FA-SQLdb_NEW.sqlite -dsco SPATIALITE=yes -sql "SELECT * FROM MVPNav_pt"
  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?
    Navigation data during field activity 2018-001-FA 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 starboard side of vessel. Positioning data from these GPS receivers were recorded using HYPACK software version 17.1.3.0 during the entire geophysical survey and positions were used for MVP sound velocity 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 10 m.
  3. How accurate are the heights or depths?
    MVP30 tow fish depths are calculated by the MVP (version 2.391) acquisition software, which converts 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 thought to be accurate to within 1 meter.
  4. Where are the gaps in the data? What is missing?
    A total of 237 sound velocity profiles were collected during cruise 2018-001-FA are included in this dataset. Profiles MVP30_0052, MVP30_0053 and MVP30_0090 do not exist. Data were collected on the following dates: 20180531-20180610 (Julian day 151-161); no surveying was done on 20180603 (Julian day 154)
  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).

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)
    U.S. Geological Survey - ScienceBase
    U.S. Geological Survey
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO
    United States

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? MVP sound velocity profile data collected off southern Long Beach Island, New Jersey during USGS Field Activity 2018-001-FA, using an AML Oceanographic Moving Vessel Profiler: includes the shapefile 2018-001-FA_MVP_data.shp, a CSV file with the same data as the shapefile (2018-001-FA_MVP_data.csv), 237 PNG images representing all sound speed profiles graphically (2018-001-FA_MVP_Images.zip), 237 .asvp ASCII files that represent all sound speed profile data (2018-001-FA_MVP_ASVP.zip), a browse graphic (2018-001-FA_MVP_data_browse.jpg) and a Federal Geographic Data Committee (FGDC) Content Standards for Digital Geospatial Metadata (CSDGM) metadata file (2018-001-FA_MVP_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, CSV, ASVP and PNG formats. The user must have software capable of reading shapefile format to use these data. The CSV and ASVP 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: 19-Mar-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 20240319)
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P9C3J33K/2018-001-FA_MVP_data_meta.faq.html>
Generated by mp version 2.9.51 on Wed Jun 26 15:25:05 2024