Assessing the quality of a kinematic GNSS trajectory
A kinematic trajectory needs a quality history through time, including interruptions, reference information and the relationship to other sensors.
Review a time series rather than one coordinate
A kinematic GNSS trajectory describes the receiver antenna position as it moves. It can support mobile mapping, vehicle surveys, drone workflows or other applications in which position changes throughout the observation period. Quality therefore varies along the route. A single average precision value can hide the short interruption or biased segment that matters most to the final product. Review position and quality as functions of time and location.
Begin with the intended use of the trajectory. Determine whether it will locate photographs, georeference another sensor, describe a vehicle path or support a derived engineering product. Each use introduces additional dependencies, including timing, sensor offsets and orientation. A sound antenna trajectory is necessary, but it is not by itself a complete statement about the accuracy of every point measured by an attached camera, scanner or other instrument.
Continue learning RTK will not fix: a practical troubleshooting order
Preserve time and coordinate definitions
Record the time system, timestamp convention and coordinate reference frame for the trajectory and every associated sensor. A time offset can shift mapped features even when the GNSS positions are internally consistent. The effect depends on movement, so a timing mistake may appear small while stationary and become obvious at higher speed or during a turn. Verify timing with the supported system procedure rather than manually adjusting a file until it looks aligned.
Document the antenna reference point and the lever arm to other sensors where relevant. These offsets must use a defined coordinate convention and orientation relationship. A sign error can produce systematic displacement that changes with vehicle heading. Preserve calibration information and the configuration applied during processing. If the platform setup changes, treat the new arrangement as a separate configuration rather than assuming that an old offset remains valid.
Continue learning GNSS integration in mobile mapping: trajectory, timing and checks
Inspect observation continuity along the route
Plot solution state, available observations, correction status and processing quality indicators against time. Identify gaps, restarts, transitions and periods of degraded tracking. Relate them to route conditions such as buildings, trees, bridges or sharp changes in platform motion. An interruption is not automatically unacceptable, but its effect must be understood for the specific processing approach and the downstream product that uses the trajectory.
Keep original timestamps when reviewing gaps. Resampling or interpolating a trajectory can create a visually smooth line without adding independent positioning evidence. Mark interpolated intervals and retain the original data. Where an integrated system bridges GNSS gaps with inertial or other measurements, evaluate the supported uncertainty and quality indicators for those periods. Do not describe the bridged segment as having the same evidence as an uninterrupted GNSS observation simply because both appear in one file.
Continue learning Drone RTK and ground control: complementary evidence for mapping
Check correction and reference information
For real time kinematic trajectories, review correction continuity, source selection and solution transitions. For postprocessed trajectories, verify matching reference observations, time coverage and the processing inputs. Confirm that the reference coordinates and antenna metadata correspond to the period observed. A trajectory can inherit a common shift from an incorrect base coordinate even if its relative shape and short term smoothness look convincing.
When processing software offers forward and backward comparisons, use them according to its documented interpretation. Agreement can provide useful diagnostic evidence, but both directions still use shared observations and models. Preserve the comparison and any flagged intervals rather than reducing it to a single pass label. Investigate changes near data gaps or initialization events, where the model may have less observational support.
Continue learning Designing a geodatabase schema for GNSS point observations
Use independent route checks
Plan check features or control observations that can be compared with the final mapped product. The checks should test the full system where that is the project objective, including timing, offsets and sensor processing. A static antenna check before departure does not independently verify every moving segment. Distribute checks across different route directions and environmental conditions so that heading dependent or localized problems have an opportunity to become visible.
Interpret discrepancies in relation to motion. A nearly constant shift may suggest a reference framework issue. A displacement that follows travel direction can suggest timing or lever arm problems. A problem limited to an obstructed segment may point toward degraded trajectory support. These patterns guide investigation, but confirm the explanation with system records and calibration evidence before applying a correction to an entire route.
Continue learning RTK will not fix: a practical troubleshooting order
Decide how degraded intervals will be handled
Establish acceptance rules for segments rather than only for the complete file. Depending on the task, a degraded interval may require recollection, a different processing strategy, exclusion or a clearly qualified deliverable. Keep segment boundaries and the reason for each decision. If a route is repeated, identify which pass supplies the accepted data and ensure that downstream products do not accidentally retain features from the rejected interval.
Avoid masking problems with excessive smoothing. A smooth trajectory can still be displaced, and legitimate motion can be removed by an inappropriate filter. Document any filtering or interpolation, including its purpose and effect on timing. Preserve the original processed trajectory so a future reviewer can distinguish changes introduced by the positioning solution from changes introduced during presentation or downstream data preparation.
Continue learning GNSS integration in mobile mapping: trajectory, timing and checks
Check timing with an illustrative motion calculation
A simple calculation shows why timing belongs in trajectory review. If a platform moves at ten meters per second, a tenth of a second timing offset corresponds to one meter of travel along a straight path. This is an illustrative relationship between speed and elapsed time, not a specification for any particular system. During turns or changing motion, the resulting displacement can be more complex because orientation and sensor geometry also matter.
Use the example to identify which timestamps refer to measurement, exposure, reception or output, according to the system documentation. Do not correct a real trajectory by applying the illustrative offset without evidence. A valid timing adjustment needs an approved calibration or synchronization method and independent verification. Retain the original and revised series if a correction is made. This keeps a useful physical intuition from turning into an arbitrary office shift and helps reviewers distinguish a positioning problem from a temporal alignment problem in the final mapped features.
Continue learning Drone RTK and ground control: complementary evidence for mapping
Deliver quality information with the trajectory
The handover should include the trajectory, time and reference definitions, processing configuration, relevant calibration information and a segment quality summary. Identify gaps, interpolated periods, limitations and independent checks. Where the final product uses additional sensors, describe the relationship between trajectory quality and product verification. This prevents a user from assuming that a precise looking coordinate at every timestamp implies uniform confidence across the survey.
A useful trajectory review follows the measurement chain through time. It connects satellite observations, corrections, platform configuration and downstream checks to the route actually traveled. The result is a dataset whose strong and weak intervals are visible, allowing later teams to make informed decisions about mapping, analysis and any necessary recollection.
Continue learning Designing a geodatabase schema for GNSS point observations
Practical checklist
- Review a time series rather than one coordinate.
- Check timing with an illustrative motion calculation.
- Deliver quality information with the trajectory.
Plan your GNSS setup
Compare the EQ10 and EQ20 receiver specifications, then discuss the configuration and support your project needs.
Compare GNSS receivers
