Re: gpsrinex epoch timestamps look wrong

[Gary E. Miller]

Yo Poul-Henning!

On Tue, 28 Apr 2020 11:49:44 +0000
"Poul-Henning Kamp" <address@hidden> wrote:

> > Except, you have no fix:  
> 
> Correct, the antenna normally belongs to the NovaTel Oem2 which
> feeds into rtk2go.com

Not gonna get PPP without a fix...

> I looked at the old RINEX I managed to get throug NRCAN last year and
> that seems to have the same issue, and yet they processed it using the
> fractional timestamps.

Hard to say without seeing your RINEX file.

> If we assume for a moment that they do not require the timestamps
> to be perfeclty on top of the second, but they need them to be close
> to 30 seconds apart, then maybe the code in gpsrinex.c which selects
> which observations to save should take the fraction into account
> so that instead of:

They do no need to be 30 sweconds apart.  But only the data that is
exactly modulo 30 seconds is used.  The rest is, almost, silently
ignored.

>       gpsrinex2020025225827.obs:> 2020 01 26 01 34 30.0000000  0 13
>       gpsrinex2020025225827.obs:> 2020 01 26 01 35 00.0000000  0 13
>       gpsrinex2020025225827.obs:> 2020 01 26 01 35 30.0000000  0 13
>       gpsrinex2020025225827.obs:> 2020 01 26 01 36 00.0000000  0 13
>       gpsrinex2020025225827.obs:> 2020 01 26 01 36 30.0000000  0 13
>       gpsrinex2020025225827.obs:> 2020 01 26 01 37 00.0000000  0 13

So those are perfect!

> it would have picked:
>       gpsrinex2020025225827.obs:> 2020 01 26 01 37 01.0000000  0 13
>  
> 
> Thus avoiding the 29 second interval ?

And failing becasue they are not mudulo 30 seconds.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpu60T0xNj7P.pgp
Description: OpenPGP digital signature