How GNSS Automated Deformation Monitoring Works

A GNSS automated deformation monitoring system does more than stream precise coordinates. It establishes a stable reference, measures carrier-phase observations at fixed monitoring points, converts baseline changes into local displacement, and decides whether the change is physical or merely measurement noise. This article explains those four steps, then discusses the practical limits that determine whether the system can support reliable alerts on slopes, dams, bridges, and large structures.

1. What Is Actually Measured?

Conventional GNSS positioning estimates a point in an Earth-fixed coordinate frame. Deformation monitoring is interested in the difference between positions at two times. If r(t0) is the initial coordinate and r(t) is the current coordinate, the displacement is:

Δr(t) = r(t) - r(t0)

The result is normally transformed into a local east, north, and up frame. Engineers can then see whether a slope is moving downslope, a bridge tower is shifting laterally, or a dam is settling. Cumulative displacement shows how far the point has moved, while displacement rate reveals whether movement is accelerating. Both are needed for interpretation.

2. Why Carrier Phase Can Detect Small Movements

GNSS deformation monitoring mainly uses carrier-phase observations. Carrier wavelengths are only about 19 to 25 cm for commonly used signals, and receivers can resolve a small fraction of one cycle. This makes carrier phase far more sensitive than code measurements. Expressed in meters, a simplified observation equation is:

L = ρ + c(δt_r - δt_s) + T - I + λN + ε

The geometric range ρ is mixed with receiver and satellite clock errors, atmospheric delays, the integer ambiguity N, and measurement noise. A coordinate change from one receiver therefore cannot be treated as structural movement without further processing.

A typical monitoring network uses a stable reference station outside the expected deformation zone and one or more receivers fixed to the monitored object. Differencing between stations and satellites removes clock errors and reduces spatially correlated atmospheric effects over short baselines. After the ambiguities are fixed correctly, the processor estimates a precise baseline vector and compares it with the initial baseline.

An important distinction remains. A real-time RTK coordinate may still scatter at the centimeter level, especially vertically. Millimeter-level deformation detection comes from stable installations, good satellite visibility, fixed ambiguities, and statistics over many epochs. It does not mean that every individual RTK epoch has millimeter-level absolute accuracy.

3. How the Automated System Operates

A complete installation includes reference and monitoring receivers, antennas, power and communications, a positioning engine, and a monitoring platform. Raw observations or differential data reach the server through wired networks, cellular links, private radio, or satellite communications.

The server first calculates an RTK or precise post-processed solution. It then checks fix status, satellite count, PDOP, residuals, and data completeness. Valid coordinates are transformed into the project frame and compared with the initial value or the previous reporting period. The platform produces displacement and velocity time series while also recording receiver health, supply voltage, communication delay, and data gaps.

Real-time RTK and longer-period processing serve different purposes. Second- or minute-level results are useful when landslide motion or construction disturbance may accelerate quickly. Hourly or daily static solutions average a longer observation span and are better suited to slow settlement and long-term structural stability. Many projects retain both: real-time results provide an early indication, and periodic solutions confirm the trend.