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

[Guenther Meyer]

Am Samstag 12 Januar 2008 schrieb Gernot Hillier:
> 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.
>
I changed the format in the svn, so whitespaces should work now as delimiters.
the fields are described in Documentation/README.tracks

> 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.
>
in the svn version the number of satellites used, hdop, fix type, course and 
speed is included if available.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.gpsdrivers.org/pipermail/gpsdrive/attachments/20080115/eaad0423/attachment.bin