For the complete documentation index, see llms.txt.Import measurement and ephemeris files into VALAR using the Import dialog. Supported formats include TDM, OEM, and SP3. Route:
/orbits/measurements/data
Import Dialog
On the measurements page, click the Import button in the top-right corner of the toolbar:
1. Configuration
Spacecraft Selection- Select which spacecraft the measurements belong to
- If you had a spacecraft selected on the page, it will be pre-selected
Doppler (range-rate) observables are a supported TDM measurement type. TDM blocks containing
DOPPLER_INSTANTANEOUS rows require configured uncertainty and declared producer correction/convention information, as well as supported bands and integration intervals. See Doppler (Range-Rate) Measurements for requirements and error remedies.2. File Upload
A drag-and-drop zone where you can:- Drag and drop files directly onto the zone
- Click to browse and select files from your file system
- Upload multiple files at once
- All selected files are uploaded in a single batch request
- Files are processed concurrently on the server
- Each file receives individual success/failure status
- No explicit file size limit is enforced by the frontend
3. File Queue
After adding files, they appear in a list showing:- File name
- Status icon (idle, uploading, success, or error)
- Progress bar during upload
- Remove button to remove files before upload
Validation
Frontend Validation
Before upload, the system checks:- File extension: Must match the selected format
- Queue not empty: At least one file must be selected
- Upload state: Cannot upload while another upload is in progress
Backend Validation
When you click Import, files are validated on the server:- Format validation: CCSDS TDM/OEM or IGS SP3 syntax, as applicable
- Data structure validation: Required fields and proper data types
- Timestamp validation: Valid ISO-8601 date formats
- Spacecraft association: Data must be associable with a valid spacecraft
Upload Outcomes
Missing Required Inputs
VALAR preserves valid supplied uncertainty. The baseline compatibility policies are below; workspaces with configurable PVT uncertainty use spacecraft defaults or import overrides for missing OEM/SP3 uncertainty.
Correct the named sensor or source-file input and retry the failed file. A catalog lookup outage requires restoring catalog access, not entering a replacement sigma. Initial TDM inspection checks syntax, identity, and epochs; uncertainty is checked during conversion before persistence, so inspection alone does not certify OD readiness.
Without configurable PVT uncertainty, missing SP3 uncertainty rejects the file. Missing required Doppler uncertainty, invalid dimension-matched TDM sigma values, or invalid supplied OEM covariance rejects that file without persisting its observations. Missing angle/range uncertainty and missing OEM covariance use the compatibility assumptions described above. Other successful files in the batch remain successful. Doppler block-level rejections can instead preserve valid sibling blocks; review the per-file error details. Supplied zeros remain valid where physically meaningful, but a zero sigma is not a usable OD weight. Historical imported values are not automatically reclassified as missing merely because they equal a former default. Successful import with assumed uncertainty does not establish measured accuracy or qualify an OD solution.
Configurable PVT uncertainty
In the selected workspace, open Spacecraft → PVT measurement uncertainty. Use the pencil icon at the top right to edit the shared defaults, then Save or Cancel in the same header. Every spacecraft starts with 100 m position / 0.1 m/s velocity, expressed as positive, finite one-sigma values per source-frame axis. The same settings apply to supported PVT measurement imports, including OEM and SP3. The import dialog offers Use spacecraft defaults or Override for this import when uncertainty is missing. Supplied OEM covariance and individual SP3 component accuracies take precedence; only missing uncertainty uses the chosen values. Invalid supplied uncertainty still rejects the file. Review each file’s values and affected observation counts. If shared defaults change before submission, use Refresh defaults. Import results retain the selected values and their source. Existing measurements and skipped duplicates keep their original uncertainty. Editing shared defaults requires spacecraft-write access; overrides require measurement-upload access. PVT uncertainty is available to authorized Operations users. Outside Operations, OEM retains its 100 m / 0.1 m/s compatibility assumption and SP3 still requires complete supplied component accuracy. The PV importer requires measured position and velocity; this setting does not make position-only SP3 or EP/EV records supported.Reading an import result
Each file has its own result. A completed measurement import is not queued: its stored count is newly inserted measurements from this attempt; duplicates skipped were already present. A file with a warning was still processed. If counts or coverage are unavailable, the dialog says so instead of estimating from the filename. Coverage is based on persisted measurement epochs when available; it may include earlier imports of a file with the same name, and it is not the file’s declared header range. Zero newly stored rows do not establish new coverage. Check the measurements table before retrying an unknown outcome. A missing-uncertainty warning names the affectedsigmas field. For OEM, the
result lists assumed 1σ position and velocity values and affected observations;
for supported configurable PVT imports it also names the spacecraft and whether
spacecraft defaults or import overrides were used. There is no post-import
Verify control. Review the result before using these measurements in OD.
If the source uncertainty should differ, correct the file before importing new
observations. Editing settings or retrying does not change skipped duplicates
or previously stored uncertainty.