There is need to post-process GNSS observables (raw data) from static rover. But there is no base receiver nearby. So classic differential base-rover
approach doesn't work here. And yet there is great need to get receiver accurate position w/ accuracy down to sub-dm.
Precise Point Positioning (PPP) Post-Processing will help here. Instead of differential base-rover processing, precise Global
satellites orbits and clocks (SP3 format) are used.
PENTAP is Precise Point Positioning post-processing online service.
It allows to compute precise rover positions using SP3 orbits and clocks corrections. No base station is needed. Instead of base-rover differential processing,
PENTAP uses precise SP3 orbits and clocks corrections automatically downloaded from one of public processing centers.
Drawback of using global corrections (instead of local differential like RTK) is increased time to get sub-dm positions accuracy (called as convergence time).
While RTK may be FIXED w/ few centimeters accuracy even instantly, PPP technology (w/o local ionospheric corrections)
may require up to 30 minutes to get sub-decimeter accuracy.
Converge time strongly depends on antenna quality and environment.
Even more, during convergence process it is recommended the rover be static (no move).
Despite other PPP services, PENTAP allows to process both static and kinematic rover files.
Example of PENTAP
Precise Point Positioning (PPP) post-processing is presented. PENTAP downloads precise orbits and clocks (SP3) automatically and process
rover observables in PPP mode. No base station is needed.
Convergence process takes about 20-30 minutes (depends on antenna quality and environment). After that positions accuracy reaches sub-dm level.
Despite other PPP online services, PENTAP allows to process both static and kinematic rover files.