Choosing satellite ephemeris information for GNSS processing

Begin with the processing strategy

Ephemeris information describes satellite motion in a form that a positioning processor can use. Broadcast navigation messages and precise orbit products are different sources of that information. Neither should be selected by a simple rule that the most impressive label always produces the best project result. Begin with the positioning method, software support, required timeliness and coordinate framework, then identify the appropriate orbit and clock inputs for that workflow.

Relative GNSS, precise point positioning and other processing approaches use models differently. Some processors obtain supporting information automatically, while others require explicit files. Record what the software actually used. A folder containing a precise orbit file is not evidence that it contributed to the solution. The processing report should link the observations, selected orbit and clock products, antenna models and other relevant settings to the resulting coordinate.

Continue learning Preparing GNSS data for PPK processing

Understand timeliness and product maturity

Orbit and clock products can be released with different latencies and levels of maturity. The International GNSS Service publishes information about its product families and their intended characteristics. Operational availability changes, so consult the current official product documentation when planning a processing schedule. Avoid copying a latency or accuracy figure from an old guide and treating it as a permanent property of every current product.

Decide whether the project needs a rapid preliminary result or can wait for a later reviewed solution. If preliminary coordinates are issued, label them clearly and define how final processing will replace them. A later product may support a more complete workflow, but the coordinate should still undergo independent checks and review. Waiting longer does not correct an antenna height mistake, unstable mark or incompatible reference framework.

Continue learning Pairing RINEX observation and navigation files correctly

Check coverage and supported constellations

Confirm that the selected product covers the observation period and the satellite systems used by the processor. Sessions near day boundaries may require adjacent coverage according to the software's interpolation and modeling rules. Inspect the file content and processing warnings. A nominal daily label does not by itself establish that all required satellites and epochs are available for every observation in a mixed constellation dataset.

Software compatibility also matters. A processor may support one precise product format or naming convention more reliably than another. Use documented import behavior and retain the original downloaded files. If conversion is needed, record the tool and settings. Do not edit satellite positions or timestamps manually to make a file import, because that creates an undocumented model that future reviewers cannot readily reproduce or validate.

Continue learning Recognizing tropospheric error in GNSS survey planning

Keep orbit, clock and model conventions compatible

Precise processing often needs more than an orbit file. Clock information, antenna calibration and other model choices can be part of a consistent set. Follow the processor's official guidance on compatible inputs and conventions. Mixing files from different sources without checking their intended use can undermine the expected benefit of using precise products, even when every individual file is valid and comes from a reputable provider.

Record the product identifiers, source and retrieval date. Where the workflow uses an automatic download, preserve the retrieved inputs or a reproducible manifest when permitted. A later rerun might otherwise select a different product family or updated file. This is particularly important for audit trails and monitoring projects, where an apparent coordinate change must be distinguishable from a change in the processing inputs.

Continue learning Organizing GNSS project folders for reliable processing and handover

Evaluate the effect with controlled comparisons

When comparing broadcast and precise strategies, change one relevant part of the workflow at a time. Keep the observations, antenna metadata, reference definition and acceptance checks consistent. Compare usable data span, warnings, residuals, uncertainty indicators and independent check discrepancies. A small difference between two coordinates does not establish that both methods are accurate; they may share a common setup or reference error.

Document why the comparison was performed. It might test whether a preliminary workflow is adequate, explain an unusual processing result or assess a software configuration. Do not select whichever solution happens to match a desired coordinate most closely without understanding the reason. The accepted method should be supported by the project specification and evidence, rather than by retrospective preference for the most convenient numerical outcome.

Continue learning Preparing GNSS data for PPK processing

Avoid confusing product quality with survey quality

Improved satellite modeling addresses only part of the measurement chain. Multipath, antenna setup, mark stability, data gaps and coordinate transformations can still dominate a project result. A precise orbit product cannot recover observations that were never recorded or identify the wrong physical mark. Keep field controls and independent checks in the workflow even when the office uses sophisticated supporting products.

If a result changes unexpectedly after switching products, investigate compatibility and coverage before concluding that the later coordinate is necessarily better. Review warnings, constellation usage and model settings. Check whether the software changed other defaults at the same time. Preserve both runs so the cause can be traced. A controlled diagnosis is more useful than treating every difference as a direct measure of the earlier solution's error.

Continue learning Pairing RINEX observation and navigation files correctly

Record an automatic download as a selected input

An automatic product download can save time, but it should still leave an identifiable record. Capture the product family, file identifier, coverage and relevant software behavior in the run manifest. If the application retains the files, preserve them according to the project policy. If it provides only a report, keep that report and document the reproducibility limit. The phrase downloaded automatically does not identify what the processor actually used.

This matters when an analyst reruns an old session after a software update. The application might choose a different product or default while appearing to follow the same button sequence. Compare the input manifests before attributing a coordinate change to improved measurement quality or physical movement. A controlled reprocessing study can then distinguish changed satellite information from changed antenna, atmospheric or reference settings. That distinction supports a defensible decision about whether the revised coordinate should supersede the earlier issue and which downstream products need to be reviewed.

Continue learning Recognizing tropospheric error in GNSS survey planning

State the selected inputs in the deliverable

The processing record should name the orbit and clock product families, file identifiers, software version and relevant model choices. Explain whether the result is preliminary or final within the project workflow. Include independent verification and any limitations in coverage or compatibility. This allows another analyst to reproduce the solution and assess whether the same inputs are appropriate for a future reprocessing task.

Before release, confirm that an analyst can locate every named input without repeating an undocumented search or relying on a personal download folder.

Good ephemeris selection is therefore a matter of consistency and purpose. Choose inputs that fit the method, cover the observations and can be documented as a coherent processing set. The final coordinate becomes more credible when the team can explain both the satellite information used and the separate field evidence supporting the measurement itself.

Continue learning Organizing GNSS project folders for reliable processing and handover