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

[Sascha Silbe]

On Sat, Jan 12, 2008 at 09:02:23AM +0100, Gernot Hillier wrote:

> 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.

You could preprocess your current incremental.sav using some command 
line tools so gpsbabel can parse it:

tr -s ' ' < ~/.gpsdrive/incremental.sav | sed -e 's/^ *//' > 
incremental.sav.new

This should create a file "incremental.sav.new" that uses exactly one 
space as field delimiter.


GPX support for GPSDrive is even better, of course, though I highly 
recommend compression since GPX files are very verbose and get huge 
quite fast. One of my logs in GPX format is 3.5M uncompressed and 151K 
gzipped; with bzip2 it would only be 111k, but take much more time for 
compression. If you can append to the compressed file on-the-fly (i.e. 
as new data gets added), the slowdown probably isn't noticeably, though.


PS @Thomas: Sorry, didn't have time to look at the speed code yet.

CU Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.gpsdrivers.org/pipermail/gpsdrive/attachments/20080112/3d8e607a/attachment.bin