Hydrodynamic and Sediment Transport Model Application for OSAT3 Guidance: wave direction

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

Frequently anticipated questions:


What does this data set describe?

Title:
Hydrodynamic and Sediment Transport Model Application for OSAT3 Guidance: wave direction
Abstract:
The U.S. Geological Survey has developed a method for estimating the mobility and potential alongshore transport of heavier-than-water sand and oil agglomerates (tarballs or surface residual balls, SRBs). During the Deepwater Horizon spill, some oil that reached the surf zone of the northern Gulf of Mexico mixed with suspended sediment and sank to form sub-tidal mats. If not removed, these mats can break apart to form SRBs and subsequently re-oil the beach. A method was developed for estimating SRB mobilization and alongshore movement. A representative suite of wave conditions was identified from buoy data for April, 2010, until August, 2012, and used to drive a numerical model of the spatially-variant alongshore currents. Potential mobilization of SRBs was estimated by comparing combined wave- and current-induced shear stress from the model to critical stress values for several sized SRBs. Potential alongshore flux of SRBs was also estimated to identify regions more or less likely to have SRBs deposited under each scenario. This methodology was developed to explain SRB movement and redistribution in the alongshore, interpret observed re-oiling events, and thus inform re-oiling mitigation efforts.
Supplemental_Information:
This data layer is a subset of USGS Open-File Report 2012-1234, Hydrodynamic and Sediment Transport Model Application for OSAT3 Guidance. It is part of a set of data layers showing the spatial variability in wave direction for a range of offshore wave condition scenarios. The specific wave conditions and object parameters for this layer are indicated by the file name (of format Hh_Dd_wave_direction), and in the shapefile attributes, and may be found by comparing the scenario name (Hh_Dd) to the look-up table included in the GIS zip file, wave_scenarios.txt. Version 1 of OFR 2012-1234 included model output of wave height (file name covention Hh_Dd_wave_height), but did not include wave direction (such as in this file) or wave period (file name convention Hh_Dd_wave_period). At the request of an OFR user, version 2 of the OFR adds wave direction and wave period model output.
  1. How might this data set be cited?
    Dalyander, P. Soupy, Long, Joseph W., Plant, Nathaniel G., and Thompson, David M., 2012, Hydrodynamic and Sediment Transport Model Application for OSAT3 Guidance: wave direction: U.S. Geological Survey Open-File Report 2012-1234, U.S. Geological Survey, Coastal and Marine Geology Program, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

    This is part of the following larger work.

    Plant, Nathaniel G., Long, Joseph W., Dalyander, P.Soupy, and Thompson, David M., 2012, Hydrodynamic and Sediment Transport Model Application for OSAT3 Guidance: U.S. Geological Survey Open-File Report 2012-1234, U.S. Geological Survey, Coastal and Marine Geology Program, St. Petersburg Coastal and Marine Science Center, St. Petersburg, FL.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -88.720441
    East_Bounding_Coordinate: -85.410772
    North_Bounding_Coordinate: 30.696090
    South_Bounding_Coordinate: 29.395074
  3. What does it look like?
    model_bathymetry.jpg (JPEG)
    Graphic showing the numerical model domain over which analysis is conducted.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Apr-2010
    Ending_Date: 01-Aug-2012
    Currentness_Reference:
    ground condition
  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?
      Indirect_Spatial_Reference: Gulf of Mexico
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • G-polygon (683660)
    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.000001. Longitudes are given to the nearest 0.000001. 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.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: 0.01 m
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    Hh_Dd_wave_direction
    Wave direction for specific wave scenarios (Source: USGS)
    FID
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: ESRI) Coordinates defining the features.
    Scenario_H
    Scenario wave height number (e.g., "h" in Hh_Dd, see wave_scenarios.txt) (Source: USGS)
    Range of values
    Minimum:1
    Maximum:5
    Units:non-dimensional
    Resolution:1
    Scenario_D
    Scenario wave direction number (e.g., "d" in Hh_Dd, see wave_scenarios.txt) (Source: USGS)
    Range of values
    Minimum:1
    Maximum:16
    Units:non-dimensional
    Resolution:1
    PeakWaveDirection
    wave direction (Source: USGS)
    Range of values
    Minimum:0
    Maximum:360
    Units:degrees
    Resolution:0.01

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • P. Soupy Dalyander
    • Joseph W. Long
    • Nathaniel G. Plant
    • David M. Thompson
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    P. Soupy Dalyander
    U.S. Geological Survey
    Oceanographer
    600 4th Street S
    St Petersburg, FL
    USA

    (727) 502-8124 (voice)
    (727) 502-8001 (FAX)
    sdalyander@usgs.gov

Why was the data set created?

This GIS layer contains an estimate of wave direction in the shallow northern Gulf of Mexico (Alabama and portion of the Florida coast) for a single set of wave conditions. This output is based on numerical model output of wave patterns for a given wave height scenario, corresponding to a particular set of offshore wave conditions at NOAA NDBC buoy 42040. The specific wave conditions for a given layer are indicated by the file name (of format Hh_Dd_wave_direction), and in the shapefile attributes, and may be found by comparing the scenario name (Hh_Dd) to the look-up table included in the GIS zip file, wave_scenarios.txt. This data layer is intended to illustrate the spatial variability in wave direction for this particular offshore wave climate scenario.

How was the data set created?

  1. From what previous works were the data drawn?
    NOAA GFS (source 1 of 2)
    NOAA National Centers for Environmental Prediction (NCEP), 20110601, NOAA/NCEP Global Forecast System (GFS) Atmospheric Model: NOAA National Centers for Environmental Prediction, Camp Springs, MD.

    Online Links:

    Type_of_Source_Media: online
    Source_Contribution:
    Wind speed data at 10 m above the sea surface from the NOAA Global Forecast System (GFS) 0.5 degree model is interpolated by NOAA to the 4' Wavewatch3 grid and archived. These archived data are used to drive the numerical wave and circulation model that creates estimates of bottom shear stress.
    NOAA WW3 (source 2 of 2)
    NOAA National Centers for Environmental Prediction (NCEP, 20121001, NOAA/NWS/NCEP 4' Wavewatch III Operational Wave Forecast: NOAA National Centers for Environmental Prediction, Camp Springs, MD.

    Online Links:

    Type_of_Source_Media: online
    Source_Contribution:
    Boundary conditions for the wave model were provided by the 4' NOAA/NWS/NCEP Wavewatch III operational ocean wave forecast.
  2. How were the data generated, processed, and modified?
    Date: 2012 (process 1 of 4)
    The D-Flow and D-Waves components of the Deltares Delft3D numerical model suite (version 4.00.01) were used to estimate east and north components of wind and wave-driven velocity for the offshore wave conditions corresponding scenarios, Hh_Dd, (characteristics of which may be found in the included wave_scenarios.txt file) in each grid cell in the model domain. The wave model D-Waves, based on the Simulating WAves Nearshore (SWAN) model, is a 3rd generation phase-averaged numerical wave model which conserves wave energy subject to generation, dissipation, and transformation processes and resolves spectral energy density over a range of user-specified frequencies and directions. D-Wave was used in stationary mode. D-Flow solves the shallow water Navier Stokes equations and is run in 2-D depth-averaged mode, with linkage to D-Waves allowing the generation of wave-driven currents via wave radiation stress forcing. Default values for model parameters governing horizontal viscosity, bottom roughness, and wind drag were used. Neumann boundary conditions were used along the east, west, and south model boundaries with harmonic forcing set to zero. Model bathymetry was provided by the NOAA National Geophysical Data Center Northern Gulf Coast digital elevation map, referenced to NAVD88.
    Significant wave height, dominant wave period, and wave direction were prescribed as D-Wave TPAR format files every 30 grid cells along the model boundary using results from the NOAA Wavewatch III 4' multi-grid model for a representative moment in time corresponding to the offshore wave conditions of the scenario, the specific time of which may be found in the included wave_scenarios.txt file. A JONSWAP (JOint NOrth Sea WAve Project) spectral shape was assumed at these boundary points. Wind forcing was provided using the archived WavewatchIII 4' winds, extracted from the NOAA GFS wind model, for this time. The D-Wave directional space covers a full circle with a resolution of 5 degrees (72 bins). The frequency range was specified as 0.05-1 Hz with logarithmic spacing. Bottom friction calculations used the JONSWAP formulation with a uniform roughness coefficient of 0.067 m2/s3. 3rd-generation physics are activated, which accounts for wind wave generation, triad wave interactions and whitecapping (via the Komen et al parameterization). Depth-induced wave breaking dissipation is included using the method of Battjes and Janssen with default values for alpha (1) and gamma (0.73). Current model outputs of east and north current velocity component were extracted and interpolated to the wave model grid (staggered points in relation to the current model grid).
    The coupled model system outputs the peak wave direction values included in this layer.
    NDBC observations from station 42012 for the representative scenario time periods were used to validate the wave model results. Person who carried out this activity:
    Joseph W. Long
    U.S. Geological Survey
    Oceanographer
    600 4th Street S
    St. Petersburg, FL
    USA

    (727) 803-8747 x3024 (voice)
    (727) 803-2032 (FAX)
    jwlong@usgs.gov
    Data sources used in this process:
    • NOAA GFS
    • NOAA WW3
    Data sources produced in this process:
    • DELFT3D
    Date: 2014 (process 2 of 4)
    Export the wave direction values for each grid cell from MATLAB format into an ArcGIS polygon shapefile using the Mathworks MATLAB Mapping Toolbox (v2012A). The shapefile is written with the "shapewrite" command. Because MATLAB does not assign a projection, the projection corresponding to the projection associated with the bathymetry used in the numerical models is added in ArcCatalog 9.3. The file was then quality checked in ArcMap to ensure values were properly exported to the shapefile from MATLAB. Person who carried out this activity:
    P. Soupy Dalyander
    U.S. Geological Survey
    Oceanographer
    600 4th Street S
    St. Petersburg, FL
    USA

    (727) 502-8124 (voice)
    (727) 502-8001 (FAX)
    sdalyander@usgs.gov
    Data sources used in this process:
    • DELFT3D
    Date: 13-Mar-2017 (process 3 of 4)
    Keywords section of metadata optimized for discovery in USGS Coastal and Marine Geology Data Catalog. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Alan O. Allwardt
    Contractor -- Information Specialist
    2885 Mission Street
    Santa Cruz, CA

    831-460-7551 (voice)
    831-427-4748 (FAX)
    aallwardt@usgs.gov
    Date: 29-Mar-2018 (process 4 of 4)
    Keywords section of metadata optimized by correcting variations of theme keyword thesauri and updating/adding keywords. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Arnell S. Forde
    Geologist
    600 4th Street South
    St. Petersburg, FL

    727-502-8000 (voice)
    aforde@usgs.gov
  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 attribute in this data layer corresponds to wave direction for Hh_Dd, characteristics of which may be found in the included wave_scenarios.txt file. Values will vary if a different numerical model is used to estimate the waves.
  2. How accurate are the geographic locations?
    Numerical models are used in estimating the wave direction values for this data layer. Because the overall horizontal accuracy of the dataset depends on the accuracy of the model, the underlying bathymetry, forcing values used, and so forth, the spatial accuracy of this data layer cannot be meaningfully quantified.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This statistic was calculated at all locations (wet grid cells) where model output exists. Because of differences between the scenarios, not all grid cells may be included in all scenarios. The statistic was calculated for a particular scenario (Hh_Dd), the characteristics of which may be found in the included wave_scenarios.txt file. The wave direction was generated with Delft3D, and would vary if a different model was used or if different model inputs (such as bathymetry, forcing winds, and boundary conditions) or parameterizations were chosen.
  5. How consistent are the relationships among the observations, including topology?
    No duplicate features are present. All polygons are closed, and all lines intersect where intended. No undershoots or overshoots are present.

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)
    P. Soupy Dalyander
    U.S. Geological Survey
    Oceanographer
    600 4th Street S
    St Petersburg, FL
    USA

    (727) 502-8124 (voice)
    (727) 502-8001 (FAX)
    sdalyander@usgs.gov
  2. What's the catalog number I need to order this data set? Hh_Dd_wave_direction.shp: peak wave direction (in degrees relative to north, direction waves are coming from) for the Hh_Dd scenario. NOTE: Specific layer name indicates the scenario (Hh_Dd), with characteristics given in the included wave_scenarios.txt file.
  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.
    Any use of trade, product, or firm 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?
    • Availability in digital form:
      Data format: WinZip archive file containing the shapefile components. The WinZip file also includes FGDC compliant metadata. in format SHP (version 3.3) ESRI shapefile Size: 35
      Network links: https://pubs.usgs.gov/of/2012/1234/datafiles.html
    • Cost to order the data: None

  5. What hardware or software do I need in order to use the data set?
    These data are available in Environmental Systems Research Institute (ESRI) shapefile format. The user must have ArcGIS or ArcView 3.0 or greater software to read and process the data file. In lieu of ArcView or ArcGIS, the user may utilize another GIS application package capable of importing the data. A free data viewer, ArcExplorer, capable of displaying the data is available from ESRI at www.esri.com.

Who wrote the metadata?

Dates:
Last modified: 29-Mar-2018
Metadata author:
U.S. Geological Survey
Attn: P. Soupy Dalyander
Oceanographer
600 4th Street S
St Petersburg, FL
USA

(727) 502-8124 (voice)
(727) 502-8001 (FAX)
sdalyander@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

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