Swath Bathymetry Sounding Data of Seven Rivers in Southwest Florida (2004) in XYZ format

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

Frequently anticipated questions:


What does this data set describe?

Title:
Swath Bathymetry Sounding Data of Seven Rivers in Southwest Florida (2004) in XYZ format
Abstract:
During the past century, river and tidal creeks through the coastal wetlands of the Everglades have filled with sediment and vegetation of surrounding landscapes to the point that many have greatly diminished or disappeared entirely. Restoration plans are under consideration to redirect additional freshwater inflow from the Everglades to open and sustain these waterways to a level that closely resembles historic patterns. In the last 100 years, requirements for water supply and flood protection for urban areas and agriculture in South Florida have resulted in the construction of an extensive canal system to prompt drainage of water into the Atlantic Ocean rather than allowing seasonal seepage through the Everglades and Florida Bay. Water diversions and excessive nutrients and contaminants within the Everglades have decimated bird populations and driven the Florida panther to the brink of extinction. In Florida Bay, declines in sea grasses have resulted in decreasing water clarity, degradation of the food web, and resultant declines in fish populations. The data will be used for hydrodynamic modeling for determining MFL, and for PES scientific studies to improve society's understanding of the environment and assist in the sustainable use, protection, and restoration of the Everglades and other ecosystems within the Southwest region of Florida.
This report serves as an archive of processed swath bathymetry data that were collected in Little Shark, Broad, Harney, Huston, Turner, Chatham, and Lopez. All rivers are located within the boundaries of Everglades National Park in 2004. All rivers are located within the boundaries of Everglades National Park in south Florida. Geographic information system data products include a XYZ data set divided by rivers and USGS quadrangle boundaries. Additional files include formal Federal Geographic Data Committee metadata.
  1. How might this data set be cited?
    Hansen, Mark, 2015, Swath Bathymetry Sounding Data of Seven Rivers in Southwest Florida (2004) in XYZ format: Archive of Bathymetry Data Collected in South Florida from 1995 to 2015 U.S. Geological Survey Data Series-1031, U.S. Geological Survey, St. Petersburg, Florida.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -81.200
    East_Bounding_Coordinate: -80.950
    North_Bounding_Coordinate: 25.500
    South_Bounding_Coordinate: 25.317
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2004
    Currentness_Reference:
    Data assumed to be constant over time but may change due to geologic processes.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: tabular digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Point data set. It contains the following vector data types (SDTS terminology):
      • Point (90796)
    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.0000001. Longitudes are given to the nearest 0.0000001. Latitude and longitude values are specified in decimal degrees. The horizontal datum used is WGS84-G1150.
      The ellipsoid used is WGS84.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257223563.
      Vertical_Coordinate_System_Definition:
      Depth_System_Definition:
      Depth_Datum_Name: NAVD88
      Depth_Resolution: 0.01
      Depth_Distance_Units: meters
      Depth_Encoding_Method: Explicit depth coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    DS1031-SWRivers2004-ChathamR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-HarneyR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-HustonR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-LittleSharkR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-LopezR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-LSharkR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-NHarneyR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-TarponBay_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-TurnerR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-USharkR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-WRivers2004-BroadR_WGS84_NAVD88-G99_SWATH.xyz.txt,DS1031-SWRivers2004-ChathamR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-HarneyR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-HustonR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-LittleSharkR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-LopezR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-LSharkR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-NHarneyR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-TarponBay_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-TurnerR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-USharkR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-WRivers2004-BroadR_WGS84_NAVD88-G99_SWATHxyz.shp
    Post-processed, area-specific X,Y,Z attributed swath bathymetry data. (Source: USGS)
    FID
    Field ID (Source: USGS)
    Range of values
    Minimum:0
    Maximum:90796
    longitude
    WGS84(G1150) x-coordinate (easting) of sample point (Source: NOAA/NGS UTMS)
    Range of values
    Minimum:-81.200
    Maximum:-80.950
    Units:decimal degrees
    Resolution:0.00000001
    latitude
    WGS84(G1150) y-coordinate (northing) of sample point (Source: NOAA/NGS UTMS)
    Range of values
    Minimum:25.317
    Maximum:25.500
    Units:decimal degrees
    Resolution:0.00000001
    z-ellipsoid height
    WGS84(G1150) ellipsoid height of sample point, in meters (Source: SANDS)
    Range of values
    Minimum:-22.00
    Maximum:-29.00
    Units:meters
    Resolution:0.001
    z-NAVD88
    Orthometric height of sample point, in meters. Relative to geoid model Geoid99. (Source: SANDS)
    Range of values
    Minimum:-5.00
    Maximum:-0.040
    Units:meters
    Resolution:0.001

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Mark Hansen
  2. Who also contributed to the data set?
    South Florida Water Management District (SFWMD) provided funding for the study. The project was conducted as a cooperative study by personnel from the USGS in St. Petersburg, FL, USGS in Woods Hole, MA, and the SFWMD, in Fort Myers, FL. Mark Hansen was the USGS principal investigator and data processor. Nancy DeWitt and Chuck Worley collected all bathymetric survey data.
  3. To whom should users address questions about the data?
    Mark Hansen
    U.S. Geological Survey - St. Petersburg Coastal and Marine Science Center
    Oceanographer
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    mhansen@usgs.gov

Why was the data set created?

The primary use of the data collected for this project was for the development of boundary conditions in numerical hydrodynamic modeling for establishing MFL in Southwest Florida. Therefore, the shallow water sonar swath interferometric system was selected to be best suited for fulfilling project requirements.

How was the data set created?

  1. From what previous works were the data drawn?
    USGS Southwest Rivers, Florida bathymetry (source 1 of 1)
    U.S. Geological Survey, Unpublished material, 2004 Southwest Rivers, Florida swath bathymetry.

    Type_of_Source_Media: digital tabular data
    Source_Contribution: Original processed swath bathymetric data
  2. How were the data generated, processed, and modified?
    Date: 2004 (process 1 of 4)
    Swath Bathymetry Acquisition- The interferometric swath bathymetry data were collected aboard the R/V Streeterville using a Systems Engineering and Assessment Ltd (SEA) SWATHplus 468 kHz interferometric sonar system mounted on a pole that was attached to the bow of the boat. Boat motion was recorded at 50-millisecond (ms) intervals using a TSS Dynamic Motion Sensor 05 (TSS DMS-05). GPS and motion data strings from the instruments were streamed in real time and recorded through HYPACK software. Pseudo range GPS data acquired by the Ashetch Z-Surveyor receiver with a Dorne-Margolin choke ring antenna, and motion data were integrated with interferometric soundings in the SWATHplus software package versions 2.2 with positional and calibration offsets pre-defined by a session file(.sxs), allowing for real-time-corrected depths. Prior to deployment, all equipment offsets were surveyed in dry dock with the use of a laser total station. During the survey all swath tracklines were recorded in SEA SWATHplus raw data format (.sxr). An Applied Microsystem SV Smart Sensor, Sound Velocity Sensor (SVS) was attached to the transducer mount and collected continuous speed of sound (SOS) measurements at the depth of the transducers. These values were directly read and incorporated into the SWATHplus acquisition software giving real-time speed of sound at the transducer while underway. Person who carried out this activity:
    Mark Hansen
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Oceanographer
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    mhansen@usgs.gov
    Data sources produced in this process:
    • Raw sensor data and GPS Carrier-phase data in binary format.
    Date: 2004 (process 2 of 4)
    Differentially Corrected Navigation Processing- The coordinate values of the reference GPS base stations obtained from OPUS were provided in the ITRF00 coordinate system. All survey data for the project was referenced to WGS84. Consequently, reference station coordinates were transformed to WGS84 coordinates using the NOAA/NGS software HTDP v1.3. The respective reference (base) station coordinates utilized as reference positions were imported into PNAV v2.0 software by ASHTECH, Inc. Differentially corrected rover trajectories were computed by merging the master and rover the GPS data. During processing, steps were taken to ensure that the trajectories between the base and rover were clean, resulting in fixed positions. By analyzing the graphs, trajectory maps, and processing logs that GrafNav produces for each GPS session, GPS data from satellites flagged by the program as having poor health or satellite time segments that had cycle slips could be excluded, or the satellite elevation mask angle could be adjusted to improve the position solutions. The final differentially corrected precise DGPS positions were computed for each rover GPS session and exported in ASCII text format. Person who carried out this activity:
    Mark Hansen
    U.S. Geological Survey
    Oceanographer
    600 Fourth St. South
    St. Petersburg, FL

    727-502-8000 (voice)
    727-502-8032 (FAX)
    mhansen@usgs.gov
    Data sources produced in this process:
    • Boat trajectory data files in ASCII text format.
    Date: 2004 (process 3 of 4)
    Swath Bathymetry Processing: The corrected trajectory positions, motion data, and sound velocity information were then integrated with the observed bathymetric values to calculate a final ellipsoid height and position representing the elevation of the seafloor with respect to the geodetic reference frame ITRF05 across the swath range. SWATHplus serves as both an acquisition software and initial processing software. Preliminary roll calibration trackline data were collected and processed using SWA SWATHplus and Grid Processor software version 3.7.17. Instrument offset and calibrations values were input into the session file (.sxs) and the raw data files (.sxr) were then processed using the updated system configuration containing roll calibration values, measured equipment offsets, acquisition parameters, navigation and motion from the GPS, motion sensor, and SOS probe at the sonar head. Any calibration offsets or acoustic filtering applied in SWATHplus is also written to the processed data file (.sxp).
    All processed data files were imported into SEA Grid Processor and edited for outliers using the program's depth filters and reference surfaces. Any remaining outliers were then edited out manually. A surface grid was created from the edited soundings dataset. The sample X,Y,Z data were exported as ASCII text at a 1 x 1 m sample resolution. Person who carried out this activity:
    Mark Hansen
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Oceanographer
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    mhansen@usgs.gov
    Data sources produced in this process:
    • Swath processed data in SWATHplus binary format.
    Date: 2015 (process 4 of 4)
    Datum Transformation: The final processed bathymetry files were reformatted for publication. UTM coordinate were converted to latitude/longitude using NOAA/NGS UTMS v2.0 software. Vertical positions were transformed to NAVD88 using National Oceanic and Atmospheric Administration (NOAA), National Geodetic Survey GEOID99 software. Shapefiles were created from X,Y,Z text files using in-house developed software. Person who carried out this activity:
    Mark Hansen
    U.S. Geological Survey St. Petersburg Coastal and Marine Science Center
    Oceanographer
    600 4th Street South
    St. Petersburg, FL
    USA

    (727) 502-8000 (voice)
    mhansen@usgs.gov
    Data sources produced in this process:
    • DS1031-SWRivers2004-ChathamR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-HarneyR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-HustonR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-LittleSharkR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-LopezR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-LSharkR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-NHarneyR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-TarponBay_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-TurnerR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-SWRivers2004-USharkR_WGS84_NAVD88-G99_SWATH.xyz.txt, DS1031-WRivers2004-BroadR_WGS84_NAVD88-G99_SWATH.xyz.txt,DS1031-SWRivers2004-ChathamR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-HarneyR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-HustonR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-LittleSharkR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-LopezR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-LSharkR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-NHarneyR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-TarponBay_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-TurnerR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-SWRivers2004-USharkR_WGS84_NAVD88-G99_SWATH.xyz.shp, DS1031-WRivers2004-BroadR_WGS84_NAVD88-G99_SWATHxyz.shp
  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?
    The accuracy of the data is determined during data collection. This dataset is from one research cruise and is therefore internally consistent. Methods are employed to maintain data collection consistency aboard the platform. During mobilization, each piece of equipment is isolated to obtain internal and external offset measurements with respect to the survey platform. All the critical measurements are recorded manually and digitally entered into their respective programs. For the interferometric swath bathymetry, offsets between the sonar head and the DGPS antennas were measured and entered into the SeaSwath acquisition internal setup program. Precise trajectories were provided by post-processing dual-frequency phase GPS data recorded by the reference station and rover receivers. These bathymetric data have not been independently verified for accuracy.
  2. How accurate are the geographic locations?
    The GPS antenna and receiver acquisition configuration used at the reference station was duplicated on the survey vessel (rover). The base receiver and the rover receiver record their positions concurrently at 1Hz recording intervals throughout the survey. All processed measurements are referenced to the base station coordinates.
    GPS base or differential reference stations were operated within approximately 15 to 20 km of the survey area. Two new temporary ground-control points or benchmarks (surveyed to within 1 cm to 2 cm accuracy) were established throughout the study area for use as reference receiver sites using standard benchmarks procedures. The new benchmarks were surveyed using Ashtech Z-12, 12 channel dual-frequency GPS receivers. Full-phase carrier data were recorded on each occupied benchmark in Ashtech proprietary BIN format with daily occupations ranging from 6 to 12 hours. BIN files were then converted to RINEX-2 format for position processing.
    All static base station GPS sessions were submitted for processing to the online OPUS, GIPSY, and SCOUT system software. The computed base location results were entered into a spreadsheet to compute one final positional coordinate and error analysis for that base location. The final positional coordinate (latitude, longitude, and ellipsoid height) is the weighted average of all GPS sessions. For each GPS session, the weighted average was calculated from the total session time in seconds; therefore, longer GPS occupation times held more value than shorter occupation times. Results were computed relative to ITRF00 coordinate system. The established geodetic reference frame for the project was WGS84. Therefore, final reference coordinates used to process the rover data were transformed from ITRF00 to WGS84 using National Oceanic and Atmospheric Administration/National Geodetic Survey(NOAA/NGS) HTDP software v2.1.
    OPUS, GIPSY, and SCOUT results provide an error measurement for each daily solution. Applying these error measurements, the horizontal accuracy of the base station is estimated to be 0.04 (m) root mean squared (RMS).
    The kinematic (rover) trajectories were processed using PNAV v2.0, by ASHTECH, Inc. A horizontal error measurement, RMS is computed for each epoch. The horizontal trajectory errors for varied between 0 and 0.08(m).
    The combined horizontal error from base station coordinate solutions and rover trajectories range from 0 and 0.22 (m), with the average approximately 0.15 (m).
  3. How accurate are the heights or depths?
    The GPS antenna and receiver acquisition configuration used at the reference station was duplicated on the survey vessel (rover). The base receiver and the rover receiver record their positions concurrently at 1Hz recording intervals throughout the survey. All processed measurements are referenced to the base station coordinates.
    GPS base or differential reference stations were operated within approximately 15 to 20 km of the survey area. Five new temporary ground-control points or benchmarks (surveyed to within 1 cm to 2 cm accuracy) were established throughout the study area for use as reference receiver sites using standard benchmarks procedures. The new benchmarks were surveyed using Ashtech Z-12, 12 channel dual-frequency GPS receivers. Full-phase carrier data were recorded on each occupied benchmark in Ashtech proprietary BIN format with daily occupations ranging from 6 to 12 hours. BIN files were then converted to RINEX-2 format for position processing.
    All static base station GPS sessions were submitted for processing to the online OPUS, GIPSY, and SCOUT system software. The computed base location results were entered into a spreadsheet to compute one final positional coordinate and error analysis for that base location. The final positional coordinate (latitude, longitude, and ellipsoid height) is the weighted average of all GPS sessions. For each GPS session, the weighted average was calculated from the total session time in seconds; therefore, longer GPS occupation times held more value than shorter occupation times. Results were computed relative to ITRF00 coordinate system. The established geodetic reference frame for the project was WGS84. Therefore, final reference coordinates used to process the rover data were transformed from ITRF00 to WGS84 using National Oceanic and Atmospheric Administration/National Geodetic Survey(NOAA/NGS) HTDP software v2.1.
    OPUS, GIPSY, and SCOUT results provide an error measurement for each daily solution. Applying these error measurements, the vertical accuracy of the base station is estimated to be 0.04 (m) root mean squared (RMS).
    The kinematic (rover) trajectories were processed using PNAV v2.0, by ASHTECH, Inc. A vertical error measurement, RMS is computed for each epoch. The vertical trajectory errors for varied between 0 and 0.08(m).
    The combined vertical error from base station coordinate solutions and rover trajectories range from 0 and 0.25 (m), with the average approximately 0.18 (m).
  4. Where are the gaps in the data? What is missing?
    These are complete post-processed xyz bathymetric data points from acoustic swath data collected in 2004 in seven rivers in south-west Florida.
  5. How consistent are the relationships among the observations, including topology?
    This dataset was acquired between May 21 and October 3, 2004 with identical hardware and software systems.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints:
The U.S. Geological Survey requests that it be referenced as the originator of this dataset in any future products or research derived from these data.
Use_Constraints:
The U.S. Geological Survey requests that it be referenced as the originator of this dataset in any future products or research derived from these data. These data should not be used for navigational purposes.
  1. Who distributes the data set? (Distributor 1 of 1)
    Mark E. Hansen
    U.S. Geological Survey
    Oceanographer
    600 Fourth St. South
    St. Petersburg, FL

    (727) 502-8000 (voice)
    (727) 502-8032 (FAX)
    mhansen@usgs.gov
  2. What's the catalog number I need to order this data set? Swath bathymetry, vessel (R/V Streeterville) acquired, bathymetric data
  3. What legal disclaimers am I supposed to read?
    The data have no explicit or implied guarantees. 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 on any other system or for general or scientific purposes, 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?

Who wrote the metadata?

Dates:
Last modified: 01-Feb-2015
Metadata author:
U.S. Geological Survey
Attn: Mark Hansen
Oceanographer
600 4th Street South
St. Petersburg, FL
USA

(727) 502-8000 (voice)
mhansen@usgs.gov
Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/DS1031-SWRivers2004_WGS84_NAVD88-G03_SWATH_metadata.faq.html>
Generated by mp version 2.9.49 on Mon Sep 10 17:44:23 2018