Begin with the claim, not the colours
Before following an arrow across a screen, find out what it represents. A map may show geostrophic surface velocity derived from altimetry, total velocity from a model, a tidal prediction or a long-term mean. These are different products. They can all be useful, but they cannot answer exactly the same question. The title and legend should identify the variable; the documentation should explain how that variable was obtained.
Check units next. Metres per second, centimetres per second and knots are not interchangeable labels. Arrow length may encode speed, while colour may encode the same quantity or something entirely different. Some displays normalise arrow length so that only direction is meaningful. Animated particles are often visual aids rather than individually tracked water parcels. Attractive motion on a screen is not, by itself, a documented transport calculation.
Read the clock and the depth label
A map’s issue time is not necessarily its valid time. A forecast may be published today but describe tomorrow; a delayed analysis may describe an earlier day. A daily mean suppresses some high-frequency variability that an hourly field retains. Monthly and seasonal averages can show persistent patterns while hiding reversals, eddy passages and short wind events. Compare like with like before calling two maps inconsistent.
“Surface” also needs a definition. A satellite retrieval, a model’s uppermost layer and a drogued instrument centred below the surface are not sampling identical water. Vertical shear can make their velocities differ. A surface arrow should never be extended unchanged through the water column unless the evidence justifies it. Subsurface currents may have different directions, speeds and variability.
Separate streamlines from journeys
A streamline is tangent to the velocity field at a given time. A trajectory follows a particle through a field that may change as time passes. They coincide only under appropriate conditions, such as a steady flow. A looping streamline on today’s map does not promise that a floating object will complete that loop tomorrow. A future trajectory requires the evolving velocity field and assumptions about the object’s behaviour.
Real floating material can also respond to wind, waves and buoyancy. Oil, fishing gear and a standard research drifter do not necessarily follow the same route. Stokes drift associated with waves can matter near the surface. A water-velocity product that omits these influences is not automatically a complete object-drift prediction, even when its arrows are accurate for the quantity it represents.
Look for the missing scales
Map pixels often look more precise than the underlying information. Interpolation, smoothing and display resampling can create a continuous field across sparse measurements. A model may publish many grid cells while resolving only larger features reliably. Narrow jets, river plumes and tidal channels can be poorly represented in a basin-scale product. Zooming in enlarges the picture; it does not improve the observing network or model physics.
Compare a broad map of the Labrador Sea with a local assessment of the English Channel. Different tides, coastlines and spatial scales affect what is useful. High-frequency coastal radar can provide valuable surface-current observations in some regions, but range, geometry, interference and quality control limit coverage. No measurement method earns universal trust simply because its output is shown as arrows.
Read uncertainty as part of the result
Uncertainty can arise from sensor noise, sparse sampling, imperfect corrections, model assumptions and timing mismatches. A single error bar may not describe all of those sources. Ensemble spread can indicate sensitivity within a forecasting system, but it is not automatically a complete measure of real-world error. Look for validation against independent observations and for information about where performance changes.
When maps disagree, investigate before choosing a favourite. Match valid time, depth, velocity component and averaging period. Then compare sources, grid scales and included processes. The disagreement may be physically understandable. For education, that comparison is productive evidence. For navigation, rescue or other safety-critical decisions, this website and its diagrams are not operational guidance: use official marine services, authoritative charts and qualified local advice.
| Label | Question to ask |
|---|---|
| Variable | Total, geostrophic, tidal or another velocity? |
| Time | Observed, analysed, forecast or averaged over which interval? |
| Depth | Which instrument level or model layer? |
| Evidence | Where were measurements taken, and how was the rest estimated? |