gpsd-dev
[Top][All Lists]
Advanced

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

Re: Invalid position given by Telit HE910-EUG


From: Gary E. Miller
Subject: Re: Invalid position given by Telit HE910-EUG
Date: Fri, 3 Apr 2020 19:51:06 -0700

Yo Titouan!

On Fri, 3 Apr 2020 18:02:16 +0200
Titouan Christophe <address@hidden> wrote:

> See 2 sentences obtained from gpspipe below:
> 
> # Normal position (51__26.953'N)
> $GPRMC,120212.953,A,5126.1926,N,00758.5483,E,0.01,0.0,180800,,,A*5F
> # 1s after: invalid position (153__35.322'N)
> $GPRMC,120213.953,A,15335.322,N,00758.5483,E,0.01,269.58,180800,,,A*60

I fed those into gpsd, and this is the result:

$GPRMC,120212.953,A,5126.1926,N,00758.5483,E,0.01,0.0,180800,,,A*5F
{"class":"TPV","mode":2,"time":"2020-04-03T12:02:12.953Z","ept":0.005,"lat":51.436543333,"lon":7.975805000,"track":0.0000,"magtrack":2.4295,"magvar":2.4,"speed":0.005}
$GPRMC,120213.953,A,15335.322,N,00758.5483,E,0.01,269.58,180800,,,A*60
{"class":"TPV","mode":2,"time":"2020-04-03T12:02:13.953Z","ept":0.005,"track":269.5800,"speed":0.005}

So gpsd DID filter out the bad data.

You are looking at the unfiltered bad data IN to gpsd.  The data OUT
of gpsd is properly cleaned.

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: pgpjLtSjL_b6c.pgp
Description: OpenPGP digital signature


reply via email to

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