gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gpsrinex - smaller than 1s epoch interval


From: Gary E. Miller
Subject: Re: gpsrinex - smaller than 1s epoch interval
Date: Thu, 21 May 2020 13:47:38 -0700

Yo All!

So I took 1,000 epochs of RAWX data, at a 10 HZ rate, from a ZED-F9P,
and converted it to RINEX with gpsrinx.  Then submitted to NRCAN
for static and kinetic PPP processing.

Both worked fine, for some definition of fine.

Initially the kinematic data returned:

Warning : Only your GPS RINEX data are processed. A combined GPS, GLONASS
 solution will be performed once the necessary GLONASS products are available.
Warning : Single-frequency only solution in kinematic mode. Please check
 your results.
Warning : Approximate position in RINEX header record was not used. Current
 solution is using a priori position initialized using a pseudo-range only
 solution.


Then later, NRCAN returned:

Warning : Your combined GPS, GLONASS RINEX observation file has been
 processed with the available GLONASS products.
Warning : Single-frequency only solution in kinematic mode. Please check
 your results.
Warning : Approximate position in RINEX header record was not used.
 Current solution is using a priori position initialized using a
 pseudo-range only solution.


So the kinematic PPP solution is GPS L1 and GLONASS L1 only.  Thus making
the L2 capable ZED-F9P overkill.  Very disappointing.

When I submitted the 10 Hz RINEX to NRCAN for static PPP, they gave me
kinamatic PPP instead.  Maybe too few epochs.

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

Attachment: pgp0Na4ggfVQb.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]