LP360 checks a base station RINEX observation header when you add the file. If information needs correction or review, the RINEX Validation dialog explains the issues before the file is accepted for processing.
This dialog is used by base-file ingest paths for all GNSS processing engine workflows. Files that pass validation are accepted silently. Passing this header check does not guarantee observation quality or compatibility with every engine version.
Review one file or a batch
When you add multiple base files together, files needing review appear in one table. Each issue row includes a Filename; hover over it to see the full source path, including when two files have the same name.
A one-file review automatically selects that file. In a multi-file review, select rows before using an action. Select any issue row to target its entire file, including all its edits and warnings. Use Ctrl/Shift to select rows from multiple files, or use Select all and Clear selection.
Use suggestions, Apply fixes, Accept warnings, Reload / Recheck, View in Default Text Editor and Exclude selected affect only selected files. Selecting several issue rows for one file does not apply an action more than once. Unselected files remain pending, and their typed corrections are retained.
Accepted or excluded files leave the table. Files with unresolved issues stay for further review. The dialog closes when all review files are resolved. Finish review asks before skipping all pending files; files already accepted are still added. Files that passed validation silently are also retained.
Understand the results
| Result | Meaning | What to do |
|---|---|---|
| Error | A blocking header issue remains. | Correct the information and recheck, or cancel and replace the file. Errors cannot be accepted as warnings. |
| Warning | Information needs your review but does not block acceptance after acknowledgment. | Correct it if possible, or explicitly choose Accept warnings if appropriate for your data. |
| Replace file | The issue cannot be edited using the dialog's entry cells. | Select a row for that file and choose Exclude selected, then add a supported original manufacturer file or re-exported RINEX. Advanced users may review a working header in a text editor when the header boundary is readable. |
Correct information in the dialog
- Find the affected row under Information. Read its Current value and Problem / How to fix (read here) columns. This guidance is in the table, not a separate document.
- Locate Corrected value (click to edit), marked with LP360's pencil icon. Click the yellow cell and type the verified value. A blank yellow cell is an entry box and accepts typing.
- If a dropdown is available, choose the exact matching entry or enter a verified value manually. You do not need to count spaces or pad values; LP360 formats supported fields automatically.
- Select a row for each file you want to apply, then click Apply fixes to validate those files' edited headers. If errors remain, those files stay in the dialog with updated issues.
- If only warnings remain, review them and choose Accept warnings to continue, or correct the information and recheck.
Apply fixes accepts each selected file when validation finds no remaining issues. Reload / Recheck checks selected files and refreshes the table without accepting them. After the table refreshes, multi-file reviews require you to select rows again for the next action.
Accept warnings is disabled if any selected file has blocking errors. After entering corrections, click Apply fixes or Reload / Recheck to refresh validation, then select the remaining warning files. Typing into a cell does not automatically revalidate it.
When no suggestion is available
No automatic suggestion means LP360 cannot safely determine the missing or correct information. It does not mean the yellow entry cell is disabled. Use receiver records, antenna labels, field logs or survey records; do not guess.
Use suggestions is enabled only when safe station-ID suggestions are available. It fills the entry cells but does not accept the file or validate the changes. Review the proposed ID and click Apply fixes or Reload / Recheck.
The antenna dropdown lists exact model/radome designations from the installed calibration catalog, not probable matches. Confirm your equipment before selecting an entry. If the catalog is unavailable, type the verified designation manually.
Where to find corrected values
| Information | Use this source |
|---|---|
| Station ID | An optional base label from your records. A missing or blank ID is accepted; do not invent one. If a supplied ID is flagged, use uppercase A-Z and digits 0-9, or clear the label if it is unknown. Check that a suggested ID still identifies the intended station. |
| Receiver model, serial number and firmware | The receiver status page or field records. |
| Antenna model / radome and serial number | The antenna label and setup records. Choose an exact catalog entry where available. |
| Earth-centered X, Y and Z | Verified Earth-centered Earth-fixed (ECEF) coordinates in meters from a survey report. Do not enter latitude/longitude or map eastings/northings. |
| Antenna height, east offset and north offset | Measured setup offsets in meters. Do not substitute a slant height without the manufacturer's conversion to the required antenna reference point. |
| Export program, operator and date | The original export records or manufacturer software. |
| Observer and agency | The field log. If unavailable, review and explicitly accept the warning. |
For numeric entry cells, use a decimal point without unit suffixes or thousands separators.
Advanced option: View in Default Text Editor
Most users should use the dialog's entry cells. Manual RINEX editing requires knowledge of header labels, field widths and the observation format.
- Select the file or files to edit and click View in Default Text Editor. LP360 opens a separate working header named
<original-filename>.header.txtfor each selected file using the Windows default application for.txtfiles. Each working copy is in its own review folder. Hover over that file's Edit in text editor cell to see the working copy's full path and distinguish identical names. If no editor opens, configure that Windows file association and try again. - This file is a header-only working copy. It is not your original observation file and contains no observation body. Existing dialog edits are included when the working copy is first created.
- Edit the header records carefully. Keep the
END OF HEADERrecord and do not add observation data or other content after it. Do not invent equipment, coordinates, heights, observation definitions or times. - Save the working copy in the editor, retaining plain-text RINEX formatting, then return to LP360 and click Reload / Recheck. The table refreshes with the saved header's validation results.
- Resolve any remaining errors, save again and recheck. Use Apply fixes to accept a clean header, or Accept warnings when only reviewed warnings remain.
While text-editor mode is active for a file, its grid editing and suggestions are disabled to avoid conflicting changes. Other files can still be edited in the grid. Reopening the editor uses that file's same working copy. Select its row again before rechecking or accepting saved changes.
Apply fixes and Accept warnings also reload and check the saved working header before acceptance. LP360 cannot see unsaved changes in the editor. Save before returning to LP360; close the working copy when finished.
If LP360 cannot safely identify the original header boundary, text-editor access is disabled. Use Exclude selected, then replace or re-export the file instead.
Replace or re-export a damaged file
If you cannot verify the missing information or safely repair a header, select a row for that file and click Exclude selected. It is not accepted; other pending files remain available for review. Use Finish review to skip all remaining pending files after confirmation.
Prefer the original supported manufacturer base file directly, such as Trimble T02, when supported by your selected workflow. Do not convert a supported native file to RINEX unnecessarily.
If your original format is not supported by that workflow, use the manufacturer's software to export a new RINEX observation file with the required metadata, supported version and observation coverage. Add the new file to LP360. Do not change timestamps or invent observation definitions simply to pass validation.
What happens to the original file?
Corrections made through this workflow do not overwrite your original file. LP360 stages an accepted processing copy and uses its corrected header for downstream processing. The observation body is copied from the original without reformatting. Review decisions and header corrections are recorded in the validation audit.
The advanced editor works only on the separate header working copy. Editing that copy does not change the original or the observation body. Changes made after acceptance are not automatically applied to an already accepted processing copy.
Further troubleshooting
For observation coverage, gaps, base setup and broader file-quality checks, see Troubleshooting: Base Station Observation Files.
If a file still cannot be accepted, record the field names and messages, LP360 version and selected processing workflow. Retain the original file and relevant setup records and contact LP360 Support. Provide observation or diagnostic files only through the approved support channel.
Comments
0 comments
Please sign in to leave a comment.