time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

tracking position & orientation

MS
Mark Sims
Sat, Nov 23, 2019 12:06 AM

NRCAN / csrs-ppp will do L1 only data.  Typical results have errror ellipses in the 300-500 mm range.  It also seems to be the only free site that handles RINEX V3.xx data.  They only use GPS and GLONASS measurements,


I do not know of any free sites that will post process “L1 only” data. Without

post processing, you will not get mm level results.

NRCAN / csrs-ppp will do L1 only data. Typical results have errror ellipses in the 300-500 mm range. It also seems to be the only free site that handles RINEX V3.xx data. They only use GPS and GLONASS measurements, -------------- >I do not know of any free sites that will post process “L1 only” data. Without post processing, you will not get mm level results.
PK
Poul-Henning Kamp
Sat, Nov 23, 2019 7:22 AM

NRCAN / csrs-ppp will do L1 only data.  Typical results have errror ellipses in the 300-500 mm range.

Then your RINEX files must have some flaw in them.

NRCAN process both L1 and L2:

OBS G L1C L2C C1C C2C

I get horizongal uncertainties of around a centimenter and vertical around 2cm:

POS CRD  SYST        EPOCH          A_PRIORI         ESTIMATED       DIFF SIGMA(95%) CORRELATIONS
POS   X IGS14 19:301:62520      3558657.3400      3558658.2826     0.9426     0.0130  1.0000
POS   Y IGS14 19:301:62520       713469.6500       713470.3210     0.6710     0.0081  0.3067  1.0000
POS   Z IGS14 19:301:62520      5227269.8000      5227271.1311     1.3311     0.0133  0.8625  0.2978  1.0000

--
Poul-Henning Kamp      | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG        | TCP/IP since RFC 956
FreeBSD committer      | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

-------- In message <SN1PR07MB390174DFEF62F4BF054C814ACE480@SN1PR07MB3901.namprd07.prod.outlook.com>, Mark Sims writes: >NRCAN / csrs-ppp will do L1 only data. Typical results have errror ellipses in the 300-500 mm range. Then your RINEX files must have some flaw in them. NRCAN process both L1 and L2: OBS G L1C L2C C1C C2C I get horizongal uncertainties of around a centimenter and vertical around 2cm: POS CRD SYST EPOCH A_PRIORI ESTIMATED DIFF SIGMA(95%) CORRELATIONS POS X IGS14 19:301:62520 3558657.3400 3558658.2826 0.9426 0.0130 1.0000 POS Y IGS14 19:301:62520 713469.6500 713470.3210 0.6710 0.0081 0.3067 1.0000 POS Z IGS14 19:301:62520 5227269.8000 5227271.1311 1.3311 0.0133 0.8625 0.2978 1.0000 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
B
Björn
Sat, Nov 23, 2019 10:49 PM

No... NRCAN is one of the few that do not require both L1 and L2 observables. It also accepts only L1.  /Björn

Sent from my iPhone

On 23 Nov 2019, at 08:22, Poul-Henning Kamp phk@phk.freebsd.dk wrote:


In message SN1PR07MB390174DFEF62F4BF054C814ACE480@SN1PR07MB3901.namprd07.prod.outlook.com, Mark Sims writes:

NRCAN / csrs-ppp will do L1 only data.  Typical results have errror ellipses in the 300-500 mm range.

Then your RINEX files must have some flaw in them.

NRCAN process both L1 and L2:

OBS G L1C L2C C1C C2C

I get horizongal uncertainties of around a centimenter and vertical around 2cm:

POS CRD  SYST        EPOCH          A_PRIORI         ESTIMATED       DIFF SIGMA(95%) CORRELATIONS
POS   X IGS14 19:301:62520      3558657.3400      3558658.2826     0.9426     0.0130  1.0000
POS   Y IGS14 19:301:62520       713469.6500       713470.3210     0.6710     0.0081  0.3067  1.0000
POS   Z IGS14 19:301:62520      5227269.8000      5227271.1311     1.3311     0.0133  0.8625  0.2978  1.0000

--
Poul-Henning Kamp      | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG        | TCP/IP since RFC 956
FreeBSD committer      | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.


time-nuts mailing list -- time-nuts@lists.febo.com
To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com
and follow the instructions there.

No... NRCAN is one of the few that do not require both L1 and L2 observables. It also accepts only L1. /Björn Sent from my iPhone > On 23 Nov 2019, at 08:22, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote: > > -------- > In message <SN1PR07MB390174DFEF62F4BF054C814ACE480@SN1PR07MB3901.namprd07.prod.outlook.com>, Mark Sims writes: > >> NRCAN / csrs-ppp will do L1 only data. Typical results have errror ellipses in the 300-500 mm range. > > Then your RINEX files must have some flaw in them. > > NRCAN process both L1 and L2: > > OBS G L1C L2C C1C C2C > > I get horizongal uncertainties of around a centimenter and vertical around 2cm: > > POS CRD SYST EPOCH A_PRIORI ESTIMATED DIFF SIGMA(95%) CORRELATIONS > POS X IGS14 19:301:62520 3558657.3400 3558658.2826 0.9426 0.0130 1.0000 > POS Y IGS14 19:301:62520 713469.6500 713470.3210 0.6710 0.0081 0.3067 1.0000 > POS Z IGS14 19:301:62520 5227269.8000 5227271.1311 1.3311 0.0133 0.8625 0.2978 1.0000 > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > _______________________________________________ > time-nuts mailing list -- time-nuts@lists.febo.com > To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com > and follow the instructions there.
PK
Poul-Henning Kamp
Sat, Nov 23, 2019 11:16 PM

Sorry, I read it as "NRCAN wil only do L1"

--
Poul-Henning Kamp      | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG        | TCP/IP since RFC 956
FreeBSD committer      | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

-------- Sorry, I read it as "NRCAN wil *only* do L1" -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.