Polygon shapefile outlining the region where we experienced Inertial Measurement Unit (IMU) problems during the October 2012 survey.

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

Frequently anticipated questions:


What does this data set describe?

Title:
Polygon shapefile outlining the region where we experienced Inertial Measurement Unit (IMU) problems during the October 2012 survey.
Abstract:
A GIS polygon shapefile outlining the region where we experienced IMU problems during the October 2012 survey. During post-processing of the October 2012 survey tie line analyses revealed a depth-bias in lines collected on the western intertidal flats on October 19th. The cause of this bias is uncertain; however it may be the result of an imprecise IMU position calibration on that day. These intertidal flat survey lines collected on October 19th were shoaled by 8 cm to minimize offsets between tie lines. After the shift was applied the mean difference of tie line intersections for this survey was 2 cm (SD = 4). Note that Guadalupe Slough was also surveyed on October 19th, but data within the slough did not appear to show the same offset as soundings within the flats, and as a result, were not adjusted. Although our best effort was made to correct these data, the accuracy of elevations within these polygons is less reliable than for the remainder of these datasets.
Supplemental_Information:
USGS Field Activity S-06-12-SF <http://walrus.wr.usgs.gov/infobank/s/s0612sf/html/s-06-12-sf.meta.html>
  1. How might this data set be cited?
    U.S. Geological Survey (USGS), Pacific Coastal and Marine Science Center (PCMSC), Santa Cruz, CA., 2014, Polygon shapefile outlining the region where we experienced Inertial Measurement Unit (IMU) problems during the October 2012 survey.:.

    This is part of the following larger work.

    U.S. Geological Survey (USGS), Pacific Coastal and Marine Science Center (PCMSC), Santa Cruz, CA., 2014, Bathymetry and Digital Elevation Models of Coyote Creek and Alviso Slough, South San Francisco Bay, California (Version 2, Revised March 2014): U.S. Geological Survey Open-File Report OF2011-1315.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -122.060187436
    East_Bounding_Coordinate: -121.974560855
    North_Bounding_Coordinate: 37.4706742088
    South_Bounding_Coordinate: 37.4231662547
  3. What does it look like?
    <http://walrus.wr.usgs.gov/infobank/s/s0612sf/html/s-06-12-sf.nav.jpg> (JPEG)
    Image showing S-06-12-SF survey tracklines.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 12-Oct-2012
    Ending_Date: 19-Oct-2012
    Currentness_Reference: ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector
  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):
      • G-polygon (2)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 10
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -123
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000
      False_Northing: 0.0
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 1.0
      Ordinates (y-coordinates) are specified to the nearest 1.0
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum of 1983 (NSRS2007).
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.
      The flattening of the ellipsoid used is 1/298.257.
  7. How does the data set describe geographic features?

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    USGS Pacific Coastal and Marine Science Center
    Attn: David P Finlayson
    Operational Geologist
    400 Natural Bridges Drive
    Santa Cruz, CA
    USA

    (831) 460-7557 (voice)
    (831) 427-4748 (FAX)
    dfinlayson@usgs.gov

Why was the data set created?

To delineate regions within the survey with less reliable elevation values.

How was the data set created?

  1. From what previous works were the data drawn?
    S-06-12-SF (source 1 of 1)
    U.S. Geological Survey, Coastal and Marine Geology Program, 2012, USGS CMG Field Activity S-06-12-SF.

    Online Links:

    Type_of_Source_Media: online
    Source_Contribution:
    This 2012 field activity collected bathymetric data in San Francisco Bay.
  2. How were the data generated, processed, and modified?
    Date: 2012 (process 1 of 6)
    Sonar Data Collection
    The bathymetric surveys were conducted using a 234.5 kHz SEA (Systems Engineering & Assessment Ltd) SWATHplus-M phase-differencing sidescan sonar. The sonar was pole-mounted on the 34-foot USGS mapping vessel R/V Parke Snavely, and affixed to a hull brace. Real-time kinematic (RTK) GPS position data were passed through a CodaOctopus F180 intertial measurement unit (IMU) to the sonar hardware and data collection software. Sonar heads, GPS antennae, and the IMU were surveyed in place to a common reference frame with a Geodimeter 640 Total Station. The R/V Snavely was outfitted with three networked workstations and a navigation computer for use by the captain and survey crew for data collection and initial processing.
    Date: 2012 (process 2 of 6)
    Geodetic Control
    Geodetic control for the survey was established using a shore based Global Positioning System (GPS) base station broadcasting Real Time Kinematic (RTK) corrections to the survey vessel via UHF radio link. The base station was located at Moffett Naval Air Station, on a pre-existing benchmark identified as ARC 34. The NGS lists this monument as PID DG6881 (See Appendix A in report for NGS Datasheet).
    GPS base station coordinates: Reference Frame: NAD83 (NSRS2007) Epoch Date: 2007.00 Latitude: N 37 degrees 25' 34.57880" Longitude: W 122 degrees 02' 05.53373" Orthometric Height: 1.280 m (NAVD88 height modernization project elevation)
    Date: 2012 (process 3 of 6)
    Vessel Position and Attitude
    The R/V Snavely was equipped with a CodaOctopus F180 attitude and positioning system for the duration of the survey. The F180 is running F190 firmware, and receives real-time kinematic (RTK) corrections directly. The RTK GPS data (2 cm error ellipse) are combined with the inertial motion measurements directly within the F190 hardware so that high-precision position and attitude corrections are fed in real-time to the sonar acquisition equipment. The NAD83 (NSRS2007) Epoch 20007.00 3-dimensional reference frame was used for all data acquisition.
    Date: 2012 (process 4 of 6)
    Sound Velocity Measurements
    Sound velocity measurements were collected continuously with an Applied Micro Systems Micro SV deployed on the transducer frame for real-time sound velocity adjustments at the transducer-water interface. The Micro SV is accurate to +/- 0.03 m/s. In addition, sound velocity profiles (SVP) were collected with an Applied Micro Systems, SvPlus 3472. This instrument provides time-of-flight sound-velocity measurements by using invar rods with a sound-velocity accuracy of +/- 0.06 m/s, pressure measured by a semiconductor bridge strain gauge to an accuracy of 0.15 percent (Full Scale) and temperature measured by thermistor to an accuracy of 0.05 degrees Celsius (Applied Microsystems Ltd., 2005).
    Date: 2012 (process 5 of 6)
    Sonar Sounding Processing
    GPS data and measurements of vessel motion are combined in the F180 hardware to produce a high-precision vessel attitude packet. This packet is transmitted to the Swath Processor acquisition software in real-time and combined with instantaneous sound velocity measurements at the transducer head before each ping. Up to 20 pings per second are transmitted with each ping consisting of 2048 samples per side (port and starboard). The returned samples are projected to the seafloor using a ray-tracing algorithm working with the previously measured sound velocity profiles in SEA Swath Processor (version 3.05.18.04). A series of statistical filters are applied to the raw samples that isolate the seafloor returns from other uninteresting targets in the water column. Finally, the processed data is stored line-by-line in both raw (.sxr) and processed (.sxp) trackline files. Processed (.sxp) files were further processed with sxpegn (build 151) by Amy Foxgrover (USGS) to remove erroneous data from the files and make valid gain-normalized amplitude data for processing backscatter data.
    Date: 2012 (process 6 of 6)
    Digital Elevation Model Production The raw bathymetry data was filtered in SEA Swath Processor and imported into CARIS HIPS and SIPS for post-processing. Within CARIS a swath angle BASE (Bathymetric with Associated Statistical Error) surface was created at 1 m resolution and the subset editor used to manually eliminate any remaining outliers or artifacts. The average depth within each 1 by 1 m cell was exported as an ASCII text file and imported into Surfer for interpolation using a linear kriging algorithm with a 1-simga nugget of 0.05 m and a 2 by 2 m search radius. The resultant grid was exported to ESRI ArcMap software for display and further analyses. The entire survey was deepened by 6 cm to account for a bias resulting from changes in the boat instrumentation configuration that occured since the initial survey was collected in 2010.
  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?
    This bathymetric data has not been independently verified for accuracy.
  2. How accurate are the geographic locations?
    Uncertainty in the horizontal position of each sounding is a function of the total uncertainty propagated through each of the following component instruments: 1) base station GPS, 2) vessel GPS, 3) intertial motion unit (IMU), 4) water sound velocity model, and 5) beam spreading in the water column. Assuming no systematic errors in the measurement instruments themselves, beam spreading is the dominate source of positional uncertainty. The 1-degree sonar beam of the SWATHplus-M results in horizontal uncertainty ranging from 0.10 m at 10 m slant range, to about 0.45 m at 50 m slant range.
  3. How accurate are the heights or depths?
    After filtering the data to remove obvious outliers, the standard deviation of the remaining sounding elevations was calculated for each 1 m by 1 m cell (each containing 19 soundings on average) in CARIS. The mean of the standard deviation for all cells in the survey is 0.05 m and 97% of the cells in the data set have a standard deviation of less than 0.15 m.
  4. Where are the gaps in the data? What is missing?
    The raw bathymetry data was filtered in SEA Swath Processor and imported into CARIS HIPS and SIPS for post-processing. Within CARIS a swath angle BASE (Bathymetric with Associated Statistical Error) surface was created at 1 m resolution and the subset editor used to manually eliminate any remaining outliers or artifacts. The average depth within each 1 by 1 m cell was exported as an ASCII text file and imported into Surfer for interpolation using a linear kriging algorithm with a 1-simga nugget of 0.05 m and a 2 by 2 m search radius. The resultant grid was exported to ESRI ArcMap software for display.
  5. How consistent are the relationships among the observations, including topology?
    All bathymetric values are derived from the same instruments and processing workflow.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints:
If physical samples or materials are available, constraints on their on-site access are described in "WR CMG Sample Distribution Policy" at URL: http://walrus.wr.usgs.gov/infobank/programs/html/main/sample-dist-policy.html
Use_Constraints:
This information is not intended for navigational purposes.
Read and fully comprehend the metadata prior to data use. Uses of these data should not violate the spatial resolution of the data. Where these data are used in combination with other data of different resolution, the resolution of the combined output will be limited by the lowest resolution of all the data.
Acknowledge the U.S. Geological Survey in products derived from these data. Share data products developed using these data with the U.S. Geological Survey.
This database has been approved for release and publication by the Director of the USGS. Although this database has been subjected to rigorous review and is substantially complete, the USGS reserves the right to revise the data pursuant to further analysis and review. Furthermore, it is released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.
Although this Federal Geographic Data Committeecompliant metadata file is intended to document these data in nonproprietary form, as well as in ArcInfo format, this metadata file may include some ArcInfo-specific terminology.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey, Pacific Coastal and Marine Science Center (PCMSC)
    Attn: David P Finlayson
    400 Natural Bridges Drive
    Santa Cruz, CA
    US

    831-460-7557 (voice)
    831-427-4748 (FAX)
    dfinlayson@usgs.gov
  2. What's the catalog number I need to order this data set? Downloadable Data
  3. What legal disclaimers am I supposed to read?
    This information is not intended for navigational purposes.
    This database has been approved for release and publication by the Director of the USGS. Although this database has been subjected to rigorous review and is substantially complete, the USGS reserves the right to revise the data pursuant to further analysis and review. Furthermore, it is released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.
    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.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 2015
Metadata author:
Amy Foxgrover
400 Natural Bridges Drive
Santa Cruz, California
USA

(831) 460-7561 (voice)
afoxgrover@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

Generated by mp version 2.9.32 on Fri Sep 04 20:55:31 2015