HI Robert. Thank you for you feedback.
CORS status are disabled. Yes I set up the CORS are used as constrains during baselines processing.
Before, 1 years ago my TBC version 5.70 could process baselines constraints accepting Rapid Orbita parameters without any problem. But now only accepting Final Orbita parameters for CORS.
After a week all final orbita parameters would be available, then I can use them. But nearest days I need approximate coordinates using Rapid Orbita Parameters.
------------------------------
[Munkhzul] [Bandikhuu]
[ASME-MON LLC]
[Mongolia]
[+976-99134735]
------------------------------
Original Message:
Sent: 01-29-2026 10:41
From: Robert Hoy
Subject: Network adjustment
Since your CORS are essentially known control points, I always disable baselines between them and use them as constraints
------------------------------
Robert Hoy
Original Message:
Sent: 01-29-2026 00:29
From: Munkhzul Bandikhuu
Subject: Network adjustment
Hello all.
I use TBC 5.70.
In the network adjustment, during baseline processing, CORS-CORS vector are failed, but CORS-Rover vectors fixed, when I use IGS rapid SP3 and ERP.
There are 4 CORS's 14 days data on 9-22th January 2026. But rovers' data are only 2-6 hours.
But when I use 9-10th January IGS final SP3 and ERP, then CORS-CORS vectors are fixed.
Has there any solution using IGS rapid SP3 and ERP files, and CORS-CORS would be fixed?
------------------------------
[Munkhzul] [Bandikhuu]
[ASME-MON LLC]
[Mongolia]
[+976-99134735]
------------------------------