gmane.comp.hardware.gps.gpsbabel.devel

patch for linux gui

tsteven4 — 2012-05-19T22:38:39

While my bias is towards the command line I like the preview available 
in the gui which led me to build it on centos 6.

I needed a few changes to make the linux distribution.  Some of these 
parallel the changes in setup.iss from r4096.  These are included in the 
patch.

I need other changes to build on my system, but at least some of these 
are system dependent.
1. Change QTLIBDIR, QTSHDIR.  It would be better to get the necessary 
information from "qmake -query QT_INSTALL_TRANSLATIONS" and "qmake 
-query QT_INSTALL_PLUGINS", at least with qt4, and make appropriate 
changes where these variables are used.
2. comment out libphonon and libaudio.  These are not dynamically loaded 
by the fe when I compile it, and if the ldd|grep|awk returns nothing 
then the script bombs.  I don't know if these are ever needed, or if 
that they just  weren't on my system.
3. for me the plugins were in another path, but see 1. above.
4. with qt4 on my system lrelease is named lrelease-qt4.


I also note that  ../../babelweb does not exist.  I left this in because 
it seems like a reminder that work needs to be done wrt help and it 
didn't cause the script to bomb.

Index: gui/makelinuxdist.sh.in
===================================================================
--- gui/makelinuxdist.sh.in(revision 4182)
+++ gui/makelinuxdist.sh.in(working copy)
< at >< at > -24,24 +24,13 < at >< at >
 cp $QTSHDIR/translations/qt_*.qm $DISTDIR/translations/
 
 # Generate the compiled translations
-TSFILES="gpsbabel_de.ts 
-gpsbabel_es.ts 
-gpsbabel_fr.ts 
-gpsbabel_hu.ts 
-gpsbabel_it.ts 
-gpsbabelfe_de.ts 
-gpsbabelfe_es.ts 
-gpsbabelfe_fr.ts 
-gpsbabelfe_hu.ts 
-gpsbabelfe_it.ts"
+TSFILES=`ls gpsbabel_*.ts gpsbabelfe_*.ts`
 
 #
 lrelease $TSFILES
 QMFILES=`echo $TSFILES | sed -e 's/\.ts/.qm/g'`
 cp $TSFILES $DISTDIR/translations
-#
-# Only Spanish and German are moderately OK.
-cp gpsbabel_es.ts gpsbabelfe_es.ts gpsbabel_de.ts gpsbabelfe_de.ts $DISTDIR/translations
+cp $QMFILES $DISTDIR/translations
 
 # Now our gui
 cp gmapbase.html $DISTDIR/
< at >< at > -54,7 +43,7 < at >< at >
 # Help needs to be donea
 cp ../../babelweb/htmldoc-development/* $DISTDIR/help/
 
-cp COPYING $DISTDIR/
+cp COPYING.txt $DISTDIR
 #cp AUTHORS $DISTDIR/
 #cp README.contrib $DISTDIR/
 #cp README.gui $DISTDIR/
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

test on skytraq-artificial.gpx failing

Bernd Zeimetz — 2012-05-18T09:31:23

hi,

in the current trunk (and since adding the test
Running testo.d/skytraq.test
--- /tmp/gpsbabel.21809/skytraq-artificial.gpx2012-05-18 11:23:53.131458101 +0200
+++ ./reference/skytraq-artificial.gpx2012-05-18 11:12:50.347645329 +0200
< at >< at > -82,7 +82,7 < at >< at >
 </trkpt>
 <trkpt lat="47.547749767" lon="9.679499575">
   <ele>435.413042</ele>
-  <time>2009-09-10T03:07:53Z</time>
+  <time>2009-09-10T21:20:09Z</time>
   <speed>0.000000</speed>
   <name>TP0009</name>
 </trkpt>
< at >< at > -232,7 +232,7 < at >< at >
 </trkpt>
 <trkpt lat="-30.376946121" lon="-97.665030673">
   <ele>185.882330</ele>
-  <time>2019-04-05T18:25:39Z</time>
+  <time>2019-04-06T12:37:55Z</time>
   <speed>55.555557</speed>
   <name>TP0034</name>
 </trkpt>
ERROR comparing /tmp/gpsbabel.21809/skytraq-artificial.gpx
./reference/skytraq-artificial.gpx

r4178 fixed most of the issues, but these two still show up.
I could try to find out what the reason for that is, but first I would prefer if
somebody ensures that the skytraq-artificial.gpx is valid and what I see is a
real issue.

Cheers,

Bernd

clang scan-build report of gpsbabel

Bernd Zeimetz — 2012-05-17T12:50:20

Hi,

I've built gpsbabel with clang's scan-build, the current report (which shows 207
bugs) is available at

http://devel.recluse.de/scan-build/gpsbabel/

For now I'll rebuild the sources every night and a new report will be generated,
assuming there is some interest to fix those bugs :)

Cheers,

Bernd

Bad CRC with Qstarz travel recorder EX

Dirk Stichling — 2012-05-09T16:31:09

Hi.

A user of my application myTracks (which uses gpsbabel internally) reports that he has problems with his Qstarz travel recorder EX. The mtk driver of gpsbabel is used for the communication. Reading tracks from the logger works fine as long as the memory of the logger is not too full. But when the memory reaches about 50% gpsbabel reports "bad CRC" errors.

I did some research on the net and found a discussion on that topic (http://old.nabble.com/Error-reading-BT-Q100P-when-more-than-50--td22123960.html).

Now my question is whether this problem has not yet been addressed? If not, is there anything I can do to help solving the problem?

Thanks,
Dirk


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Problem with Columbus V900 (with link)

Dirk Stichling — 2012-05-08T17:13:31

Hi.

I have a problem with the following CSV file from a Columbus V900:
http://www.mytracks4mac.com/tmp/V900.CSV

It results in the following assertion:
v900.c:364: failed assertion `line.bas.common.tag == 'C' || line.bas.common.tag == 'V''

When I comment out that assertion everything seems to be fine.

Can anybody check that?

Dirk

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Problem with Columbus V900

Dirk Stichling — 2012-05-08T17:08:58

Hi.

I have a problem with the attached CSV file from a Columbus V900. It results in the following assertion:
v900.c:364: failed assertion `line.bas.common.tag == 'C' || line.bas.common.tag == 'V''

When I comment out that assertion everything seems to be fine.

Can anybody check that?

Dirk



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Patch to add "discard" option to track filter

Tom Paton — 2012-05-04T11:07:24

Hi,

This is revisiting something I attempted a few years back, I think
I've got it working this time (with some help from a friend).

The patch adds a "discard" option to the "-x track,merge" filter that
suppresses the "Found track point at lat,lon without time!" error and
instead just drops the points.

I've attached a zip that includes the diff to trackfilter.c (as at svn
revision 4173) and a test script and test files.  I also tried adding
a documentation file, but I'm not sure how to make that work.  Is
anything else needed?

Also, on a side note, I had problems running the test scripts that I
think is probably timezone related: The reference output files didn't
match due to the dates being off by one day (I'm UTC+10). Is that
something there's a workaround for or just something that no one's
bumped into yet?

Kind regards,

Tom
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

bug with reverse filter and tracks

tsteven4 — 2012-05-03T12:59:56

There is a bug with the reverse filter when applied to tracks.  It 
effects output formats kml and gpx, causing invalid xml to be produced 
due to mismatched tags.  This results because  wpt_flags.new_trkseg is 
not updated when the track is reversed.  The new_trkseg flag should be 
set at, and only at, the start of each track segment, but after reversal 
it is set only at the end of each track segment (which was the start 
before reversal).  I am thinking about a fix but I don't have anything yet.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

BUG+PATCH: garmit-fit with extra header data fails

Niobos — 2012-05-01T13:23:22

The FIT files of my "Garmin Edge 200" contain two additional header
bytes. This patch does account for extra header bytes, but ignores them.

Greetings,
Niobos


PS: You should update the README.contrib: it says to make patches with
`cvs`, while the current code is in SVN.

Index: gpsbabel/garmin_fit.c
===================================================================
--- gpsbabel/garmin_fit.c(revision 4172)
+++ gpsbabel/garmin_fit.c(working copy)
< at >< at > -96,6 +96,12 < at >< at >
   if (sig[0] != '.' || sig[1] != 'F' || sig[2] != 'I' || sig[3] != 'T') {
     fatal(MYNAME ": .FIT signature missing\n");
   }
+
+  // Read in rest of header (if any)
+  len -= 12;
+  while( len-- ) {
+    gbfgetc(fin); // throw away unknown header data
+  }
 }
 
 static gbuint8

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

obsolete files

tsteven4 — 2012-04-28T21:47:39

It appears to me that tpo.README.patch and tpo.testo.patch are obsolete 
and should be deleted.  They were introduced in r1509, Oct 31 2005.

svn delete tpo.README.patch
svn delete tpo.testo.patch



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

bad gpx introduced with r4167, r4168, r4170 "Steve from Climber adds line style handling in TPO3."

tsteven4 — 2012-04-28T19:25:56

The reference file LineStyles.gpx is invalid.  The ^K (#xB vertical tab) 
characters are not allowed.  The reference files LineStypes.gpx and 
LineStyles.kml are created by gpsbabel when building the target check:
   I note that r4170 (Steve adds line styling to TPO3 reader. Hacked KML 
writer to discard control characters in a description.)  may have been 
dealing with this issue in the kml output, but it was not dealt with in 
other output xml formats such as gpx.  Furthermore, I believe that some 
of the control characters discarded by the kml "hack" may be legal.  
Note that the ^M (carriage return) characters are not detected as 
invalid in either the gpx or the kml (before r4170 stripped them).  In 
general 3 characters with values less than #x20 (space) are allowed in 
strings, there is a fairly long series of specs that often comes down to 
http://www.w3.org/TR/2000/WD-xml-2e-20000814#charsets which allows |#x9 
| #xA | #xD  (horizontal tab, |line feed, carriage return).||  Perhaps a 
fix can be found that both corrects the issue for all xml output formats 
and does not strip legal characters.  This may have been part of what 
Steve from Climber had in mind when he wrote in kml.c:

Regarding LineStyles.gpx my Xerces C based validator returns:


and xmllint returns:

The relevant lines of LineStyles.gpx are:

As of r4171 LineStyles.gpx is the only invalid gpx reference file.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

gpx test patch

tsteven4 — 2012-04-28T01:14:22

This patch fixes a reference test input so that it is valid.  This is a 
reordering of the fix and type elements. The output of the test is not 
currently compared due to issues noted in testo.d/subrip.test.


Index: reference/track/gpx_subsecond-sample.gpx
===================================================================
--- reference/track/gpx_subsecond-sample.gpx(revision 4170)
+++ reference/track/gpx_subsecond-sample.gpx(working copy)
< at >< at > -14,40 +14,40 < at >< at >
   <time>2011-07-02T17:47:25Z</time>
   <speed>13.818100</speed>
   <name>trkpt-2011-07-02T17:47:25.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794710000" lon="9.833996000">
   <ele>289.300000</ele>
   <time>2011-07-02T17:47:25Z</time>
   <speed>14.049800</speed>
   <name>trkpt-2011-07-02T17:47:25.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794734000" lon="9.833976000">
   <ele>289.300000</ele>
   <time>2011-07-02T17:47:25Z</time>
   <speed>14.161100</speed>
   <name>trkpt-2011-07-02T17:47:25.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794758000" lon="9.833955000">
   <ele>289.400000</ele>
   <time>2011-07-02T17:47:25Z</time>
   <speed>14.090400</speed>
   <name>trkpt-2011-07-02T17:47:25.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794782000" lon="9.833934000">
   <ele>289.500000</ele>
   <time>2011-07-02T17:47:25Z</time>
   <speed>14.183800</speed>
   <name>trkpt-2011-07-02T17:47:25.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <!--
 <trkpt lat="49.794807000" lon="9.833916000">
< at >< at > -55,40 +55,40 < at >< at >
   <time>2011-07-02T17:47:26Z</time>
   <speed>14.208100</speed>
   <name>trkpt-2011-07-02T17:47:26.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794831000" lon="9.833898000">
   <ele>289.800000</ele>
   <time>2011-07-02T17:47:26Z</time>
   <speed>14.272600</speed>
   <name>trkpt-2011-07-02T17:47:26.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794856000" lon="9.833881000">
   <ele>289.800000</ele>
   <time>2011-07-02T17:47:26Z</time>
   <speed>14.279100</speed>
   <name>trkpt-2011-07-02T17:47:26.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794880000" lon="9.833863000">
   <ele>289.800000</ele>
   <time>2011-07-02T17:47:26Z</time>
   <speed>14.085500</speed>
   <name>trkpt-2011-07-02T17:47:26.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 <trkpt lat="49.794904000" lon="9.833847000">
   <ele>289.800000</ele>
   <time>2011-07-02T17:47:26Z</time>
   <speed>12.700900</speed>
   <name>trkpt-2011-07-02T17:47:26.000Z</name>
+  <type>T</type>
   <fix>3d</fix>
-<type>T</type>
 </trkpt>
 -->
 </trkseg>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Internal styles conflicting with custom xcsv styles?

Tom Paton — 2012-04-09T10:52:02

Hi,

Just ran into a little issue and I'm wondering if a) i'm doing
something wrong, b) there's a simple work around someone can think of,
or c) it's just a bug...

I'm currently using gpsbabel 1.4.2 and if I read from a file defined
using the xcsv internal styles (e.g. garmin301) and then try to
convert using a custom xcsv style file, the custom style file is
ignored and the output is in the same format as the input.

I suspect anyone familiar with the code can track down the issue
faster than they can reproduce my test case, somewhere around
xcsv.c:566 is my guess.

tom< at >neon:~/dev/gpsbabel/gpsbabel-1.4.2$ cat ~/garmin301.example
Garmin 301 data
Timestamp,Latitude, Longitude, Altitude(ft), heart rate
1280310051,31.158194,121.423790,93.832022F, 0
1280310052,31.158197,121.423798,93.832022F, 0
1280310053,31.158196,121.423859,93.832022F, 0
1280310054,31.158222,121.424141,93.832022F, 0
1280310056,31.158243,121.423981,93.832022F, 0
1280310057,31.158642,121.424347,93.832022F, 0
1280310058,31.158548,121.424095,93.832022F, 0
1280310059,31.158476,121.424080,93.832022F, 0

gpsbabel ignores any specified custom xcsv style file and outputs in
the garmin301.style format:

tom< at >neon:~/dev/gpsbabel/gpsbabel-1.4.2$ gpsbabel -i garmin301 -f
~/garmin301.example -o xcsv,style=style/csv.style -F -
Garmin 301 data -
Timestamp,Latitude, Longitude, Altitude(ft), heart rate
1280310051,31.158194,121.423790,93.832022F, 0
1280310052,31.158197,121.423798,93.832022F, 0
1280310053,31.158196,121.423859,93.832022F, 0
1280310054,31.158222,121.424141,93.832022F, 0
1280310056,31.158243,121.423981,93.832022F, 0
1280310057,31.158642,121.424347,93.832022F, 0
1280310058,31.158548,121.424095,93.832022F, 0
1280310059,31.158476,121.424080,93.832022F, 0

Outputting to another internal style works ok though:

tom< at >neon:~/dev/gpsbabel/gpsbabel-1.4.2$ gpsbabel -i garmin301 -f
~/garmin301.example -o csv -F -
31.15819, 121.42379, WPT001
31.15820, 121.42380, WPT002
31.15820, 121.42386, WPT003
31.15822, 121.42414, WPT004
31.15824, 121.42398, WPT005
31.15864, 121.42435, WPT006
31.15855, 121.42409, WPT007
31.15848, 121.42408, WPT008

Thanks in advance,

Tom

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2

Topo line color now works in KML out! Re: enhancement for Nat Geo "Topo" files

Steve — 2012-03-31T19:25:24

Ah-HAH! That was the hint I needed!
I had searched for gb_color, which I didn't find anywhere.

KML output now accurately contains the correct line color and line width
for Topo tracks. Here's an example (turn off the points to see the color):
   http://g.co/maps/f3hkp
I've mapped dashed lines into semi-transparent (regular lines have opacity
of 255=0xff, dashed lines have opacity 0x50) so all the Topo line style
info is there in one form or another. It turns out KML output really does
respect per-track line style and doesn't need command-line options... as
long as the input module loads ->line_width and ->line_color.bbggrr )with
or without ->line_color.opacity).

I'll need your help again to check in the new source. (see other email)

Thanks for staying engaged while I came up the learning curve! It's
daunting to fiddle with code that's been around this many years, but
yesterday's exchange broke the log jam.

Now, about adding color to GPX output... any hints about Garmin extensions
like the depth extension you already have? Maybe it's not such a big deal
since a couple of sed passes can get the description I'm writing into
MapSource as color, but it would be cleaner and more general to handle
color from ANY source, not just from Topo.

Steve



------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

enhancement for Nat Geo "Topo" files

Steve — 2012-03-21T16:34:16

New to the list, please excuse if this is the wrong place to post!

I've modified tpo.c to read freehand route line styles (color,
width, dashed or solid) from .tpo files (the tpo3 format). The
code was already in place to find the style block, all I had to
do is reverse engineer that one block and use the style index
that the track-reading block extracted but did not use.

I put style info in the "desc" field of the track since there
doesn't seem to be any direct provision for track styles and
the Topo parser doesn't use the desc field for anything else.
It's visible in GPX output but would need to be put into a
private extension to be read by tools like MapSource that do
allow track colors or destinations like Google Maps that allow
both colors and widths.

Can anyone point me to a central definition for tracks, or
does each format have it's own?

There doesn't seem to be much recent activity on the Topo format,
and this is the first C programming I've done for many years, so
what's the procedure for getting it checked out / verified and
into the distribution?

Steve



------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

code/protocol for BG728 ("navibe mercury") logger

Thorben Thuermer — 2012-03-08T03:24:34

Hello,

i've been using this device, reverse-engineered it's protocol,
and wrote some code to interface with it (none could be found on the web),

...which i think i should share, an this seems to be the best place for that.

the BG728 ("navibe mercury") is a gps-based bicycle computer and gps logger.
(it omits the wheel-rotation sensor usually used by bicycle computers,
and relies solely on gps as it's data-source, even for the speed-display)
it also includes some basic navigation features.
(i did not write code to program POIs/routes, but it could be done.)
as an extra, it contains a temperature sensor (temp data is not logged),
and maybe a digital compass - i didn't yet open the device to verify this.

the manufacturer appers to be http://www.cpss.com.tw/product/?d=37
a good reference page is http://home.icon.co.za/~supercyc/mercury.htm
and it's f.ex. sold by conrad: http://www.conrad.de/ce/de/product/372728
ofcourse the windows software is horrible and partially broken.
(for the map display it embeds IE, displaying google maps - but the map
tiles do not load, i guess they are somewhat violating the google TOS.)

the logger stores 6000 trackpoints at a minimum intervall of 5 seconds.
a horrible flaw in the device is that it keeps logging the last known
point when it loses it's gps-fix, you will want to just discard duplicate
points.

it contains a prolific PL2303 usb-serial bridge, and luckily the protocol
is easily reverse-engineered by listening on the windows program's
communication with the device.
generally, the serial (not usb!) communication seems flaky,
transfered data is regularly corrupted, and crc-checking and
retries are needed to get usable results.

attached you find my documentation of the protocol as a gnumeric spreadsheet.
(if you're desperate, it's a gzip compressed xml file, somewhat readable)

and my code to download logs. it's not perfecly clean, but works and i've
been using it for months...
(i think it sometimes skips log points when reading fails)
(the code uses some files from gpsbabel, but is not integrated with gpsbabel,
it merily writes out the raw data from the device, which can easily be
parsed as csv.
i am not actually using gpsbabel to process the logs, but any of you can
esily write an (x)csv configuration to read the files.)

if you have any questions/comments, consider contacting me directly,
as i'll probably not stay subscribed to this list.

Greetings,
T. Thuermer
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Contributing translation

Erik Krause — 2012-02-11T22:45:08

Hello,

I enhanced the German translation for gpsbabelfe_de (gpsbabel_de is 
already perfect). I went through the process described on 
http://www.gpsbabel.org/tips/translate.html
Unfortunately I didn't find a hint how to provide the translated files...

gb_color

tsteven4 — 2012-02-07T00:54:38

Shouldn't we make bbggrr a long to guarantee we get at least 32 bits, or 
perhaps int_least32_t?  I don't know of any problems, but I am preparing 
an enhancement and I want to program defensively.


------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

patch - a bunch of documentation spellingcorrections

tsteven4 — 2012-02-05T21:30:01

Index: xmldoc/filters/options/transform-del.xml
===================================================================
--- xmldoc/filters/options/transform-del.xml(revision 4154)
+++ xmldoc/filters/options/transform-del.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para>
-This option, when used in connction with the wpt, rte, or trk options, tells
+This option, when used in connection with the wpt, rte, or trk options, tells
 GPSBabel to delete the source data after conversion.  This is most useful if 
 you are trying to avoid duplicated data in the output.
 </para>
Index: xmldoc/filters/options/discard-sat.xml
===================================================================
--- xmldoc/filters/options/discard-sat.xml(revision 4154)
+++ xmldoc/filters/options/discard-sat.xml(working copy)
< at >< at > -1,4 +1,4 < at >< at >
 <para>
-This option specifies the minimum required number of satelites.
+This option specifies the minimum required number of satellites.
 </para>
 
Index: xmldoc/filters/discard.xml
===================================================================
--- xmldoc/filters/discard.xml(revision 4154)
+++ xmldoc/filters/discard.xml(working copy)
< at >< at > -1,7 +1,7 < at >< at >
 <para>
 This filter is used to "fix" unreliable GPS data by discarding points
 that are believed to be unreliable.  You may specify an 
-HDOP and/or VDOP above a specified limit, a minimum number of satellits
+HDOP and/or VDOP above a specified limit, a minimum number of satellites
 that must have been in view for a fix to be considered, or both.
 </para>
 <para>
< at >< at > -14,7 +14,7 < at >< at >
 </example>
 </para>
 <para>
-You may specify a minimmum number of  satellites.  
+You may specify a minimum number of  satellites.  
 </para>
 <para>
 <example id="example_discard_filter_sats">
Index: xmldoc/filters/reverse.xml
===================================================================
--- xmldoc/filters/reverse.xml(revision 4154)
+++ xmldoc/filters/reverse.xml(working copy)
< at >< at > -8,7 +8,7 < at >< at >
         Timestamps are kept with the original waypoints so the
         resulting track or route will have the interesting
         characteristic that time runs backwards.  This tends to make
-        Magellan Mapsend, in particular, do a wierd thing and place
+        Magellan Mapsend, in particular, do a weird thing and place
         each waypoint on a separate day.
 </para>
          <para> Additionally, if you're using this to reverse a route
Index: xmldoc/chapters/styles.xml
===================================================================
--- xmldoc/chapters/styles.xml(revision 4154)
+++ xmldoc/chapters/styles.xml(working copy)
< at >< at > -37,7 +37,7 < at >< at >
 command each time.  If 'mystyle' is a format 
 that describes a popular program or is likely to be of use to others, you can
 then share <filename>mystyle.style</filename> with other GPSBabel users.
-Send it along with a coherent descripton to the GPSBabel-misc mailing 
+Send it along with a coherent description to the GPSBabel-misc mailing 
 list for consideration to be included in a future version.
 </para>
 </section>
< at >< at > -749,7 +749,7 < at >< at >
 <title>LAT_10EX / LON_10EX</title>
 <para>
    Defines the latitude or longitude in the format used i.e. by TomTom Navigator
-   itinerary files. It is degress multiplied by 10 power X. X have to be replaced with
+   itinerary files. It is degrees multiplied by 10 power X. X have to be replaced with
    a valid decimal value. A factor of 10000 would be generated by LAT_10E5 as shown
    in the examples below.
 </para>
< at >< at > -1230,7 +1230,7 < at >< at >
 <section id="style_def_pathcourse">
 <title>PATH_COURSE</title>
 <para>
-   Course in degerees.  Gpsbabel does not calculate this data by default; 
+   Course in degrees.  Gpsbabel does not calculate this data by default; 
    it is read from the input file if present.  (If not present, it may be
    calculated with the <link linkend="filter_track">track</link> filter.)
 </para>
Index: xmldoc/chapters/use.xml
===================================================================
--- xmldoc/chapters/use.xml(revision 4154)
+++ xmldoc/chapters/use.xml(working copy)
< at >< at > -244,7 +244,7 < at >< at >
 <listitem>
 <para>Common format settings.</para>
 <para>  Any option from any of the formats listed here will be used by
-GPSBabel unless explictly provided on the command line.
+GPSBabel unless explicitly provided on the command line.
 </para>
 </listitem>
 <listitem>
< at >< at > -290,7 +290,7 < at >< at >
       As of this writing, <link linkend="fmt_garmin">Garmin's PVT
         protocol</link>  and 
       <link linkend="fmt_nmea">NMEA</link>  are supported 
-  inputs. KML, NMEA, and the variou XCSV formats are supported on 
+  inputs. KML, NMEA, and the various XCSV formats are supported on 
   output.   Additional formats may be added by interested parties 
   later.
     </para>
< at >< at > -360,7 +360,7 < at >< at >
   <para>
    The complete list of available options to GPSBabel can be obtained by
    running <command>gpsbabel -h</command>.  While there are a number of
-   options, most people will not use most of them, so don't be intimiated.
+   options, most people will not use most of them, so don't be intimidated.
   </para>
 <para><option>-p</option> Read preferences file.   On startup, GPSBabel will look for a file named <filename>gpsbabel.ini</filename> containing preferences you have provided.  This option lets you pick a different files.  See <xref linkend="inifile"/> for more info.</para>
 <para><option>-s</option> Write "smart" names.  This option influences some - but not all - of our writers to try to build "smart" waypoint names.   For example, in modules that know about geocaching, it may replace "GC1234" with the actual name of the geocache.</para>
Index: xmldoc/formats/kml.xml
===================================================================
--- xmldoc/formats/kml.xml(revision 4154)
+++ xmldoc/formats/kml.xml(working copy)
< at >< at > -3,12 +3,12 < at >< at >
 <ulink url="http://earth.google.com">Google Earth</ulink>.  
 </para>
 <para>There are concepts in KML that GPSBabel can't support very well on 
-read becuase they don't map well into other programs.  For example, KML has
+read because they don't map well into other programs.  For example, KML has
 ideas of camera views and names and descriptions can have arbitrarily 
 complicated HTML in them.   KML files may have tiered "Styles" which
 can identify sizing info and URLs of associated icons.   Reading such
 files with GPSBabel - even if your goal it to write it back out as KML - can often
-have suprising results.  Simple files with waypoints and paths (which
+have surprising results.  Simple files with waypoints and paths (which
 GPSBabel represents internally as tracks) work fine.
 </para>
 <para>
< at >< at > -19,7 +19,7 < at >< at >
 In general, GPSBabel's KML writer is relatively strong.  GPSBabel handles simple KML on read fairly well, but if you're dealing with handcrafted KML that uses extensive features that have no analog in other formats like nested folders, ringgeometry, camera angles, and such, don't expect GPSBabel to do well with them on read.
 </para>
 <para>
-  Google Earth 4.0 and later have a feature that can suprise users of this 
+  Google Earth 4.0 and later have a feature that can surprise users of this 
   format.   Earth's "time slider" feature controls what timestamped data
   gets displayed.  If you're using data that has timestampes (e.g. GPX 
   points that contain time or almost any track data) this will be important
Index: xmldoc/formats/ggv_ovl.xml
===================================================================
--- xmldoc/formats/ggv_ovl.xml(revision 4154)
+++ xmldoc/formats/ggv_ovl.xml(working copy)
< at >< at > -8,14 +8,14 < at >< at >
 </para>
 <para>
    During the creation of an overlay file, a circle will be added to each 
-   postion of a waypoint or a route.
+   position of a waypoint or a route.
 </para>
 
 <para>
   Sample layout of the ASCII overlay file
   <programlisting format="linespecific">
     [Symbol &lt;number # &gt;]
-    Typ=&lt;1=picture,2=Text, 3=line, 4=area, 5=retangle, 6=circle, 7=triangle&gt;
+    Typ=&lt;1=picture,2=Text, 3=line, 4=area, 5=rectangle, 6=circle, 7=triangle&gt;
     Group=&lt;1=no group, number &gt; 1=group number&gt;
     Col=&lt;number of the line color&gt;
     Zoom=&lt;1=no zoom, 2=zoom&gt;
Index: xmldoc/formats/options/miniHomer-initbaud.xml
===================================================================
--- xmldoc/formats/options/miniHomer-initbaud.xml(revision 4154)
+++ xmldoc/formats/options/miniHomer-initbaud.xml(working copy)
< at >< at > -8,6 +8,6 < at >< at >
 </para>
 <para>
 Please note that miniHomer by default uses 38400bps and does not autodetect the port speed. If you need autodetect, start as
-<userinput>gpsbabel -i miniHomer,initibaud=0 -f /dev/ttyUSB0 -o gpx -F out.gpx</userinput>
+<userinput>gpsbabel -i miniHomer,initbaud=0 -f /dev/ttyUSB0 -o gpx -F out.gpx</userinput>
 </para>
 
Index: xmldoc/formats/options/garmin-get_posn.xml
===================================================================
--- xmldoc/formats/options/garmin-get_posn.xml(revision 4154)
+++ xmldoc/formats/options/garmin-get_posn.xml(working copy)
< at >< at > -1,4 +1,4 < at >< at >
-<para>This options gets the current longtitude and latitude from the attached GPS device
+<para>This options gets the current longitude and latitude from the attached GPS device
 and returns it as a single waypoint for further processing.  For example,
 to return the current position from a USB Garmin to a KML file:
 </para>
Index: xmldoc/formats/options/magellanx-deficon.xml
===================================================================
--- xmldoc/formats/options/magellanx-deficon.xml(revision 4154)
+++ xmldoc/formats/options/magellanx-deficon.xml(working copy)
< at >< at > -1,3 +1,3 < at >< at >
 <para>
-  The deficon option is used to control the icon output when writing to this format.   It overrides any icon informatino that might be present in the source data.
+  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
 </para>
Index: xmldoc/formats/options/tiger-genurl.xml
===================================================================
--- xmldoc/formats/options/tiger-genurl.xml(revision 4154)
+++ xmldoc/formats/options/tiger-genurl.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para>
-genurl is a convenience option for generating the scaling paramaters
+genurl is a convenience option for generating the scaling parameters
 when accessing the Tiger servers.  It will output the latitude, longitude,
 height, and width parameters in a form suitable for use in the URL to generate
 a map that will hold all the points to be displayed  and is suitably scaled
Index: xmldoc/formats/options/pcx-deficon.xml
===================================================================
--- xmldoc/formats/options/pcx-deficon.xml(revision 4154)
+++ xmldoc/formats/options/pcx-deficon.xml(working copy)
< at >< at > -1,3 +1,3 < at >< at >
 <para>
-  The deficon option is used to control the icon output when writing to this format.   It overrides any icon informatino that might be present in the source data.
+  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
 </para>
Index: xmldoc/formats/options/delbin-hint_at_and.xml
===================================================================
--- xmldoc/formats/options/delbin-hint_at_and.xml(revision 4154)
+++ xmldoc/formats/options/delbin-hint_at_and.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para>
-  When set to true, this places the "HINT:" entry from a geocacching.com 
+  When set to true, this places the "HINT:" entry from a geocaching.com 
    pocket query at the end of the screen (scroll up for quick access) like
    Cache Register and Topo7 do instead of at the top as Topo8 does.
 </para>
Index: xmldoc/formats/options/kml-extrude.xml
===================================================================
--- xmldoc/formats/options/kml-extrude.xml(revision 4154)
+++ xmldoc/formats/options/kml-extrude.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para>
-This option is a boolean flag to specicy whether Google Earth should
+This option is a boolean flag to specify whether Google Earth should
 draw lines from trackpoints to the ground.   It defaults to '0', which
 means no extrusion lines are drawn.   The option of '1' is, of course,
 most useful for points that aren't actually on the ground such as those
Index: xmldoc/formats/options/osm-created_by.xml
===================================================================
--- xmldoc/formats/options/osm-created_by.xml(revision 4154)
+++ xmldoc/formats/options/osm-created_by.xml(working copy)
< at >< at > -1,7 +1,7 < at >< at >
 <para> Use this value as custom created_by value in an OSM file.</para>
 
 <para>
-With this pption, the given string is added as the 'created_by' field in 
+With this option, the given string is added as the 'created_by' field in 
 all the created nodes and ways.
 </para>
 
Index: xmldoc/formats/options/mmo-visible.xml
===================================================================
--- xmldoc/formats/options/mmo-visible.xml(revision 4154)
+++ xmldoc/formats/options/mmo-visible.xml(working copy)
< at >< at > -3,7 +3,7 < at >< at >
    By default GPSBabel creates only 'visible' items.
 </para>
 <para>
-   Sample command to write an mmo file with 'in-vsisible' items:
+   Sample command to write an mmo file with 'invisible' items:
 </para>
 <para>
    <userinput>
Index: xmldoc/formats/options/geo-nuke_placer.xml
===================================================================
--- xmldoc/formats/options/geo-nuke_placer.xml(revision 4154)
+++ xmldoc/formats/options/geo-nuke_placer.xml(working copy)
< at >< at > -1,6 +1,6 < at >< at >
 <para>
 If this option is specified, GPSBabel will not read geocache placer information
-from a .loc file on input.  That is, it will ignore any placeer names in the
+from a .loc file on input.  That is, it will ignore any placer names in the
 input file.
 </para>
 <para>
Index: xmldoc/formats/options/unicsv-filename.xml
===================================================================
--- xmldoc/formats/options/unicsv-filename.xml(revision 4154)
+++ xmldoc/formats/options/unicsv-filename.xml(working copy)
< at >< at > -1,6 +1,6 < at >< at >
 <para>
   When this option is enabled, we write an additional column called 'Filename'.
-  The values of this column are filled with filenames of previos input formats.
+  The values of this column are filled with filenames of previous input formats.
 </para>
 <para>
   This can be very helpful for locating specific waypoints (i.e. using the position filter)
Index: xmldoc/formats/options/igo8-title.xml
===================================================================
--- xmldoc/formats/options/igo8-title.xml(revision 4154)
+++ xmldoc/formats/options/igo8-title.xml(working copy)
< at >< at > -1,3 +1,3 < at >< at >
 <para>
-  Use ths option to set the title of the track.
+  Use this option to set the title of the track.
 </para>
Index: xmldoc/formats/options/tiger-margin.xml
===================================================================
--- xmldoc/formats/options/tiger-margin.xml(revision 4154)
+++ xmldoc/formats/options/tiger-margin.xml(working copy)
< at >< at > -2,6 +2,6 < at >< at >
 The margin may be specified in either decimal degrees or as a 
 percentage.</para>
 <para>
-This option is most useful for ensuring there is adaequate space for
+This option is most useful for ensuring there is adequate space for
 the label around the markers when generating automatically scaled maps.
 </para>
Index: xmldoc/formats/options/delbin-hint_at_end.xml
===================================================================
--- xmldoc/formats/options/delbin-hint_at_end.xml(revision 4154)
+++ xmldoc/formats/options/delbin-hint_at_end.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para>
-  When set to true, this places the "HINT:" entry from a geocacching.com 
+  When set to true, this places the "HINT:" entry from a geocaching.com 
    pocket query at the end of the screen (scroll up for quick access) like
    Cache Register and Topo7 do instead of at the top as Topo8 does.
 </para>
Index: xmldoc/formats/options/pathaway-deficon.xml
===================================================================
--- xmldoc/formats/options/pathaway-deficon.xml(revision 4154)
+++ xmldoc/formats/options/pathaway-deficon.xml(working copy)
< at >< at > -1,3 +1,3 < at >< at >
 <para>
-  The deficon option is used to control the icon output when writing to this format.   It overrides any icon informatino that might be present in the source data.
+  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
 </para>
Index: xmldoc/formats/options/magellan-deficon.xml
===================================================================
--- xmldoc/formats/options/magellan-deficon.xml(revision 4154)
+++ xmldoc/formats/options/magellan-deficon.xml(working copy)
< at >< at > -1,3 +1,3 < at >< at >
 <para>
-  The deficon option is used to control the icon output when writing to this format.   It overrides any icon informatino that might be present in the source data.
+  The deficon option is used to control the icon output when writing to this format.   It overrides any icon information that might be present in the source data.
 </para>
Index: xmldoc/formats/options/delbin-nukewpt.xml
===================================================================
--- xmldoc/formats/options/delbin-nukewpt.xml(revision 4154)
+++ xmldoc/formats/options/delbin-nukewpt.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para>
-  When present on the command line and sending waypoins (either explicitly 
+  When present on the command line and sending waypoints (either explicitly 
   via -w or as the default), this will erase
   all waypoints in the receiver before sending the new ones.
 </para>
Index: xmldoc/formats/gopal.xml
===================================================================
--- xmldoc/formats/gopal.xml(revision 4154)
+++ xmldoc/formats/gopal.xml(working copy)
< at >< at > -31,7 +31,7 < at >< at >
 and is simply discarded while reading. If written, there will be a time_t value from the current (computed) timestamp.
 </para>
 <para>
-Somehwere around Gopal 4.8 or 5.0, Electrobit added three more fields to the end of this format.  They are, in order, date (which eliminates most of the silliness above), an unknonw field, and a bearing.   GPSBabel now reads the date and ignores the other two.  We don't yet write these three fields for compatibility with earlier versions.
+Somewhere around Gopal 4.8 or 5.0, Electrobit added three more fields to the end of this format.  They are, in order, date (which eliminates most of the silliness above), an unknown field, and a bearing.   GPSBabel now reads the date and ignores the other two.  We don't yet write these three fields for compatibility with earlier versions.
 </para>
 <para>
 
Index: xmldoc/formats/igc.xml
===================================================================
--- xmldoc/formats/igc.xml(revision 4154)
+++ xmldoc/formats/igc.xml(working copy)
< at >< at > -119,7 +119,7 < at >< at >
 </para>
 <para><userinput>gpsbabel -i gpx -f baro.gpx -i igc -f my2D.igc -o igc -F my3D.igc</userinput></para>
 <para>
-The same can be acheived by downloading directly from a barograph instrument
+The same can be achieved by downloading directly from a barograph instrument
 supported by GPSBabel.  For example with a Brauniger IQ Comp GPS variometer:
 </para>
 <para><userinput>gpsbabel -i baroiq -f /dev/ttyS0 -i igc -f my2D.igc -o igc,timeadj=auto -F my3D.igc</userinput></para>
Index: xmldoc/formats/pocketfms_fp.xml
===================================================================
--- xmldoc/formats/pocketfms_fp.xml(revision 4154)
+++ xmldoc/formats/pocketfms_fp.xml(working copy)
< at >< at > -2,7 +2,7 < at >< at >
    This format provides support for XML flightplans from <ulink url="http://www.pocketfms.com">PocketFMS</ulink>.  
 </para>
 <para>
-   PocketFMS XML flightplans contain route and waypoint information and much more flight planning info as airspaces, aircraft performance, fuel managment etc. This format cannot be read by PocketFMS. Hence GPSBabel supports only input of route and waypoint information.
+   PocketFMS XML flightplans contain route and waypoint information and much more flight planning info as airspaces, aircraft performance, fuel management etc. This format cannot be read by PocketFMS. Hence GPSBabel supports only input of route and waypoint information.
 </para>
 <para>
     The PocketFMS flightplan converter take into account the -w waypoint flag. If set then additional waypoints are stored to the route point and path information. 
Index: xmldoc/formats/garmin_gpi.xml
===================================================================
--- xmldoc/formats/garmin_gpi.xml(revision 4154)
+++ xmldoc/formats/garmin_gpi.xml(working copy)
< at >< at > -6,7 +6,7 < at >< at >
 </para>
 <para>
    The layout of GPI files isn't documented and our module was created
-   via reverse engeneering. If you get a problem on reading or writing 
+   via reverse engineering. If you get a problem on reading or writing 
    a GPI file, please provide that file (mailto:gpsbabel-misc< at >lists.sourceforge.net).
 </para>
 <para>
Index: xmldoc/formats/v900.xml
===================================================================
--- xmldoc/formats/v900.xml(revision 4154)
+++ xmldoc/formats/v900.xml(working copy)
< at >< at > -1,6 +1,6 < at >< at >
 <para>Read-only support for the csv file format used by <productname>Visiontac VGPS-900</productname> and <productname>Columbus V-900</productname> GPS data loggers. These seem to be two brand names for the exact same product.</para>
 
-<para>The the V-900 stores logs on a microSD card in a custom csv format. This format contains NULL chracters and fixed length fields, and therefore can not  be handled by the normal csv module in GPSBabel.</para>
+<para>The the V-900 stores logs on a microSD card in a custom csv format. This format contains NULL characters and fixed length fields, and therefore can not  be handled by the normal csv module in GPSBabel.</para>
 
 <para>
 <ulink url="http://www.visiontac.com/v900_specs.htm">Visiontac VGPS-900</ulink>
Index: xmldoc/formats/stmsdf.xml
===================================================================
--- xmldoc/formats/stmsdf.xml(revision 4154)
+++ xmldoc/formats/stmsdf.xml(working copy)
< at >< at > -2,7 +2,7 < at >< at >
 This format supports the .sdf files from the Suunto product family
 'Suunto Trek Manager', 'Suunto Ski Manager' and 'Suunto Sail Manager'.
 The contents of the sdf file depends on the used product and can
-be one route or one track. Thatswhy when you want to use sdf on the
+be one route or one track. Thats why when you want to use sdf on the
 output side you have to use the
 <link linkend="Route_And_Track_Modes">-r OR the -t</link> option. This will tell
 GPSBabel which type of data should be written.
Index: xmldoc/formats/openoffice.xml
===================================================================
--- xmldoc/formats/openoffice.xml(revision 4154)
+++ xmldoc/formats/openoffice.xml(working copy)
< at >< at > -1,5 +1,5 < at >< at >
 <para> 
-Tab seperated export-all (except geocaching data) file
+Tab separated export-all (except geocaching data) file
 format.  Intended to serve as source for number-processing
 applications like OpenOffice, Ploticus and others. Tab was chosen as
 delimiter because it is a) supported by both OpenOffice and Ploticus
Index: xmldoc/formats/gpsdrive.xml
===================================================================
--- xmldoc/formats/gpsdrive.xml(revision 4154)
+++ xmldoc/formats/gpsdrive.xml(working copy)
< at >< at > -1,7 +1,7 < at >< at >
 
       
       
-      <para>GpsDrive way.txt file format. A space seperated format
+      <para>GpsDrive way.txt file format. A space separated format
 file. Tested against GpsDrive v 1.30 found at <ulink url="http://www.gpsdrive.de">gpsdrive.de</ulink>.
 Contributed by Alan Curry.</para>
     
Index: xmldoc/formats/miniHomer.xml
===================================================================
--- xmldoc/formats/miniHomer.xml(revision 4154)
+++ xmldoc/formats/miniHomer.xml(working copy)
< at >< at > -45,7 +45,7 < at >< at >
 </example>
 
 <para>miniHomer has five POI called Home, <emphasis>Car</emphasis>, <emphasis>Boat</emphasis>, <emphasis>Heart</emphasis>, <emphasis>Bar</emphasis>. You can set the lla 
-(Lattitude, Longitude, Altitude) for each of the POI. The format is 
+(Latitude, Longitude, Altitude) for each of the POI. The format is 
 <emphasis>&lt;name&gt;=&lt;lat&gt;:&lt;lng&gt;[:&lt;alt&gt;]</emphasis>
 Once the according POI symbol is selected on miniHomer, the display shows you the direction and distance to the POI.
 </para>
Index: xmldoc/formats/pcx.xml
===================================================================
--- xmldoc/formats/pcx.xml(revision 4154)
+++ xmldoc/formats/pcx.xml(working copy)
< at >< at > -1,6 +1,6 < at >< at >
       <para> Garmin documents only PCX5, an older format limited to
 the lame NMEA six-character waypoint names that's treated as a
-second-class citizien in current versions of MapSource.  In Mapsource,
+second-class citizen in current versions of MapSource.  In Mapsource,
 use file-&gt;import to read these files.  If you name the files *.wpt,
 Mapsource will find them more easily.
 </para>
Index: xmldoc/formats/unicsv.xml
===================================================================
--- xmldoc/formats/unicsv.xml(revision 4154)
+++ xmldoc/formats/unicsv.xml(working copy)
< at >< at > -32,7 +32,7 < at >< at >
       exported = Geocache export date 
       found =    <link linkend="style_def_geofound">Geocache last found date</link>
       fix =      3d, 2d, etc.
-      gcid =     Geocache chache id
+      gcid =     Geocache cache id
       geschw =   Geschwindigkeit (speed)
       hdop =     Horizontal dilution of precision
       head =     Heading / Course true
Index: xmldoc/formats/bushnell.xml
===================================================================
--- xmldoc/formats/bushnell.xml(revision 4154)
+++ xmldoc/formats/bushnell.xml(working copy)
< at >< at > -20,7 +20,7 < at >< at >
   gpsbabel -i gpx -f whatever.gpx -o bushnell -F /Volumes/Bushnell/WAYPOINT/whatever
 </userinput>
 will result in "whatever-0.wpt", "whatever-1.wpt", and "whatever-2.wpt" being
-credated in that directory.
+created in that directory.
 Windows users may prefer the spelling:
 <userinput>
   gpsbabel -i gpx -f whatever.gpx -o bushnell -F e:/WAYPOINT/whatever
Index: xmldoc/formats/destinator_trl.xml
===================================================================
--- xmldoc/formats/destinator_trl.xml(revision 4154)
+++ xmldoc/formats/destinator_trl.xml(working copy)
< at >< at > -4,7 +4,7 < at >< at >
 <para>
   The basic information was found at <ulink url="http://mozoft.com/d3log.html">mozoft.com</ulink>.
   In addition to the standard GPS track data of coordinates and timestamp, this format also stores the 
-  position fix and the number of satelites seen during recording. 
+  position fix and the number of satellites seen during recording. 
 </para>
 <para>
   <productname>Destinator</productname> by
Index: xmldoc/formats/skyforce.xml
===================================================================
--- xmldoc/formats/skyforce.xml(revision 4154)
+++ xmldoc/formats/skyforce.xml(working copy)
< at >< at > -5,7 +5,7 < at >< at >
 </para>
 <para>
    Each kind of our basic GPS data (waypoints, routes, and tracks) is 
-   stored in a seperate file. Therefore you need three steps to 
+   stored in a separate file. Therefore you need three steps to 
    convert a complex format like GPX or GDB into skyforce.
    <userinput>
       gpsbabel -i gpx -f file.gpx -o skyforce -w -F waypoints.txt -r -F routes.txt -t -F tracks.txt
Index: xmldoc/formats/ik3d.xml
===================================================================
--- xmldoc/formats/ik3d.xml(revision 4154)
+++ xmldoc/formats/ik3d.xml(working copy)
< at >< at > -3,7 +3,7 < at >< at >
 </para>
 <para>
   <ulink url="http://www.magicmaps.de">MagicMaps</ulink> <productname>"Das interaktive Kartenwerk"</productname> is a Software from Germany. It's a
-  route-planning software with a 3-dimensional envirounment.
+  route-planning software with a 3-dimensional environment.
 </para>
 <para>
   The project files are XML based and we can read the main GPS items (names and coordinates). 
Index: xmldoc/formats/holux.xml
===================================================================
--- xmldoc/formats/holux.xml(revision 4154)
+++ xmldoc/formats/holux.xml(working copy)
< at >< at > -5,7 +5,7 < at >< at >
 compact flash cards.  File formats were provided by Holux-Taiwan
 <ulink url="http://www.holux.com.tw">holux.com</ulink> to the author.
 The code was tested against version 2.27E1; other versions and
-receivers may work but have not been explictly tested.  Anyone with
+receivers may work but have not been explicitly tested.  Anyone with
 information on other Holux receivers is encouraged to contact
 jochen< at >bauerbahn.net.
 </para>
< at >< at > -16,7 +16,7 < at >< at >
       <para> Comparing the waypoints of a .wpo files against other
 formats like .gpx you may notice a small difference in the latitude
 and longitude values.  The reason is the low resolution of the
-coordinates in the wpo file format.  In a .wpo file the reolution is
+coordinates in the wpo file format.  In a .wpo file the resolution is
 1/10"; in gpx for example it is 1/100".  A a practical matter, this
 loss is only about 1.7 meters (5 feet).
 </para>
Index: xmldoc/formats/garmin.xml
===================================================================
--- xmldoc/formats/garmin.xml(revision 4154)
+++ xmldoc/formats/garmin.xml(working copy)
< at >< at > -266,7 +266,7 < at >< at >
 a unit number, with zero being the implied default.  So if you 
 have three USB models on your system, they can be addressed as 
 <filename>usb:0</filename>, <filename>usb:1</filename>, and <filename>usb:2</filename>.  To get a list of recognized devices,
-specifiy a negative number such as:
+specify a negative number such as:
 </para>
 <para><userinput>gpsbabel -i garmin -f usb:-1</userinput></para>
  
Index: xmldoc/formats/psitrex.xml
===================================================================
--- xmldoc/formats/psitrex.xml(revision 4154)
+++ xmldoc/formats/psitrex.xml(working copy)
< at >< at > -4,7 +4,7 < at >< at >
       <para>This is a text format created by KuDaTa's PsiTrex program
 for the Psion PDAs. The format can't be readily handled by XCSV, so
 this format is handled explicitly. Waypoints, routes and tracks are
-all handled, with icon names used corresponding to verison 1.13 of
+all handled, with icon names used corresponding to version 1.13 of
 PsiTrex. This module was contributed to GPSBabel by Mark
 Bradley.</para>
     
Index: xmldoc/formats/gpsdrivetrack.xml
===================================================================
--- xmldoc/formats/gpsdrivetrack.xml(revision 4154)
+++ xmldoc/formats/gpsdrivetrack.xml(working copy)
< at >< at > -2,6 +2,6 < at >< at >
       
       
       <para>Format used by GpsDrive to save tracks. Like GPSDRIVE a
-space seperated format file. See above for a link to GpsDrive.
+space separated format file. See above for a link to GpsDrive.
 Contributed by Tobias Minich.</para>
     
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

more svn mode fixes

tsteven4 — 2012-02-03T02:25:17

I recommend deleting svn:executable on the following files.  This can be 
done by running the attached script "reset_exec".  The log from my run 
is "reset_exec.txt".  I was able to build and test code afterwards, 
although that certainly doesn't attempt to execute everything that 
should be executable.

My strategy was
i) no executable files should be in the reference directory,
ii) no .ico, .png, .cpp, .xml files should be executable.



#!/bin/bash
find reference -type f -executable -exec svn propdel svn:executable {} \;
find . -name "*.ico" -executable -exec svn propdel svn:executable {} \;
find . -name "*.png" -executable -exec svn propdel svn:executable {} \;
find . -name "*.cpp" -executable -exec svn propdel svn:executable {} \;
find . -name "*.xml" -executable -exec svn propdel svn:executable {} \;
property 'svn:executable' deleted from 'reference/expertgps.gpx'.
property 'svn:executable' deleted from 'reference/mapsource.mps'.
property 'svn:executable' deleted from 'reference/mps-empty.mps'.
property 'svn:executable' deleted from 'reference/pocketfms_fp.gpx'.
property 'svn:executable' deleted from 'reference/pocketfms_bc'.
property 'svn:executable' deleted from 'reference/track/wintec_tes.tes'.
property 'svn:executable' deleted from 'reference/track/height_out.gpx'.
property 'svn:executable' deleted from 'reference/track/height.gpx'.
property 'svn:executable' deleted from 'reference/track/i65.anr'.
property 'svn:executable' deleted from 'reference/route/naviguide-route.twl'.
property 'svn:executable' deleted from 'reference/route/route.mps'.
property 'svn:executable' deleted from 'reference/coastexp.nob'.
property 'svn:executable' deleted from 'reference/enigma.gpx'.
property 'svn:executable' deleted from 'reference/memory-map.mmo'.
property 'svn:executable' deleted from 'reference/easygps.loc'.
property 'svn:executable' deleted from 'reference/enigma-gpsb.ert'.
property 'svn:executable' deleted from 'reference/foo.an1'.
property 'svn:executable' deleted from 'reference/navilink_waypoints.wpt'.
property 'svn:executable' deleted from 'reference/coastexp.ref'.
property 'svn:executable' deleted from 'reference/pocketfms_bc.babel'.
property 'svn:executable' deleted from 'reference/bushnell.wpt'.
property 'svn:executable' deleted from 'reference/pocketfms_wp.gpx'.
property 'svn:executable' deleted from 'reference/pocketfms_bc.gpx'.
property 'svn:executable' deleted from 'reference/navilink_tracks.trk'.
property 'svn:executable' deleted from 'reference/navilink_tracks_gpx.trk'.
property 'svn:executable' deleted from 'reference/dusky.trk'.
property 'svn:executable' deleted from 'reference/enigma-pfms.ert'.
property 'svn:executable' deleted from 'gui/images/babel2.ico'.
property 'svn:executable' deleted from 'gui/images/appicon.ico'.
property 'svn:executable' deleted from 'gui/images/babel3.ico'.
property 'svn:executable' deleted from 'gui/images/exit.png'.
property 'svn:executable' deleted from 'gui/images/runit.png'.
property 'svn:executable' deleted from 'gui/gmapdlg.cpp'.
property 'svn:executable' deleted from 'gui/map.cpp'.
property 'svn:executable' deleted from 'gui/dpencode.cpp'.
property 'svn:executable' deleted from 'gui/gpx.cpp'.
property 'svn:executable' deleted from 'xmldoc/formats/pocketfms_wp.xml'.
property 'svn:executable' deleted from 'xmldoc/formats/enigma_wp.xml'.
property 'svn:executable' deleted from 'xmldoc/formats/pocketfms_fp.xml'.
property 'svn:executable' deleted from 'xmldoc/formats/pocketfms_bc.xml'.
property 'svn:executable' deleted from 'xmldoc/formats/enigma.xml'.
property 'svn:executable' deleted from 'xmldoc/formats/options/height-add.xml'.
property 'svn:executable' deleted from 'xmldoc/formats/options/height-wgs84tomsl.xml'.
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

.FIT conversion for Edge800 No Go

Stefan Skopnik — 2012-02-01T09:19:44

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d_______________________________________________
Gpsbabel-code mailing list  http://www.gpsbabel.org
Gpsbabel-code< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code