Halocline-Induced Refraction and the Vistula Plume Dynamics
The water column in Gdańsk Port is a chaotic layering of densities. During my last field stint, we recorded salinity swings from nearly 0 PSU at the surface to over 7 PSU at the benthos within a vertical span of just five meters. This extreme stratification isn't just a chemical curiosity; it is an acoustic nightmare. Because the speed of sound fluctuates wildly with these salinity gradients, the acoustic beams from an ADCP don't travel in straight lines. They bend. This refraction leads to significant depth-bin errors, often displacing the perceived velocity measurement by several decimeters. If you ignore the sound velocity profile (SVP), your data is essentially fiction.
The Vistula River dumps a massive freshwater load into the Gulf of Gdańsk, creating a plume that pushes saltier North Sea water deeper into the basin. This creates a highly unstable pycnocline. When strong northerly winds hit the coast, they force a sudden intrusion of dense, saline water into the port. This flips the density gradient almost overnight. I've seen these events trigger massive vertical shear, where surface currents race in one direction while the bottom layer stagnates or reverses. It makes standard current averaging useless.
Most practitioners mistake the minimal tidal range in the Baltic—often under 20cm—for stability. They are wrong. The real driver here is the seiche effect and wind-driven surges. These atmospheric forcings create water level oscillations that can mask the actual tidal signal. In a high-traffic environment like Gdańsk, these surges interact with the dredged channels to create localized eddies that can trip up a poorly placed sensor. You aren't measuring tides; you're measuring the wind's grip on the Baltic.
The Deep-Dredged Fairways and the Motława Convergence
The bathymetry of the port is erratic. You have deep, man-made channels designed for Ultra Large Container Vessels (ULCVs) cutting through naturally shallower flats. These channels act as conduits for the denser, saltier water inflows. Around the coordinates 54.35°N, 18.65°E, the depth contours drop sharply. This creates a 'canyon effect' where currents accelerate through the channels while remaining sluggish in the basins. The convergence of the Motława river flow with the Baltic saltwater creates a turbulent mixing zone that is notoriously difficult to map with a single stationary instrument.
We often see a 'wedge' of salt water creeping along the bottom of these channels. This wedge moves independently of the surface currents. If you place your ADCP on a shallower ledge, you miss the primary salt-water transport entirely. Conversely, placing it in the deepest part of the fairway exposes the transducer to the worst of the turbidity. It is a constant trade-off between getting a representative sample of the water column and avoiding the 'muddy' signal of the benthos.
Acoustic Propagation Challenges in This Environment
Turbidity is the primary enemy in Gdańsk. The Vistula brings in a heavy load of organic suspended solids and fine silts. These particles scatter the acoustic signal. During spring freshets, the turbidity spikes so aggressively that you get severe bin contamination. The ADCP starts reflecting off the suspended sediment rather than the water column's natural backscatter. I've seen datasets where the 'current' looked like a vertical wall of noise simply because a plume of silt drifted through the beam. It's frustrating. You spend more time cleaning the data than actually analyzing it.
Then there is the noise. Gdańsk is one of the busiest ports in the Baltic. The acoustic signature of a 20,000 TEU container ship is deafening. When a hull passes directly over a transducer, the signal-to-noise ratio plummets. I've encountered deployments where the data was spiked every time a bulk carrier passed overhead, creating artificial velocity peaks that looked like storm surges but were actually just propeller wash and hull noise. To get a clean signal, you have to position the unit away from the quay walls to avoid acoustic reflections, but not so far that you're in the direct path of every ship's wake.
Frequency Selection and Deployment Strategy
For this specific environment, I always push for 600kHz or 1200kHz units. A 300kHz unit is overkill for the depths in Gdańsk and lacks the spatial resolution needed to resolve the halocline. You need high-resolution bins to see where the velocity shear actually happens. Honestly, the 1200kHz unit is the winner here. It allows you to slice the water column into thinner layers, which is the only way to ground-truth the interaction between the freshwater plume and the saline bottom layer.
Bottom-mounting is the only viable option. Moored ADCPs drift too much in these wind-driven surges, and the resulting tilt correction often introduces more error than it solves. I prefer a heavy tripod mount with a dedicated sound velocity sensor (SVS) running in real-time. Using a monthly or weekly SVP is a recipe for disaster in a mixing zone. You need second-by-second sound speed updates to correct for the salinity swings. Without that, your depth bins are essentially guesses.
Data Interpretation and Field Findings
When looking at the raw data from the Gdańsk fairways, the first thing I do is a sanity check against the local tide gauges. If the ADCP shows a surge that the gauge doesn't, you're likely looking at vessel-induced turbulence. We've observed that the current profiles in the port often show a 'double peak'—one driven by the wind at the surface and another, smaller, opposing current at the bottom. This is the classic signature of the Baltic's stratification. The surface water is pushed out by the wind, while the denser salt water creeps in to replace it.
We found that the most significant velocity shears occur in the top 3 meters of the water column. This is where the Vistula's freshwater meets the Baltic. The turbulence here is intense. Most 'off-the-shelf' processing software struggles with this because it tries to smooth the data. I prefer raw bin analysis. If you smooth the data, you erase the very turbulence that drives sediment transport and dredging requirements in the port. You have to embrace the noise to find the signal.
Operational Implications
Understanding these currents is critical for port operations. The high turbidity and sharp velocity shears mean that sediment doesn't just settle; it migrates in unpredictable pulses. For dredging companies, this means the 'hot spots' for siltation change based on the wind direction and the strength of the Vistula plume. If you only measure the average current, you'll miss the peak transport events that actually fill up the channels.
Furthermore, the acoustic noise from shipping traffic means that any long-term monitoring program must include a strict filtering protocol. You can't just take the mean velocity. You have to identify and excise the 'ship-pass' spikes. I've seen projects fail because the analysts didn't account for the Ro-Ro vessel traffic, leading to an overestimation of the average current speed by as much as 15%. In a professional engineering context, that's an unacceptable margin of error.
About the author: Sarah Jenkins. Sarah is a leading expert in underwater acoustics with twenty years of experience deploying instrumentation in challenging brackish environments. She specializes in the intersection of tidal asymmetry and sediment transport on continental shelves.
Acoustic Signal Attenuation and Refraction in the Vistula-Baltic Mixing Zone of Gdańsk Port