Trimble Business Center

ian bissonnette posted 12-06-2024 09:08

couple questions that might not matter but might help.

 are you seeing this just after the import or did you run the baseline processing and are you seeing the baselines between leica finding a solution in the processor? (fixed results). maybe check the settings in the processor too, but from memory i can t think of anything there.  

did you just drag the rinex files in or use the importer. using the importer and the hidden dropdown to “force static” has helped me in the past. but not specifically on what you are seeing. 

Serg Chirila posted 12-06-2024 13:29

Thanks for the suggestions Ian. 

I am seeing this just after the import. I have tried dragging the files in and using the importer, the result is the same. I have tried the force static option and still have the same result. The processor settings look normal. 

ian bissonnette posted 12-07-2024 09:13

i think you are seeing the ties the data collector ‘knows’ about. try running the baseline processor and see what solutions you get. 

ian bissonnette posted 12-07-2024 18:27

another question just to make sure we are not missing something simple. during the rinex import are you getting a prompt with the data check in for point numbers and antennae heights??

it might look a bit funny because usually a random point number is generated, i think it often uses the serial number of the gps head. make sure all are confirmed that you want to import. i think i often look at the duration of the observations to weed out anything funny(if the head was used for other work during that day). then change to the correct number after import and merge with other data. these points will also be off of the other observations because the initial autonomous position is used as a starting point. (maybe you deleted them after import??? as another posibility?)

sorry if i am stating the obvious, just don t know all the details of what is going on and how much experience you have with this stuff. good luck. 

Dave Olander posted 12-09-2024 08:25

You probably know this but just in case, Rinex doesn't contain ephemeris data, but the Trimble native (.t02 and similar) do.

Therefore, if the Leica data was taken at a significantly different time than the Trimble data I would suspect that you don't have an orbit for the missing data. Simple fix is to go the internet download and download the missing files. You will be able to get the broadcast and rapid orbits, but might not get final orbits unless the data is about 2 weeks old. Depending on the source it also may not include all the constellations.

It has been several years since I did any static GNSS processing, but I think that MGEX is the place to get it now. When I transitioned to a different role, IGS was pretty dated, but maybe they have added stuff. Also, keep an eye on the time frame, if the data spans over month or 2, you'll probably want to do separate downloads for each session or blocks of sessions, but if it is all in about a month or less, just let it download orbits for the whole time frame.

Bob Epstein posted 12-09-2024 10:37

Regarding the ephemeris (or lack thereof):

I agree with Dave, MGEX is the first place to go for orbits as it covers multiple constellations. TBC has updated the Internet connection and is now quite reliable. It can only help and never hurts.

My fallback is the Trimble Global Tracking Network. Although not quite as good, it will get you by if you don’t have the orbits and is available quickly. For our fast static processing with short baselines, it gives about the same results.

Serg Chirila posted 12-09-2024 11:37

Hi all,

Thank you for your contributions to this post. I did receive ephemeris files as part of the deliverable, but I also tried downloading data from sources like MGEX in case the provided files were corrupt.

In the end, I found a workaround to view the baselines. I imported the .24o files and applied the "force static" option using the importer. Then, I started a separate job and imported the same files again without the "force static" option. By merging the two jobs, the baselines came through. From what I can gather, without using the importer and the "force static" option, the setups over survey marks that collected data for 6+ hours do not come through. 

In retrospect, the issue in my original post is likely related to user error/lack of experience with other file types. I have only used the likes of t.02 and t.04 files from Trimble where I "drag and drop" them in the software and the baselines show up.