SpaceProcessing
POSPac PP-RTX: corridor trajectories without local base stations
What base-station-free trajectory processing changes—and what still needs validation.
The corridor logistics problem
Long linear projects can make local GNSS base-station deployment difficult. Stations need suitable sites, access, power, security and an observation plan. A post-processed correction service can change those logistics, but the survey still needs a clear accuracy specification and a defensible reference system.
What PP-RTX provides
Trimble Applanix describes POSPac PP-RTX as a service using precise orbit, clock and atmospheric corrections to process GNSS-inertial trajectories. Its documentation includes crewed airborne applications and workflows that do not require local base stations along a corridor. SpaceChamps offers this processing approach as part of suitable airborne configurations, subject to compatible hardware, software and service licensing.
No local base does not mean no checks
Trajectory correction and independent validation solve different problems. Checkpoints test the resulting mapping and should not simply repeat the observations used to fit it. The project must also define horizontal and vertical reference systems, the applicable geoid or height conversion, units and any transformation to a client grid. Omitting these details can make otherwise good data difficult to combine with engineering drawings.
Build the processing plan into the brief
Ask how raw navigation observations will be retained, how trajectory quality will be assessed and how gaps will be handled. Require a report that distinguishes trajectory performance from final point-cloud and terrain accuracy. Before mobilization, confirm service access and a contingency for any unsuitable data. Manufacturer support for crewed mapping is a technical capability; the aircraft installation and flight operation still require their own applicable approvals.