What Belongs in a Sensor Station Description?
From the earlier reference collection. Read the current software blog.
A station description should let readers identify the instrument location and understand what, where, and under what conditions it measures.
Give the station a stable identity
Provide a stable station identifier and a human-readable name, and explain how the identifier relates to any provider identifier. Names can be reused or changed; a stable key helps readers connect records across files and updates. If a station moved or its instrument was replaced, describe whether the project treats that as a continuation or a new station. Include an active, inactive, or unknown status when that status is maintained.
Coordinates should include a coordinate reference system and enough precision to locate the station meaningfully. State whether coordinates refer to the sensor, a platform, or a nearby representative point. A coordinate without context can be misleading when a sensor is mounted offshore, inside a building, or on a moving platform. Do not imply survey-level accuracy unless it is known.
Describe the measurement
Name the measured quantity and its units. For a water-temperature station, say whether the value is water temperature, air temperature, or a derived quantity, and provide the unit used in stored data. If a display converts units, identify the stored unit and conversion behavior. Include measurement depth where it matters, with the reference point: “2 m below the surface at the sensor” is more useful than “depth 2.” If depth varies, explain how it is recorded or why it is not fixed.
Give the sampling or reporting interval only when established, and distinguish instrument sampling from data publication. A sensor may sample frequently while the public feed provides aggregated or delayed values. State whether a reported record is instantaneous, averaged over an interval, or otherwise processed. That detail changes how readers compare a point reading with a daily mean or a measurement from another station.
Record operating context and limits
Include notes that affect interpretation: deployment and maintenance periods, known relocations, calibration status if available, and periods when the sensor was offline. Identify the source and date for the station metadata. If a field is unknown, label it unknown rather than leaving readers to interpret a blank as “not applicable.” Avoid burying operational caveats in a general site-wide disclaimer.
A useful station card might identify station W-12, give its coordinates and reference system, specify water temperature in degrees Celsius at a stated depth, and note that measurements are published as hourly averages. Those details let a reader compare like with like. If the station description cannot establish accuracy, representativeness, or current operating state, say which facts remain uncertain. Update the description after a move or instrument change so historical readings are not casually interpreted as though they came from an unchanged setup.