The familiar salinity number is a derived quantity
A conductivity–temperature–depth instrument, or CTD, does not extract and weigh the salt in each passing parcel. Its conductivity observation supports a quantity called Practical Salinity, which describes seawater through its electrical behavior. The official TEOS-10 explanation distinguishes that quantity from Absolute Salinity, the salt mass fraction used in seawater thermodynamics. Both are useful, but they are not interchangeable names for one raw observation. Understanding the distinction explains why a data file can contain measured conductivity, calculated salinity and another salinity variable used to calculate density.
Sources: sal-teos
Temperature and pressure complete the conversion
The Gibbs SeaWater conversion takes three inputs: conductivity, in-situ temperature and sea pressure. Its published example makes their importance tangible. Conductivities of 34.5487 and 34.5600 millisiemens per centimeter look almost identical, yet the corresponding Practical Salinities are about 20.01 and 36.40. The example pairs those conductivities with very different temperatures and pressures. Those values are software demonstration inputs, not a measured ocean contrast being reported here. They show why conductivity alone cannot be read as a universal salt-concentration scale.
Sources: sal-conversion
Mismatched sensor responses can create a false spike
Temperature and conductivity need to describe the same water closely enough for their combination to make physical sense. Sea-Bird’s profiling-CTD discussion explains that conductivity responds to temperature too. A temperature feature without the corresponding conductivity response can therefore produce a spike in calculated salinity. In its pumped systems, delayed flushing can worsen this mismatch through sharp gradients such as a thermocline. A narrow salinity spike may consequently arise in the combination of channels even when neither channel looks spectacularly wrong by itself.
Sources: sal-alignment
The calculation carries its own units and range
The documented conversion expects conductivity in millisiemens per centimeter, temperature on ITS-90 and sea pressure in decibars. Sea pressure here means absolute pressure minus the specified atmospheric reference. Its output, Practical Salinity on PSS-78, is unitless. The underlying PSS-78 algorithm is valid between Practical Salinities of 2 and 42; this implementation uses a modified low-salinity expression below 2. These details explain why copying an electrical-conductivity number into an unfamiliar calculator can fail even when the digits and the word salinity look plausible.
Sources: sal-conversion
Salt composition matters when calculating density
Two waters need not have exactly the same mixture of dissolved constituents. TEOS-10 accounts for spatial composition differences when connecting Practical Salinity to Absolute Salinity, expressed in grams per kilogram. Consequently, the relationship is not one universal multiplication that works identically everywhere. Absolute Salinity is the appropriate salinity variable for the framework’s density and other thermodynamic calculations. Practical Salinity remains the recommended archived measurement variable, preserving the conductivity-based observation from which later calculations can be reproduced or revised.
Sources: sal-teos
Position enters the next inference
The official Practical-to-Absolute Salinity function asks for longitude, latitude and sea pressure alongside Practical Salinity. Those extra inputs make the second stage visible: a conductivity-derived quantity is being combined with geographic information to estimate the salinity needed by the thermodynamic description. The function returns grams per kilogram, rather than simply relabeling the original unitless number. A plotted salinity profile is therefore easier to interpret when its variable is named explicitly. The symbol and units reveal which stage of this chain the plotted curve represents.
Sources: sal-absolute