The Interference of Southwest Swell on Nearshore Vectorial Accuracy
Observations at Claromecó often reveal a deceptive surface velocity. During a typical autumn surge, we might see surface currents peaking at 0.8 m/s, but the net transport is far lower. The problem is the Atlantic swell. The orbital motion of these waves creates a massive oscillation that masks the actual longshore current. If you sample at low frequencies, you're just averaging a sine wave. You get a result close to zero while the water is actually ripping past the sensor at 0.6 m/s. It is a classic case of signal aliasing in a high-energy surf zone. To get a clean signal, we have to separate the residual current from the wave noise. This isn't a simple subtraction. The interaction between the shallow bathymetry of the Buenos Aires province and the incoming swell creates non-linear effects. The water doesn't just move back and forth; it pushes sediment in a specific direction. Most researchers I've reviewed from this region mistake this orbital velocity for net flow. They report current speeds that are physically impossible given the wind stress. I've seen this error repeatedly. It comes down to a failure to account for the wave period in the sampling strategy. In my experience, the only way to solve this is high-frequency sampling. We need to capture the full wave cycle to mathematically strip it away. If you don't, your data is essentially useless for sediment transport modeling. We are talking about a highly volatile environment where the difference between a 'calm' day and a storm surge is the difference between a stable seabed and a complete redistribution of the nearshore sandbars.The Shifting Sandbars of the Claromecó Coastline
The bathymetry here is a nightmare for long-term instrumentation. Around 38°S, the coastline is characterized by a narrow continental shelf and a series of highly mobile sandbars. These bars shift constantly under the influence of the Malvinas Current's distal effects and the immediate pressure of southwest winds. Depth contours are erratic. You might be in 12 meters of water one week and 6 meters the next because a sandbar migrated right over your mooring. This makes the 'bottom-track' function of an ADCP incredibly temperamental. Because the tidal range is micro-tidal (usually under 0.5 meters), the water level is governed by wind-driven surge rather than lunar cycles. This means the vertical pressure gradient changes rapidly during storm events. When the southwest winds kick in, they push a volume of water toward the coast, compressing the water column against the shoreline. This creates an intense longshore current moving northward. It's a high-energy conveyor belt for sediment. I've compared this to the North Sea, but Claromecó is more erratic. The sand moves in pulses, not a steady stream.Acoustic Propagation Challenges in This Environment
Claromecó is often choked with suspended solids during the winter months. These sediments attenuate acoustic signals. When the turbidity spikes, the signal-to-noise ratio drops. You start seeing 'spikes' in your velocity profiles that aren't real water movement; they are just the ADCP struggling to lock onto a backscatter signal through a wall of silt. We found this unreliable in turbid waters unless we tightened the correlation threshold. If you leave the correlation settings too loose, the instrument starts guessing. That's where the 'noisy data' comes from. Then there is the issue of bottom-bounce. In depths of 5 to 10 meters, the acoustic ping hits the seabed and reflects back before the instrument has finished processing the water column. This creates a 'fence' of contamination. In practical terms, the bottom 1.5 meters of your profile becomes a blur of interference. You can't trust the shear layer data in these zones. It's a frustrating limitation. You want to see how the current slows down as it hits the bed, but the physics of acoustic reflection in shallow water prevents a clean reading.600kHz Frequency and Bottom-Mounted Configuration
For this specific site, a 600kHz ADCP is the only logical choice. I've tried 300kHz in similar shallow environments, and the blanking distance is simply too large. With a 300kHz unit, you lose the first 1.5 to 2 meters of the water column. In a 7-meter depth, losing 2 meters is a disaster. The 600kHz unit allows us to get much closer to the seabed. We use a bottom-mounted configuration with a custom-weighted tripod. This isn't optional. If you use a standard mooring, the current will roll the instrument over. Once the transducer head isn't level, your vectorial accuracy is gone. You'll be measuring a diagonal flow as a horizontal one. I've seen deployments fail because the team used a gravity base that was too light for the Atlantic's surge. I prefer setting the bins to 0.25m. Yes, it increases the data load significantly. But if you want to capture the shear layer and detect the exact point where the wave orbital velocity dies out, you need that resolution. We run the sampling rate at 1Hz or higher. Anything slower is just a gamble. If you sample at 0.1Hz, you are effectively blind to the wave period. You'll see a 'zero' velocity when the water is actually ripping past at 0.6 m/s because you caught the peak and the trough in one average. It's a common rookie mistake.Data Interpretation and Field Findings
When we look at the data from a typical southwest wind event, the pattern is striking. The velocity peaks in the upper water column and drops sharply as you move toward the bed. This is the 'wave-induced' component. The residual current—the actual transport of water—is much smaller and constant. By applying a high-pass filter to the 1Hz data, we can strip the wave oscillation. What remains is the true longshore transport. In several runs, we found that the 'apparent' current was 1.2 m/s, but the 'residual' current was only 0.3 m/s. That's a massive difference for anyone trying to calculate sediment budget. We also noticed a strange correlation between the surge height and the signal attenuation. As the water level rises during a storm, the turbidity increases, and the ADCP's 'ping' strength weakens. We had to perform a sanity check against a handheld current meter during a low-energy window to ensure the ADCP wasn't drifting. The ground-truthing confirmed that the 600kHz unit was accurate, provided the bin size was tight and the correlation threshold was set to 70%. Anything lower and the sediment noise takes over.Operational Implications
These findings change how we approach coastal engineering at Claromecó. If you build a breakwater based on 'apparent' currents, you are over-engineering for the wrong force. The real driver of morphology here is the episodic, wind-driven surge, not a constant current. Understanding the residual flow allows for better prediction of where the sandbars will migrate. It also helps in timing the dredging of navigation channels. If you know the residual transport rate, you can predict when the channel will silt up after a storm. For future deployments, I recommend a dual-instrument approach. Pair the ADCP with a pressure sensor on the surface. This allows us to correlate the exact moment of surge arrival with the change in current vectors. It removes the guesswork. Honestly, the 600kHz unit outperformed every other option we tested, but only if the mooring is heavy enough to survive the winter. If the instrument tilts even five degrees, your data is skewed. Precision in deployment is just as important as precision in sampling.About the author: Dr. Kenji Sato. A specialist in underwater acoustics and oceanographic instrumentation with 20 years of experience in river discharge and coastal flow. He has designed acoustic monitoring networks across four continents.
Isolating Wave-Induced Orbital Velocity from Longshore Transport at Claromecó