RINEX files not on even seconds (continued)

[jjb (juan borda)]

Got this from Emlid awhile back. It’s message #43/51 of this thread.

RINEX files not on even seconds

Hi Juan, Sorry it took so long to get back to you. We’ve found a way to convert RINEX data from Reach RS2 so that the time becomes an integer. To get the integer time in RINEX data, you should specify the -TADJ=0.1 option in the Receiver Options field in RTKConv Options as it’s shown on the screenshot below: [11] However, this is not required for OPUS as it accepts standard RINEX data recorded on Reach RS2. According to AUSPOS, their service can’t work with L2C data. Therefore Reach logs w…

It interpolates the GPS data to even seconds. Kind of like the Decimate program to trim down excess observations from RINEX files.

It has been called by several users, me included, that this is not normal data from other major GPS brands. If you set time interval to 1 second recording, then you get even second reading from topcon,sokkia, leica units.

Problem arises when you try to integrate the GPS data with other sensors that are recording in even seconds like bathymetry, drone, IMU data that are not linked real time.

@tatiana.andreeva , I really hope that you could fix this in hardware instead of doing it in software. I noticed that there is a slight difference between the 2 sets (even & decimal time stamps) when processed by OPUS.