I loaded in 7 consecutive days of some CORS into TBC, expecting it to create seven seperate vectors, each with 24 hours of data. What it actually did was to solve one vector with 7 days of data.
Not really a problem, but not what I was expecting, either.
In LGO, you can select "merge intervals" on import, look for something like that in TBC that will allow the data to remain seperate.
SHG
Interesting. I just tried this with multiple adjacent days of 24 hr Canadian Active Control Point RINEX data.
It does merge the files into a single long occupation vector.
I really don't have a problem with it either one way or the other. I don't see any switch to treat them as multiple occupations.
The processor is extremely fast so I don't see it as an issue.
If one was determined to treat them separately, a reasonably simple solution might be to create a data layer for each day of observations prior to import, set a layer then import the data from that day into TBC. Set the next layer, rinse and repeat. I don't know that this would work...but it might.
