Water sensor data for ponds, tanks and water bodies: temperature, light, turbidity

Water temperature, light at the surface and turbidity from a sensor box on a pond or water body, about every 10 minutes, for aquaculture and water-management accounts.

Questions this data answers

  • Is water temperature drifting out of the range the culture tolerates, and since when?
  • How much light reaches the surface over the day, for timing feeding or harvest?
  • Is turbidity rising, the early sign of a bloom, sediment or a crash?
  • How do 2 ponds or tanks on the same site compare hour by hour?

Fields of the water sensor data

4 declared fields in total. water_temp, in degrees, is the variable an aquatic culture is most sensitive to by far. par is photosynthetically active radiation at the surface, in micromoles per square metre per second, specifically the light a culture or plant can use, which differs from the illuminance a weather station reports. turbidity, in nephelometric units, works as a density proxy for a culture or a suspended-sediment proxy for a water body, while turbidity_v keeps the sensor’s raw voltage so the conversion can be redone after recalibration. Every row is tagged by installation and by box.

How it arrives

The water box skips the field radio network entirely. It publishes straight to the platform’s own message broker over the site’s own connection and lands in its own dedicated dataset. A sensor that isn’t fitted sends null, and the bridge keeps that null rather than writing a 0, so a missing probe never quietly reads as a freezing pond. Conductivity, wherever a probe exists, arrives in microsiemens per centimetre and gets stored in millisiemens.

Reading a day

A culture sitting at 23 to 25 °C under 200 micromoles of light at the daily mean is having a productive day; that same light at 30 °C is stress instead. Conductivity drifts down with dilution and up with evaporation, so a jump of several units usually means a top-up happened. Turbidity climbs as a culture thickens toward harvest and drops again right after it. Daily means show the overall shape; the 10-minute rows reveal the afternoon peak a daily mean would otherwise flatten out.

Alerts and dashboards

Threshold rows for water installations get stored per installation, but this dataset itself sends no alerts; the dashboard for water accounts reads the rows directly instead. Water accounts see the same market data as every other account, and can hold a weather station alongside the box if they choose, in which case the Weather Data group applies separately to that station.

Query patterns

A week: start=-7d. Daily means: every=1d&agg=mean. The raw voltage for recalibration: fields=turbidity,turbidity_v.

Cadence~10 min
Key scopefarm:read
Declared fields4
History2026-08 to today
Coverageyour own water sensors
StatusOwn sensors, own account

Only for the account that owns the hardware. Readings and everything computed from them are served to keys on the owning account and to nobody else. The way to get this dataset is a station on your own field, or your own sensors sent in through Sensor Ingest. A NuaSense station on the field is what produces these rows; the hardware is described at nuasense.com/products.

Fields

FieldUnitNote
water_temp°C
parµmol/m²/sphotosynthetically active radiation
turbidityNTU
turbidity_vVraw sensor voltage

Filters

gateway_idnode_id

The dataset is listed in the platform catalogue under the account's installation and answers the same query grammar as every other dataset: start and end, every with agg, fields, limit, order.