[Top][All Lists]

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

Re: gpsprof: higher resolution

From: Gerry Creager - NOAA Affiliate
Subject: Re: gpsprof: higher resolution
Date: Mon, 17 Aug 2020 22:32:38 +0000


What would you like specifics on? Besides decimation... 

Decimation does indeed mean dropping at least consecutive positions, especially when they're not presented on the satellite observables. I'll let you read about autocorrelation of measurements if you're not already aware of the concept. Simply put, most GPS's providing code-phase positioning use the last determination as a first-guess for the next determination, and then account for movement, consistent movement vectors, etc., If you're trying to determine position with NMEA output, this becomes a problem and you'll see some wandering of position. 

If you're using raw observables this is not an issue, although the geodetic processing I've used tended to randomly remove an observation or two to decouple obs. 

I can go into more detail if desired.

gerry n5jxs

On Sun, Aug 16, 2020 at 14:59 Hal Murray <> wrote: said:

> Also, a caveat I'm sure you're aware of, is before you simply average your

> NMEA data, decimate it to reduce the impact of autocorrelation in the

> standard position output.

Could you please say more.  That sounds like something I should understand but

I don't get it.

What does "decimate" mean in that context?  Do I just throw away 9 out of 10

samples?  Or average blocks of 10 then take their average?  The latter sounds

like a dodge for numerical precision.  My back of the envelope says it should

fit in a double.

How does autocorrelation get involved and/or how does it screw things up?


These are my opinions.  I hate spam.

reply via email to

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