Reading path: Coastal water observation →
Identify the quantity first
A salinity column may contain a practical salinity value, a mass concentration, or a different measure derived from conductivity or other observations. The label alone may not tell the whole story. Read the instrument and dataset documentation to learn what quantity is reported and whether it is a measured value, a calculated value, or a product with specific assumptions.
Practical salinity is conventionally reported as a dimensionless quantity, whereas mass concentration might be given in grams per kilogram or another mass-based unit. Those labels describe different conventions. Do not assume that a value of 35 in one dataset can be treated as exactly 35 grams per kilogram in another. Confirm the definition before any conversion or comparison.
Check units and method notes
Inspect the data dictionary, instrument type, calibration notes, and any stated temperature or pressure treatment. Conductivity-based measurements depend on instrument response and can be processed using particular conventions. A research dataset may also apply corrections or report derived quantities. Two columns both called “salinity” may not be directly interchangeable without the underlying definitions.
Imagine one coastal record lists 32 with no unit and another lists 32 g/kg. The matching numerals do not establish matching quantities. Search for the first record's metadata before plotting both as a continuous comparison. If the definition cannot be established, keep the records separate and clearly label the uncertainty.
Convert only when justified
A conversion is appropriate when the source and target quantities are related by a documented method and the necessary inputs are available. It is not a matter of changing the axis label or adding a decimal. Preserve the source values and add a converted field with the method, assumptions, and input data recorded. If the values are already dimensionless practical salinity, attaching mass units without a justified conversion changes the meaning.
For a field notebook, write the value exactly as supplied, including units or the absence of them, and note the instrument and collection context. If you later compare with another station, make the harmonization step explicit. That protects against false precision and lets a reader revisit the conversion if the method is clarified.
Compare context as well as numbers
Even matching units do not make two records equivalent. Check station location, sensor depth, sampling time, and coverage. Salinity near a river mouth can change over short distances, while a deeper sensor may respond on a different timescale from a surface instrument. Use a shared time zone and compare dates when both series have valid observations.
A strong comparison states the salinity convention, units, method, and site context. If one source's quantity remains uncertain, describe each series on its own terms instead of forcing a numerical match. The result is a more honest account of coastal variation and a clearer path for resolving metadata gaps.
Have a correction or a source to suggest? Send a note →