Field noteConnectivity

Observing a mountain valley: a reference design

In a mountain valley, snow, slope and weather change faster than any one observer can follow. This reference design shows how a valley observing site watches them together, works around the terrain, and keeps deciding when its links fail1.

  • 5 min read
  • Figures 5
  • Sources 10
  • Updated

A mountain valley on real terrain, with a network tower and edge module on the floor, a weather station on the lower slope, a radar on a high shoulder and a seismic vault opposite.

Figure 1 The reference site: tower, edge module, weather station, radar and seismic vault

Key points

  1. Avalanche and slope danger depend on snow, weather and ground together, so a valley site measures all three on one clock.
  2. Terrain decides what each radio and instrument can see, so siting starts from the ground model, not the map.
  3. Every value carries its time, place, instrument and quality, so forecasters and road crews can judge it alone.
  4. The site keeps observing and deciding locally when the valley is cut off.

What a mountain valley needs to see

A valley observing site exists to answer one question for the people below the slopes: is it safe to be here now, and will it stay safe? Avalanche warning services define danger as the potential for avalanches to cause damage to something of value1.

That danger is judged from the stability of the snowpack, how widely weak spots are spread, and how large an avalanche could become1. European warning services publish it on a common scale with five levels, from low to very high1.

Forecasters also name the kind of problem they face. For new snow, the amount of fresh loading on the old snowpack is the crucial factor, and how critical it is depends on air temperature, wind and the old snow surface2. Those are measurements a valley site can make continuously.

Snow is not the whole story. Rockfall, debris flows and creeping slopes share the same valleys and respond to the same rain, melt and freeze. A seismometer on bedrock can register large slides and rockfall as ground motion, which gives the site a sense the weather station cannot provide.

The reference site therefore brings together an automatic weather station, a compact radar, a seismic vault and a private network tower, joined to an edge module on the valley floor. Each answers part of the question; together they give a forecaster, a road crew and a lift operator one shared picture.

Siting around the terrain

Mountains decide what every instrument and radio can see. The international guide to observing practice covers snow measurement, automatic weather stations and weather radar in separate chapters, because each has its own exposure rules3.

A weather station for avalanche work stands where it samples the wind that loads the starting zones, not in the sheltered spot that is easiest to reach. A snow depth sensor needs undisturbed ground, clear of drifts built by buildings, fences or the mast itself.

A side view of a radio link across a valley with the Fresnel ellipse drawn between two masts and the clearance it needs at mid-path.

Figure 2 Fresnel clearance on a valley link, at illustrative starting values

Radio links fail first in the shadow of a ridge. Designers of fixed line-of-sight links use international propagation methods4, and when terrain blocks the path the signal bends around obstacles by diffraction, which has its own prediction methods5.

A clear straight line between two antennas is not enough. The radio wave occupies an ellipse around that line, called the Fresnel zone, and a ridge or a snow cornice that intrudes into it weakens the link even when the far mast is in plain view. The simulator shows how wide that zone becomes at mid-path.

This is why the reference design puts the radar on a high shoulder and the seismic vault on firm rock, then checks every link against a terrain model before anything is built. Where a link cannot clear the ground, a relay on a spur or a different band is chosen at the design stage, not after a winter of dropped readings.

From sensor to decision

Every instrument on the site joins one private mobile network run for the valley's own use. Mobile standards describe such non-public networks, and note that keeping network entities on site lets an outage be handled locally6.

The edge module admits each station, checks what it is, stamps its data against the site clock and keeps a copy. Seismic records travel in an open format that can also carry the recording system's state of health, with a companion description of each station's location and response7.

A systems diagram in four tiers: field instruments at the bottom, the private network above them, the edge module above that, and the warning service and local operators at the top, with links running upward.

Figure 3 From sensor to decision in the valley

Decisions that cannot wait are made on the valley floor. A sudden rise in wind loading or a burst of ground motion near a road can raise a local alert at once, while the same values continue upstream to the warning service for its regional forecast.

When the site does publish an alert, it uses an open, non-proprietary message format for all kinds of warnings, with geographic targeting and support for updates and cancellations8. A road authority, a resort and a public warning channel can then read the same message.

What travels with each value

A wind speed from a ridge is only useful if the reader knows which ridge, at what height, measured how, and whether the sensor was iced. Each value leaving the site carries its time, place, instrument, method and quality flags through an open interface for sensor observations and their metadata9.

Quality management is part of observing, not an afterthought, and the international guide gives it a volume of its own3. In the valley that means flagging a rimed anemometer or a buried snow sensor at the edge, where the evidence is fresh, rather than discovering it in a forecast office days later.

Weather observations can also flow to national and international services. The global system for sharing meteorological data is moving to open web standards and a subscribe-and-notify model10, so a valley site can contribute without a special link.

A stack of layers that travel with every valley observation: the value, its time, its place on the terrain, the instrument and its state, the method, quality flags and provenance.

Figure 4 What travels with every value from the valley

Questions and answers

Is this a deployment in a specific valley?

No. It is a reference design that shows how the parts fit together. A real site is designed from its own terrain survey and snow climate.

Does the site replace the avalanche forecaster?

No. It gives forecasters and local crews better observations sooner. Danger ratings remain the work of the warning service.

Glossary

Fresnel zone
The ellipse-shaped region around the straight line between two antennas that a radio link needs to keep largely clear.
Avalanche problem
A named pattern of snowpack instability, such as new snow or wind slab, that forecasters use alongside the danger level.
Edge
Computing placed at the site, close to the instruments, rather than in a distant data centre.

References

  1. Government or regulator: Avalanche Danger Scale. European Avalanche Warning Services (EAWS). avalanches.org (accessed )
  2. Government or regulator: Avalanche Problems. European Avalanche Warning Services (EAWS). avalanches.org (accessed )
  3. Standard or official statistic: Guide to Instruments and Methods of Observation (WMO-No. 8). World Meteorological Organization. community.wmo.int (accessed )
  4. Standard or official statistic: Recommendation ITU-R P.530: Propagation data and prediction methods required for the design of terrestrial line-of-sight systems. International Telecommunication Union. itu.int (accessed )
  5. Standard or official statistic: Recommendation ITU-R P.526: Propagation by diffraction. International Telecommunication Union. itu.int (accessed )
  6. Standard or official statistic: Non-Public Networks (NPN). 3GPP. 3gpp.org (accessed )
  7. Consortium or technical document: miniSEED 3 specification. International Federation of Digital Seismograph Networks (FDSN). docs.fdsn.org (accessed )
  8. Standard or official statistic: Common Alerting Protocol Version 1.2. OASIS. docs.oasis-open.org (accessed )
  9. Standard or official statistic: OGC SensorThings API. Open Geospatial Consortium. ogc.org (accessed )
  10. Standard or official statistic: WMO Information System (WIS). World Meteorological Organization. community.wmo.int (accessed )

As of