AllCases_Sediment_Fluxes: Model Sensitivity to Sediment Parameters and Bed Composition in Delft3D: Model Output

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

Frequently anticipated questions:

What does this data set describe?

Title:
AllCases_Sediment_Fluxes: Model Sensitivity to Sediment Parameters and Bed Composition in Delft3D: Model Output
Abstract:
The sensitivity to sediment parameterization and initial bed configuration on sediment transport processes and morphological evolution are assessed through process-based numerical modeling. Six sensitivity cases using a previously validated model for Dauphin Island, Alabama were modeled using Delft3D (developed by Deltares) to understand impacts on bed level morphology, barrier island evolution, and sediment fluxes. Delft3D model output of suspended and bedload sediment fluxes, and final bed levels data are included in this dataset. Model output from six cases (comprised of three sensitivity configurations and two simulation types (deterministic Delft3D, and probabilistic Delft3D mormerge) as forced by 9 climatological wave forcing conditions are included in this data release. All simulations were initialized using the same initial Digital Elevation Model (DEM) with nearshore and island topopbathy dated 2015 (Passeri and others, 2018). Climatological forcing bins were built from a 1979-2020 reanalysis wave record as applied in Jenkins and others, 2020. For further information regarding model input generation, set up, and analysis, refer to Jenkins and others (2020) and Passeri and others (2018).
  1. How might this data set be cited?
    Jenkins, Robert L. III, Passeri, Davina L., Smith, Christopher G., and Ellis, Alisha M., 20241031, AllCases_Sediment_Fluxes: Model Sensitivity to Sediment Parameters and Bed Composition in Delft3D: Model Output:.

    This is part of the following larger work.

    Jenkins, Robert L. III, Passeri, Davina L., Smith, Christopher G., and Ellis, Alisha M., 20241031, Model Sensitivity to Sediment Parameters and Bed Composition in Delft3D: Model Output: U.S. Geological Survey data release doi:10.5066/P13LISYW, U.S. Geological Survey - 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.4811
    East_Bounding_Coordinate: -87.6599
    North_Bounding_Coordinate: 30.7631
    South_Bounding_Coordinate: 29.9930
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Jan-2020
    Ending_Date: 01-Jan-2021
    Currentness_Reference:
    model simulation
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: raster digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 16
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -87.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 5
      Ordinates (y-coordinates) are specified to the nearest 5
      Planar coordinates are specified in meters
      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.25722210100002.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: 0.01
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    AllScenarios_AllBins_CrossSectionFluxes.zip
    Zipped file containing the NetCDF files (.nc) of the processed resultant time-series of instantaneous sediment flux (meters-cubed per second) and cumulative sediment fluxes (meters-cubed) through a set of observational cross-sections produced by 18 climatological wind and wave forcing bins, three cases: three sensitivity configurations and one model simulation mode (Delft3D). (Source: U.S. Geological Survey)
    Entity_and_Attribute_Overview:
    The Climate and Forecast (CF)-compliant metadata (version CF-1.6) in the header of the NetCDF files provides spatial information for projecting the data into a geographic information system (GIS). It also provides information about the conventions used for attributes in the dataset.
    Entity_and_Attribute_Detail_Citation:
    The entity and attribute information were generated by the individual and/or agency identified as the originator of the dataset. Please review the rest of the metadata record for additional details and information.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Robert L. Jenkins III
    • Davina L. Passeri
    • Christopher G. Smith
    • Alisha M. Ellis
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Robert L Jenkins
    U.S. Geological Survey, SOUTHEAST REGION
    Physical Scientist
    600 4th Street South
    St. Petersburg, FL
    US

    727-502-8138 (voice)
    727-502-8182 (FAX)
    rljenkins@usgs.gov

Why was the data set created?

Data were generated by the Delft3D model as output to assess model sensitivity to bed configuration, and sediment parameterization. Appropriate use of this data includes the assessment of morphological, sediment process, and hydrodynamic differences due to the inclusion of multiple sediment classes, and alternative model initial bed configurations. The AllCases_Sediment_Fluxes.zip is a dataset that consists of Federal Geographic Data Committee (FGDC) metadata record (.txt and .xml) and Network Common Data Form (NetCDF, .nc) files (under six scenarios: three sensitivity configurations and two simulation types (Delft3D, [one-month] and probabilistic, Delft3D mormerge [10-years]), as forced by 9 climatological wave forcing conditions) containing the following variables: coordinates of the cross-section end points (Easting and Northing), cross-section orientation (north-south or east-west) and processed resultant time-series of instantaneous sediment flux (meters-cubed per second) and cumulative sediment fluxes (meters-cubed) through a set of observational cross-sections produced by 9 climatological wind and wave forcing conditions during a one-month Delft3D run.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 22-Feb-2024 (process 1 of 2)
    The Delft3D model simulated process-based deterministic morphological change and sediment fluxes resultant from hydrodynamic action (including waves) and sediment transport. Boundary conditions in the form of a wave and water level boundary forcing are also outlined in Jenkins and others (2020). Output locations of observational cross-sections were placed within the model domain. Over a one-month Delft3D run, sediment fluxes were produced under three cases: three sensitivity configurations and one model simulation mode (Delft3D). Model convention for positive values is in the positive x-direction or y-direction (depending on cross-section orientation). Instantaneous sediment flux (meters-cubed per second) and cumulative sediment flux (meters-cubed) were output at hourly intervals. Person who carried out this activity:
    Robert L Jenkins
    U.S. Geological Survey, SOUTHEAST REGION
    Physical Scientist
    600 4th Street South
    St. Petersburg, FL
    US

    727-502-8138 (voice)
    727-502-8182 (FAX)
    rljenkins@usgs.gov
    Date: 22-Feb-2024 (process 2 of 2)
    Resultant instantaneous sediment flux and cumulative sediment flux were extracted in MathWorks MATLAB (R2015a) with functions included in the OpenEarth toolbox (provided by Deltares; https://publicwiki.deltares.nl/display/OET/Tools). The resulting sediment flux variables from the model grid were then packaged into a NetCDF file (.nc) using the functions available in MATLAB for inclusion in this data release. Upon writing to NetCDF files, dimensional data related to observational cross-sections was also included. Dimensions described in the NetCDF header include: 'n,' the singleton dimension for cross-section end coordinates; 'xy,' number of x-y values used to describe end points; 'i,' the singleton dimension for cross-section end coordinates; 'nn,' the number of cross-section orientation values; 't,' time; and 's,' number of observational cross-sections. This step was completed for three cases: three sensitivity configurations and one model simulation mode (Delft3D) and were packaged into a zipped file. Please see the Resource_Description section for more information. Person who carried out this activity:
    Robert L Jenkins
    U.S. Geological Survey, SOUTHEAST REGION
    Physical Scientist
    600 4th Street South
    St. Petersburg, FL
    US

    727-502-8138 (voice)
    727-502-8182 (FAX)
    rljenkins@usgs.gov
    Data sources produced in this process:
    • AllCases_CrossSectionFluxes.zip
  3. What similar or related data should the user be aware of?
    Roelvink, Dano J.A., 200602, Coastal morphodynamic evolution techniques: Coastal Engineering Volume 53, Issues 2-3.

    Online Links:

    Other_Citation_Details: Pages 277-287
    Jenkins, Robert L., Long, Joseph W., Dalyander, P. Soupy, Thompson, David M., and Mickey, Rangley C., 2020, Development of a process-based littoral sediment transport model for Dauphin Island, Alabama: Open File-Report 2020-1011, U.S. Geological Survey, Reston Virginia.

    Online Links:

    Passeri, Davina L., Long, Joseph W., Jenkins, Robert L., and Thompson, David M., 2018, Effects of proposed navigation channel improvements on sediment transport in Mobile Harbor, Alabama: Open File-Report 2018-1123, U.S. Geological Survey, Reston, Virginia.

    Online Links:

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Deterministic and probabilistic validation simulations were run. Model output was evaluated against observed waves and water levels during that time-period. The model results accurately predicted the observed conditions. More information about model accuracy and validation is outlined in Jenkins and others (2020).
  2. How accurate are the geographic locations?
    Within the Delft3D model, the horizontal coordinates were projected to the North American Datum of 1983 (NAD83) Universal Transverse Mercator (UTM) Zone 16 North (16N) coordinate system with an approximate resolution of 5 m.
  3. How accurate are the heights or depths?
    Within the Delft3D model, the vertical positions were projected to the North American Vertical Datum of 1988 (NAVD88) with an estimated resolution of 0.01 m.
  4. Where are the gaps in the data? What is missing?
    These are the complete resultant sediment fluxes from the Delft3D run simulating the periods 2015/06/19 through 2015/07/19 and 2015/01/01 through 2025/01/01 (Roelvink, 2006). This dataset is considered complete for the information presented, as described in the abstract section. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    The resultant final sediment fluxes are the sediment fluxes output on several cross sections during the one-month Delft3D run simulating the periods 2015/06/19 through 2015/07/19.

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, St. Petersburg Coastal and Marine Science Center as the originator of these data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    USGS SPCMSC Data Management
    U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
    600 4th Street South
    St. Petersburg, FL
    US

    727-502-8000 (voice)
    gs-g-spcmsc_data_inquiries@usgs.gov
  2. What's the catalog number I need to order this data set? FourSedimentClasses_SingleLayer_CrossSectionFluxes.nc, FourSedimentClasses_Underlayers_CrossSectionFluxes.nc, and OneSedimentClass_SingleLayer_CrossSectionFluxes.nc
  3. What legal disclaimers am I supposed to read?
    This digital publication was prepared by an agency of the United States Government. Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made regarding the display or utility of the data on any other system, nor shall the act of distribution imply any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of the data described and (or) contained herein. 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: 31-Oct-2024
Metadata author:
USGS SPCMSC Data Management
U.S. Geological Survey, St. Petersburg Coastal and Marine Science Center
600 4th Street South
St. Petersburg, FL
US

727-502-8000 (voice)
gs-g-spcmsc_data_inquiries@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/AllCases_Sediment_Fluxes_metadata.faq.html>
Generated by mp version 2.9.51 on Mon Nov 4 09:16:24 2024