[ gpsdrive ] conversion of tracks saved by gpsdrive (incremental.sav) to GPX?

Gernot Hillier gernot at hillier.de
Fri Jan 11 23:02:38 AKST 2008


Hi!

Guenther Meyer schrieb:
> Am Freitag 11 Januar 2008 schrieb Kim Hawtin:
>>>> If you run gpsdrive 2.10pre4 w/o MySQL supports, it seems to write
>>>> recorded tracks to a file called incremental.sav.
>>>>
> just a hint: when you toggle the "save track" checkbox, you can get separate 
> files for your tracks...

Hmm, probably this didn't work in 2.10pre4? At least I toggled this
checkbox a lot of times already and never got an additional file.
Incremental.sav already stores tracks of weeks :)

>>>> It seems the "gpsdrive" and "gpsdrivetrack" filters of gpsbabel don't
>>>> work correctly for incremental.sav, at least with gpsbabel 1.3.3 (and
[...]
> I had the same problem with gpsbabel, but your script works great :-)

Well, I looked into the gpsbabel stuff and it seems to be non-trivial to
get it running for gpsdrive. The problem is that they have a sort of
formal method to describe such ASCII files.

There you have to state that incremental.sav uses WHITESPACEs as field
delimiters. But, as gpsdrive uses %10.6f as format string to write the
latitude at the beginning of the line, you may end up with something like:
 48.543723  12.132512        445 Fri Jan 11 11:14:11 2008

And this is impossible to describe correctly in the formal format of
gpsbabel as the leading blank is ambiguous - it may be a field delimiter
as well as part of the field data.

> another tool, hmm, let's see... yes, I have something here, it's called 
> gpsdrive ;-)
> my current gpsdrive version can export a recorded track directly to gpx.
> this also works for loaded gpsdrive track files.
> I guess it will be in the svn at sunday.

That's great news to hear! From a programmer's standpoint, I think the
current data format for writing tracks isn't optimal as we have this
ambiguity described above...

BTW: I'd love to see if gpsdrive would also log the number of satellites
used to receive the point as well as the HDOP. This may be used to
filter the recorded tracks before uploading to OSM so that we only get
accurate track points.

I have a tool which converts the tracklogs from my Medion GoPal device
and they do exactly this: they'll only write points to the output GPX
file if we saw at least 5 satellites with a HDOP<2.5.

--
Gernot


More information about the GPSdrive mailing list