z-logo
open-access-imgOpen Access
Long‐term sediment mobilization at a sandy inner shelf site, LEO‐15
Author(s) -
Styles Richard,
Glenn Scott M.
Publication year - 2005
Publication title -
journal of geophysical research: oceans
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.67
H-Index - 298
eISSN - 2156-2202
pISSN - 0148-0227
DOI - 10.1029/2003jc002175
Subject(s) - sediment transport , submarine pipeline , geology , sediment , bed load , storm , current (fluid) , oceanography , hydrology (agriculture) , continental shelf , environmental science , geomorphology , geotechnical engineering
Nearly 2 years of wave and current observations are used to drive a calibrated bottom boundary layer model to examine sediment transport at the Long‐term Ecosystem Observatory (LEO‐15) located off of the southern coast of New Jersey. The multiyear record is of sufficient resolution to categorize sediment mobilization characteristics such as storm duration, frequency of occurrence, seasonal trends, and modes of transport at this shallow water sandy site. A total of 51 sediment transport events are identified within the 2 year timeframe. Thirty‐two are categorized as winter events, and wintertime sediment transport constitutes 63% of the total for the 2 year period. In nearly all cases, bed load transport dominates the suspended load. The majority of the bed load transport is onshore due to wave asymmetries that lead to higher orbital velocities during the forward half of the wave cycle. For the remainder of events a bimodal wave spectrum is suspected to reverse the orbital velocity skewness leading to offshore transport. Suspended sediment transport is primarily directed alongshore toward the southwest, consistent with current patterns during northeasters. By including bed load transport, the net sediment transport for the 2 year period is directed primarily onshore and slightly alongshore toward the southwest.

The content you want is available to Zendy users.

Already have an account? Click here to sign in.
Having issues? You can contact us here