Hi,
I'm trying to use gpxlogger (-V: SVN ID: $Id: gpxlogger.c 5326 2009-03-02
23:24:03Z esr $ ) on a debian box with an old no-name mouse GPS
(
http://www.geeks.com/details.asp?invtid=MS-GM-03&cat=CON) and the
'jitter' apparently breaks things up into several tracks per
second--rotating between tracks for a 3d fix, 2d fix, and 3d fixes with
corrupted time-stamp. (sample fragment below)
I've tried the -j flag, but its usage seems odd as compared to the other
clients in that it requires an argument:
gpxlogger -j
gpxlogger: option requires an argument -- 'j'
Usage: gpxlogger [-V] [-h] [-i timeout] [-j casoc]
[server[:port:[device]]]
defaults to 'gpxlogger -i 5 -j 0 127.0.0.1:2947'
doing a 'gpxlogger -j=1' or 'gpxlogger -j 1' seems to not fault, but I
still get similarly jittery track logs.
Is my GPS particularly jittery, or is there some other -j parameter value
I should try?
Dave
--
David Forrest P.E., Ph.D. (804)684-7900w
drf@... (804)413-2882c
drf5n@... (804)642-0662h
http://maplepark.com/~drf5n/### sample fragment with 3 tracks in 1 second ###
<trk>
<trkseg>
<trkpt lat="37.247307" lon="-76.501325">
<ele>224.900000</ele>
<time>2009-10-23T17:51:43Z</time>
<fix>3d</fix>
</trkpt>
</trkseg>
</trk>
<trk>
<trkseg>
<trkpt lat="nan" lon="nan">
<ele>nan</ele>
<time>-219246529-25297425-129T08:29:52Z</time>
<fix>3d</fix>
</trkpt>
</trkseg>
</trk>
<trk>
<trkseg>
<trkpt lat="37.247307" lon="-76.501325">
<ele>nan</ele>
<time>2009-10-23T17:51:43Z</time>
<fix>2d</fix>
</trkpt>
<trkpt lat="37.247308" lon="-76.501322">
<ele>224.500000</ele>
<time>2009-10-23T17:51:44Z</time>
<fix>3d</fix>
</trkpt>
</trkseg>
</trk>
_______________________________________________
Gpsd-users mailing list
Gpsd-users@...
https://lists.berlios.de/mailman/listinfo/gpsd-users