Campaign processing
How does a station move? Drop daily observation files — or name a station in the IGS/EUREF archives — and each day is solved with precise point positioning, then fitted into a time series with a velocity, seasonal motion, jumps and outliers. Everything runs in your browser.
Drop daily RINEX files — one station or a network
Any number of station-days (RINEX 2/3/4, Hatanaka, gzip). Each is solved with static PPP in your browser; precise orbits are fetched per day. Files are grouped by marker name.
Ocean tide loading: automatic
Near tidal coasts the crust moves by centimetres under the ocean tides. It averages out of a full day, but in sessions of a few hours it biases the height by up to a few centimetres (Brest, 2 h: 48 mm → 16 mm scatter). By default it is applied everywhere from our own global grid: the GOT4.10c ocean tide model (NASA) loaded onto an elastic Earth, typically within a millimetre of Onsala's coefficients.
To use a specific model instead, get your station's coefficients in BLQ format from the free Onsala ocean loading service (model FES2014b, centre-of-mass correction on) and paste them here; the station name must match the file's marker (first 4 characters). A BLQ entry takes precedence over the grid.
Campaign processing FAQ
- What does campaign processing do?
- It turns many days of observations from one station into a coordinate time series: each day is solved with static Precise Point Positioning, then an offset, a velocity, seasonal terms and jumps are fitted and outlier days are left out. The result is how the station moves — its velocity in ITRF2020 and relative to its tectonic plate — and how stable it is.
- How accurate is it?
- Against the official IGS20 velocity of the IGS station Wettzell (WTZR), three and a half years of monthly days gave East 20.23 vs 20.32, North 15.39 vs 15.42 and Up −0.55 vs −0.04 mm/yr, with a day-to-day scatter of about 2 mm horizontally and 5 mm vertically. That suits CORS operators, surveyors and deformation monitoring; official reference-frame solutions (EUREF, IGS) use network software and more modelling.
- How much data do I need?
- Full days (24 h) give the best daily positions. For a velocity, span at least two years — shorter series let seasonal motion leak into the trend. Monthly or weekly days are enough for a velocity; daily data shows short-term motion and events.