Nabble - GPSBabel - Dev

Patch: Heartrate/cadence write support for GPX

2009-12-11T14:13:51Z

Hi,

the attached patch adds support for writing heartrate and cadence
information to GPX files using the Garmin trackpoint extensions (i.e.
compatible to the heartrate/cadence reading support that's already in
gpx.c). It's enabled only if the "garminextensions" option has been
specified.

I know that there have been discussions about whether heartrate and cadence
is something that should be stored in GPX files, but IIRC, one of the last
statements from Robert was that he wouldn't be opposed to it if somebody
would implement it. So here we go... Would be great to see this in official
gpsbabel release so that I don't have to maintain my own branch.

Questions? Comments?

Martin

--- gpsbabel-cvs-20091119/gpx.c.orig 2009-12-08 17:24:18.000000000 +0100 +++ gpsbabel-cvs-20091119/gpx.c 2009-12-09 19:18:07.000000000 +0100 @@ -1608,29 +1608,38 @@ } static void -gpx_write_common_depth(const waypoint *waypointp, const char *indent) +gpx_write_common_extensions(const waypoint *waypointp, const char *indent) { - if (waypointp->depth != 0 || waypointp->temperature != 0) { - if (opt_humminbirdext || opt_garminext) { - gbfprintf(ofd, "%s<extensions>\n", indent); - if (waypointp->depth != 0) { - if (opt_humminbirdext) - gbfprintf(ofd, "%s <h:depth>%f</h:depth>\n", - indent, waypointp->depth*100.0); - if (opt_garminext) - gbfprintf(ofd, "%s <gpxx:Depth>%f</gpxx:Depth>\n", - indent, waypointp->depth); - } - if (waypointp->temperature != 0) { - if (opt_humminbirdext) - gbfprintf(ofd, "%s <h:temperature>%f</h:temperature>\n", - indent, waypointp->temperature); - if (opt_garminext) - gbfprintf(ofd, "%s <gpxx:Temperature>%f</gpxx:Temperature>\n", - indent, waypointp->temperature); - } - gbfprintf(ofd, "%s</extensions>\n", indent); + if (((opt_humminbirdext || opt_garminext) && (waypointp->depth != 0 || waypointp->temperature != 0)) + || (opt_garminext && (waypointp->heartrate != 0 || waypointp->cadence != 0))) { + gbfprintf(ofd, "%s<extensions>\n", indent); + if (waypointp->depth != 0) { + if (opt_humminbirdext) + gbfprintf(ofd, "%s <h:depth>%f</h:depth>\n", + indent, waypointp->depth*100.0); + if (opt_garminext) + gbfprintf(ofd, "%s <gpxx:Depth>%f</gpxx:Depth>\n", + indent, waypointp->depth); } + if (waypointp->temperature != 0) { + if (opt_humminbirdext) + gbfprintf(ofd, "%s <h:temperature>%f</h:temperature>\n", + indent, waypointp->temperature); + if (opt_garminext) + gbfprintf(ofd, "%s <gpxx:Temperature>%f</gpxx:Temperature>\n", + indent, waypointp->temperature); + } + if (opt_garminext && (waypointp->heartrate != 0 || waypointp->cadence != 0)) { + gbfprintf(ofd, "%s <gpxtpx:TrackPointExtension>\n", indent); + if (waypointp->heartrate != 0) + gbfprintf(ofd, "%s <gpxtpx:hr>%u</gpxtpx:hr>\n", + indent, waypointp->heartrate); + if (waypointp->cadence != 0) + gbfprintf(ofd, "%s <gpxtpx:cad%u</gpxtpx:cad>\n", + indent, waypointp->cadence); + gbfprintf(ofd, "%s </gpxtpx:TrackPointExtension>\n", indent); + } + gbfprintf(ofd, "%s</extensions>\n", indent); } } @@ -1688,7 +1697,7 @@ /* MapSource doesn't accepts extensions from 1.0 */ garmin_fs_xml_fprint(ofd, waypointp); } - gpx_write_common_depth(waypointp, " "); + gpx_write_common_extensions(waypointp, " "); gbfprintf(ofd, "</wpt>\n"); } @@ -1750,7 +1759,7 @@ fprint_xml_chain( fs_gpx->tag, waypointp ); } - gpx_write_common_depth(waypointp, " "); + gpx_write_common_extensions(waypointp, " "); gbfprintf(ofd, "</trkpt>\n"); } @@ -1805,7 +1814,7 @@ fprint_xml_chain( fs_gpx->tag, waypointp ); } - gpx_write_common_depth(waypointp, " "); + gpx_write_common_extensions(waypointp, " "); gbfprintf(ofd, " </rtept>\n"); } @@ -1878,7 +1887,8 @@ if (opt_humminbirdext) gbfprintf(ofd, " xmlns:h=\"http://humminbird.com\"\n"); if (opt_garminext) - gbfprintf(ofd, " xmlns:gpxx=\"http://www.garmin.com/xmlschemas/GpxExtensions/v3\""); + gbfprintf(ofd, " xmlns:gpxx=\"http://www.garmin.com/xmlschemas/GpxExtensions/v3\"\n" + " xmlns:gpxtpx=\"http://www.garmin.com/xmlschemas/TrackPointExtension/v1\"\n"); gbfprintf(ofd, " xmlns=\"http://www.topografix.com/GPX/%c/%c\"\n", gpx_wversion[0], gpx_wversion[2]); if (xsi_schema_loc) {

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev

_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

issue when trying to convert mtk binary log to another format

2009-12-08T14:25:44Z

Hi!
I didn't found if this issue has been reported
it was working fine with an older version of gpsbabel
I have a qstarz Q1000p data logger, I use it to record every 5m
(tipical use is hicking)
the command used is :
gpsbabel -D 2 -t -w -i mtk -f /dev/ttyUSB0 -o gpx -F out.gpx

the bin is downloading fine, the file contain data
however the created gpx is an empty one, only the headers are
provided, I tried to re-do the conversion using mtk-bin for -i but the
result is the same.
I tried to create the gpx using bt747 and here all is ok, I get a
valid gpx file....
it was working some time ago, I don't remember the version of gpsbabel
I was using then
thanks and regards
JLM

--
KISS! (Keep It Simple, Stupid!)
(garde le simple, imbécile!)
"mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses
simples et qui marchent, espèce d'imbécile!"
-----------------------------
"Si vous pensez que vous êtes trop petit pour changer quoique ce soit,
essayez donc de dormir avec un moustique dans votre chambre." Betty
Reese
http://www.grainesdechangement.com/citations.htm

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: patch to increase precision in unicsv.c

2009-12-02T15:14:34Z

Robert wrote:
> Under what circumstances does this patch actually improve
> precision?

after a trip into the field last week I was downloading &
converting the data and losing info in the process. Specifically
river depths from the sounder are better than 10cm while
shallow, and temperature is given better than 0.1 deg C.
This was from a consumer grade Garmin depth sounder.

HDOP et al were just along for the ride, the idea being that
units using meters should report to the mm (to accomodate
survey grade/RTK GPSs). For lat/lon that means about %.9f btw.

> Do you really have a device that returns temperature to a
> thousandth of a degree

actually I do, but that's a bit besides the point & I'm not
really asking you to support research gear (but for the cost
of 1 sigf dig that would sure be nice).

good thermistors are pretty cheap these days, something that
gets you to better than 0.1 deg C is less than $0.50 so lots
of things have that. The idea of going to 0.001 deg instead
of 0.01 deg was to avoid introducing any FP rounding errors.
(mostly an issue for lat/lon which needs to be stored in a
double, but after tearing my hair out so many times due to
that (after the source data was gone) I try to preserve
precision+1 for everything now and let gzip worry about any
added zeros)

> or that returns DOP with meaningful values in the hundredths
> position?

DOP was just to standardize at 1mm reporting. No arguement that
that will be slight overkill. I'll have a peek at some of our
Trible logs and see if I get any really tiny DOP numbers out of
that (should be good to about 2mm position in the horizontal).
I've got a feeling that the DOP there is in pseudo-meters though,
Gpsd has some code to convert, I'm not really sure how correct
their approach is though.

> If there is actually valid information, I
> don't mind bloating the output,

sure, I see your point.

for bit balance, the GPX output doesn't need to go to %.6f for
those things.

> but it's not like speed (which is almost always computed and
> not measured)

are you sure about that? I seem to recall something recently
discussing how the speed solution was often better than fix as
it took phase differences into account.

> from consumer grade GPS has two significant digits past the
> decimal.

thanks,
Hamish

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: patch to increase precision in unicsv.c

2009-11-30T06:25:16Z

Under what circumstances does this patch actually improve precision? Do you really have a device that returns temperature to a thousandth of a degree or that returns DOP with meaningful values in the hundredths position? If there is actually valid information, I don't mind bloating the output, but it's not like speed (which is almost always computed and not measured) from consumer grade GPS has two significant digits past the decimal.

RJL

On Wed, Nov 25, 2009 at 8:19 PM, Hamish <hamish_b@...> wrote:

Hi,

the attached patch increases output precision for fields like depth and
temperature with the unicsv output format. To-the-mm is perhaps erring on
the side of overkill, but to-the-decimeter was losing valid information.
No point in throwing away good data...

thanks,
Hamish

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-30T06:13:16Z

Yes, thanx Rogier.   This is what I committed.

Index: garmin.c
===================================================================
RCS file: /cvsroot/gpsbabel/gpsbabel/garmin.c,v
retrieving revision 1.133
diff -p -u -r1.133 garmin.c
--- garmin.c    23 Jun 2009 03:14:21 -0000    1.133
+++ garmin.c    30 Nov 2009 14:12:07 -0000
@@ -638,16 +638,13 @@ pvt2wpt(GPS_PPvt_Data pvt, waypoint *wpt
         wpt->longitude = pvt->lon;
     WAYPT_SET(wpt,course,1);
     WAYPT_SET(wpt,speed,1);
-    /* convert to true course in degrees */
-    if ( pvt->east >= 0.0 )
-        wpt->course = 90 - DEG(atan(pvt->north/pvt->east));
-    else
-        wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
-#if 0
+
+    wpt->course = 180 + DEG(atan2(-pvt->east, -pvt->north));
+
     /* velocity in m/s */
-    wpt->speed = sqrt(pvt->north*pvt->north + pvt->east*pvt->east);
-    wpt->vs = pvt->up;
-#endif
+    WAYPT_SET(wpt,speed, sqrt(pvt->north*pvt->north + pvt->east*pvt->east));
+    // wpt->vs = pvt->up;
+
     /*
     * The unit reports time in three fields:
     * 1) The # of days to most recent Sun. since 1989-12-31 midnight UTC.

On Sat, Nov 28, 2009 at 1:34 PM, Jeff McFadden <jeff.mcfadden@...> wrote:

Roger,

Thanks for explaining how that all works. A very elegant solution and now I understand a lot more about how all these trig functions are working.

thanks!

-- Jeff

On Thu, Nov 26, 2009 at 2:11 AM, Rogier Wolff <R.E.Wolff@...> wrote:

On Thu, Nov 26, 2009 at 09:55:48AM +0100, Rogier Wolff wrote:
> wpt->course = 180 DEG(atan2(-pvt->east, -pvt->north));

Typo:

wpt->course = 180 + DEG(atan2(-pvt->east, -pvt->north));

Roger.
--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-28T11:34:00Z

Roger,

Thanks for explaining how that all works. A very elegant solution and now I understand a lot more about how all these trig functions are working.

thanks!

-- Jeff

On Thu, Nov 26, 2009 at 2:11 AM, Rogier Wolff <R.E.Wolff@...> wrote:

On Thu, Nov 26, 2009 at 09:55:48AM +0100, Rogier Wolff wrote:
> wpt->course = 180 DEG(atan2(-pvt->east, -pvt->north));

Typo:

wpt->course = 180 + DEG(atan2(-pvt->east, -pvt->north));

Roger.
--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

Re: Question on real time tracking

2009-11-26T01:11:07Z

On Thu, Nov 26, 2009 at 09:55:48AM +0100, Rogier Wolff wrote:
> wpt->course = 180 DEG(atan2(-pvt->east, -pvt->north));

Typo:

wpt->course = 180 + DEG(atan2(-pvt->east, -pvt->north));

Roger.
--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-26T00:55:48Z

On Wed, Nov 25, 2009 at 11:58:17AM -0700, Jeff McFadden wrote:
> Sorry for the delay (left town for Thanksgiving vacation). Here's a patch
> for the changes.
> + if(pvt->east == 0.0){
> + wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please
> + }else if(pvt->east > 0.0){
> + wpt->course = 90 - DEG(atan2(pvt->north/pvt->east));
> + }else{
> + wpt->course = 270 - DEG(atan2(pvt->north/pvt->east));
> + }

I think it should be something like:

wpt->course = DEG(atan2(pvt->east, pvt->north));

Your patch should at least give a warning, because atan2 needs a
second argument.

Notice that I've rotated the result by 90 degree by swapping east and
north and then putting a minus in front of "north". Mathematicians start
counting at east, and count counter clockwise. Course is clockwise, so
should go the other way. So to achieve that, we should flip the whole
thing. This is done by adding another minus sign.

Now there is one more problem: The result of atan2 is between -PI and
+PI, so we also get negative courses. We could add:

if (wpt->course < 0) wpt->course += 360;

but we can ddo this more elegantly. If we rotate the result by 180
degrees and add 180 degrees the result will be between 0 and 360...

wpt->course = 180 DEG(atan2(-pvt->east, -pvt->north));

Roger.

--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

patch to increase precision in unicsv.c

2009-11-25T18:19:33Z

Hi,

the attached patch increases output precision for fields like depth and
temperature with the unicsv output format. To-the-mm is perhaps erring on
the side of overkill, but to-the-decimeter was losing valid information.
No point in throwing away good data...

thanks,
Hamish

[unicsv_precisions.diff]

Index: unicsv.c =================================================================== RCS file: /cvsroot/gpsbabel/gpsbabel/unicsv.c,v retrieving revision 1.47 diff -u -r1.47 unicsv.c --- unicsv.c 20 Sep 2008 20:13:53 -0000 1.47 +++ unicsv.c 26 Nov 2009 01:55:33 -0000 @@ -1372,7 +1372,7 @@ unicsv_print_str((wpt->icon_descr != NULL) ? wpt->icon_descr : "Waypoint"); if FIELD_USED(fld_depth) { if WAYPT_HAS(wpt, depth) - gbfprintf(fout, "%s%.1f", unicsv_fieldsep, wpt->depth); + gbfprintf(fout, "%s%.3f", unicsv_fieldsep, wpt->depth); else gbfputs(unicsv_fieldsep, fout); } @@ -1384,13 +1384,13 @@ } if FIELD_USED(fld_temperature) { if WAYPT_HAS(wpt, temperature) - gbfprintf(fout, "%s%.1f", unicsv_fieldsep, wpt->temperature); + gbfprintf(fout, "%s%.3f", unicsv_fieldsep, wpt->temperature); else gbfputs(unicsv_fieldsep, fout); } if FIELD_USED(fld_speed) { if WAYPT_HAS(wpt, speed) - gbfprintf(fout, "%s%.1f", unicsv_fieldsep, wpt->speed); + gbfprintf(fout, "%s%.2f", unicsv_fieldsep, wpt->speed); else gbfputs(unicsv_fieldsep, fout); } @@ -1415,19 +1415,19 @@ } if FIELD_USED(fld_hdop) { if (wpt->hdop > 0) - gbfprintf(fout, "%s%.1f", unicsv_fieldsep, wpt->hdop); + gbfprintf(fout, "%s%.2f", unicsv_fieldsep, wpt->hdop); else gbfputs(unicsv_fieldsep, fout); } if FIELD_USED(fld_vdop) { if (wpt->vdop > 0) - gbfprintf(fout, "%s%.1f", unicsv_fieldsep, wpt->vdop); + gbfprintf(fout, "%s%.2f", unicsv_fieldsep, wpt->vdop); else gbfputs(unicsv_fieldsep, fout); } if FIELD_USED(fld_pdop) { if (wpt->pdop > 0) - gbfprintf(fout, "%s%.1f", unicsv_fieldsep, wpt->pdop); + gbfprintf(fout, "%s%.2f", unicsv_fieldsep, wpt->pdop); else gbfputs(unicsv_fieldsep, fout); }

Re: Question on real time tracking

2009-11-25T10:58:17Z

Sorry for the delay (left town for Thanksgiving vacation). Here's a patch for the changes.

-- Jeff

Index: garmin.c

===================================================================

RCS file: /cvsroot/gpsbabel/gpsbabel/garmin.c,v

retrieving revision 1.133

diff -u -r1.133 garmin.c

--- garmin.c 23 Jun 2009 03:14:21 -0000 1.133

+++ garmin.c 25 Nov 2009 18:56:49 -0000

@@ -633,21 +633,25 @@

{

double wptime, wptimes;

- wpt->altitude = pvt->alt;

- wpt->latitude = pvt->lat;

- wpt->longitude = pvt->lon;

+ wpt->altitude = pvt->alt;

+ wpt->latitude = pvt->lat;

+ wpt->longitude = pvt->lon;

WAYPT_SET(wpt,course,1);

- WAYPT_SET(wpt,speed,1);

/* convert to true course in degrees */

- if ( pvt->east >= 0.0 )

- wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

- else

- wpt->course = 270 - DEG(atan(pvt->north/pvt->east));

-#if 0

+ if(pvt->east == 0.0){

+ wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please

+ }else if(pvt->east > 0.0){

+ wpt->course = 90 - DEG(atan2(pvt->north/pvt->east));

+ }else{

+ wpt->course = 270 - DEG(atan2(pvt->north/pvt->east));

+ }

/* velocity in m/s */

- wpt->speed = sqrt(pvt->north*pvt->north + pvt->east*pvt->east);

- wpt->vs = pvt->up;

-#endif

+ WAYPT_SET(wpt,speed,sqrt(pvt->north*pvt->north + pvt->east*pvt->east));

+ //wpt->vs = pvt->up;

* The unit reports time in three fields:

* 1) The # of days to most recent Sun. since 1989-12-31 midnight UTC.

On Thu, Nov 19, 2009 at 9:31 AM, Rogier Wolff <R.E.Wolff@...> wrote:

On Thu, Nov 19, 2009 at 10:08:54AM -0600, Robert Lipe wrote:
> Good call, guys. atan2 is in C89, so it should be available everywhere we
> care.
>
> Roger, I was indeed trying to defend against the case of floating point
> jitter near, but not quite equal to zero. The values in question do come
> from 32-bit floats from the device (not ascii) and there's nothing that
> actually stops the device from reporting amounts of or arbitrarily close to
> zero; it's not "just" NMEA/ASCII that we're reading. But I'm quite happy
> making this atan2's problem.

atan (x) is only just a little more than "x" when x is small.

This is what implementations use to implement atan. Many atan2 (and
atan) functions will start with something like:

double atan2 (double y, double x)
{
if (abs (y) < abs(x)) return (PI/4 - atan2 (x, y));

return x + epsilon (x/y);

}

> Jeff, since you're in this section of code, want to drop it in and us send a
> patch?

Good patches reduce the size of the code. (which is possible in this
case!)

Roger.

--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

Re: Write support for binary lmx

2009-11-23T10:01:05Z

2009/11/23 Christian Bühler <christian@...>

I also thought about creating a seperate format, but the structure of
the binary and XML format are very similar to each other, so this would
have meant quite a lot of duplicate code.

The way we've handled this in the past has been to expose two separate entries in vecs.c (thus allowing two different menu options in the GUI) and then have the foo_init set or clear the equivalent of your 'binary' variable. You can see an extreme case of this in magproto.c where the "same" protocol is both a serial and two annoyingly different file-based ones.

If we were convinced anybody used binary LMX, I'd be more inclined to tackle this. :-) Let's just go with it for now.

Also the original specification sais, that implementations should
support both formats. So I think, it makes sense to keep both
implementations close to each other.

(This also means, that even Nokia does not comply strictly to their own
specification :-)

Yes, this project has made it very clear that even when vendors do publish specs for such things, they're frequently not followed even internally within the company.

Later,
RJL

Am Montag, den 23.11.2009, 00:37 -0600 schrieb Robert Lipe:

> Thanx. This seems pretty sane to me. My first inclination is to make
> binary LMX a different format but if they're not supporting it on
> their current devices and this is just a historic thing, it might not
> be so bad.
>
> I've applied this.
>
> 2009/11/6 Christian Bühler <christian@...>
> Hi,
> I sat down a while and implemented write support for the
> binary lmx
> format.
>
> I also implicitly fixed some mistakes in the lmx xml format:
> - XML files support UTF-8, so no need to convert special
> characters
> - Shortnames are now handled just like in gpx
> - There was a missing space in the xsi:schemaLocation
> - indentation is now with tabs just like it is generated by my
> Nokia N82
> - added a test to testo for the binary format
> - I also added a bit to the lmx documentation
>
> Feel free to fine tune the documentation as I am not a native
> english
> speaker.
>
> Unfortunately, just after I finished this, I realized that my
> mobile
> does not support the binary format at all, so I won't use this
> in
> production. But I hope this is of use for someone else.
> However, it was
> a good practice :-)
>
> Regards,
> Christian
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal
> Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment
> - and focus on
> what you do best, core application coding. Discover what's new
> with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
>
>

Re: Write support for binary lmx

2009-11-23T09:14:34Z

I also thought about creating a seperate format, but the structure of
the binary and XML format are very similar to each other, so this would
have meant quite a lot of duplicate code.

Also the original specification sais, that implementations should
support both formats. So I think, it makes sense to keep both
implementations close to each other.

(This also means, that even Nokia does not comply strictly to their own
specification :-)

Am Montag, den 23.11.2009, 00:37 -0600 schrieb Robert Lipe:

> Thanx. This seems pretty sane to me. My first inclination is to make
> binary LMX a different format but if they're not supporting it on
> their current devices and this is just a historic thing, it might not
> be so bad.
>
> I've applied this.
>
> 2009/11/6 Christian Bühler <christian@...>
> Hi,
> I sat down a while and implemented write support for the
> binary lmx
> format.
>
> I also implicitly fixed some mistakes in the lmx xml format:
> - XML files support UTF-8, so no need to convert special
> characters
> - Shortnames are now handled just like in gpx
> - There was a missing space in the xsi:schemaLocation
> - indentation is now with tabs just like it is generated by my
> Nokia N82
> - added a test to testo for the binary format
> - I also added a bit to the lmx documentation
>
> Feel free to fine tune the documentation as I am not a native
> english
> speaker.
>
> Unfortunately, just after I finished this, I realized that my
> mobile
> does not support the binary format at all, so I won't use this
> in
> production. But I hope this is of use for someone else.
> However, it was
> a good practice :-)
>
> Regards,
> Christian
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal
> Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment
> - and focus on
> what you do best, core application coding. Discover what's new
> with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
>
>

Re: Write support for binary lmx

2009-11-22T22:37:39Z

Thanx. This seems pretty sane to me. My first inclination is to make binary LMX a different format but if they're not supporting it on their current devices and this is just a historic thing, it might not be so bad.

I've applied this.

2009/11/6 Christian Bühler <christian@...>

Hi,
I sat down a while and implemented write support for the binary lmx
format.

I also implicitly fixed some mistakes in the lmx xml format:
- XML files support UTF-8, so no need to convert special characters
- Shortnames are now handled just like in gpx
- There was a missing space in the xsi:schemaLocation
- indentation is now with tabs just like it is generated by my Nokia N82
- added a test to testo for the binary format
- I also added a bit to the lmx documentation

Feel free to fine tune the documentation as I am not a native english
speaker.

Unfortunately, just after I finished this, I realized that my mobile
does not support the binary format at all, so I won't use this in
production. But I hope this is of use for someone else. However, it was
a good practice :-)

Regards,
Christian

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-19T08:31:44Z

On Thu, Nov 19, 2009 at 10:08:54AM -0600, Robert Lipe wrote:
> Good call, guys. atan2 is in C89, so it should be available everywhere we
> care.
>
> Roger, I was indeed trying to defend against the case of floating point
> jitter near, but not quite equal to zero. The values in question do come
> from 32-bit floats from the device (not ascii) and there's nothing that
> actually stops the device from reporting amounts of or arbitrarily close to
> zero; it's not "just" NMEA/ASCII that we're reading. But I'm quite happy
> making this atan2's problem.

atan (x) is only just a little more than "x" when x is small.

This is what implementations use to implement atan. Many atan2 (and
atan) functions will start with something like:

double atan2 (double y, double x)
{
if (abs (y) < abs(x)) return (PI/4 - atan2 (x, y));

return x + epsilon (x/y);
}

> Jeff, since you're in this section of code, want to drop it in and us send a
> patch?

Good patches reduce the size of the code. (which is possible in this
case!)

Roger.

--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-19T08:08:54Z

Good call, guys. atan2 is in C89, so it should be available everywhere we care.

Roger, I was indeed trying to defend against the case of floating point jitter near, but not quite equal to zero. The values in question do come from 32-bit floats from the device (not ascii) and there's nothing that actually stops the device from reporting amounts of or arbitrarily close to zero; it's not "just" NMEA/ASCII that we're reading. But I'm quite happy making this atan2's problem.

Jeff, since you're in this section of code, want to drop it in and us send a patch?

RJL

On Thu, Nov 19, 2009 at 3:23 AM, Mathias Adam <m.adam@...> wrote:

Rogier Wolff schrieb:

The atan of a division by "almost" zero is well defined. Actually,
in theory, the atan of 1/0 should simply be pi/4 (or whatever it is).

So you're defending against the "east" number being very very small,
but that's not a problem.
So.... I would suggest:

// Although the textbooks recommend against comparing for an exact
// floating point value, we've thought about it and come to the // conclusion that in this case it's appropriate.

I got this mail after sending my own reply. I agree on that, so I'd go this way too in case atan2 isn't usable.
(Note: I just checked atan2, it does give PI/4 for y=1,x=0)

Regards
Mathias

Re: Question on real time tracking

2009-11-19T01:23:14Z

Rogier Wolff schrieb:

> The atan of a division by "almost" zero is well defined. Actually,
> in theory, the atan of 1/0 should simply be pi/4 (or whatever it is).
>
> So you're defending against the "east" number being very very small,
> but that's not a problem.
>
> So.... I would suggest:
>
> // Although the textbooks recommend against comparing for an exact
> // floating point value, we've thought about it and come to the
> // conclusion that in this case it's appropriate.

I got this mail after sending my own reply. I agree on that, so I'd go
this way too in case atan2 isn't usable.
(Note: I just checked atan2, it does give PI/4 for y=1,x=0)

Regards
Mathias

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-19T01:08:07Z

Hello,

perhaps atan2 is of any help here? it takes both x and y values
separately to get the quadrant right. However I'm not sure what it does
if y = 0 though. (I don't have such a device, just stumbled across the
mail on the list...)

Regards
Mathias

Jeff McFadden schrieb:

> How about
>
> if( pvt->east < 0.1 && pvt->east > -0.1 ){
>
> since negative east value means moving west, so those are entirely expected.
>
> -- Jeff
>
>
>
> On Wed, Nov 18, 2009 at 11:17 PM, Robert Lipe <robertlipe@...>wrote:
>
>> Division by zero is bad. Then again, so is numerical comparison with
>> floating point zero. If we change your patch to start with
>>
>> if( pvt->east < 0.1 ){
>>
>> would you still like it as much? If so, I'll appy this and the patch
>> that turns speed calcs on.
>>
>> We've shipped this for three years and never had bugreports of crashes
>> here? Wow.
>>
>> RJL
>>
>>
>>
>>
>> On Wed, Nov 18, 2009 at 1:07 PM, Jeff McFadden <jeff.mcfadden@...>wrote:
>>
>>> I just delved into this today when working on a problem with velocity
>>> data.
>>>
>>> I noticed that in the function (garmin.c)
>>>
>>> pvt2wpt(GPS_PPvt_Data pvt, waypoint *wpt)
>>>
>>>
>>> That this code is running (line 635):
>>>
>>> if ( pvt->east >= 0.0 ){
>>> wpt->course = 90 - DEG(atan(pvt->north/pvt->east));
>>> }else{
>>> wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
>>> }
>>>
>>>
>>> Since the north and east values are velocity, my guess is that when the
>>> gps is losing a fix it's returning a 0 for velocity, and the program is
>>> crashing with a divide-by-zero error.
>>>
>>> A solution is something like
>>>
>>> if( pvt->east == 0.0 ){
>>> wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please
>>> }else if ( pvt->east > 0.0 ){
>>> wpt->course = 90 - DEG(atan(pvt->north/pvt->east));
>>> }else{
>>> wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
>>> }
>>>
>>>
>>> That's a guess only, but it seems like it's an error whether that's
>>> causing this specific crash or not.
>>>
>>> -- Jeff
>>>
>>>
>>> Robert Lipe <robertlipe@gp...> writes:
>>>
>>>> On Tue, Oct 13, 2009 at 6:14 AM, Marc <dkm@ka...> wrote:
>>>>
>>>> it, I read the sensors' value and add theses value in the output. The
>>>> problem I have is that when the GPS looses signal, gpsbabel exits. I
>>>>
>>>>
>>>> It's not supposed to. In fact, that was one of the test criteria for
>>> that
>>>> mode. Now different GPSes have been added since my original work and
>>> they may
>>>> have different failure states, but in the absence of debug traces, a GPS
>>> model,
>>>> connection media, operating system in use, or so on the search area for
>>>> guessing is large.
>>> Thanks for your answer. I can already provide more info, but I'll
>>> investigate exactly what happens by looking more deeply into the code
>>> (which I already did some time ago...).
>>>
>>> I'm using a Garmin Vista Cx through the USB on an Ubuntu 9.04 :)
>>>
>>> But as I said, I'll gather more info to narrow down my problem.
>>>
>>> Thanks,
>>> Marc
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>>> 30-Day
>>> trial. Simplify your report design, integration and deployment - and focus
>>> on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>>> _______________________________________________
>>> Gpsbabel-code mailing list http://www.gpsbabel.org
>>> Gpsbabel-code@...
>>> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
>>>
>>>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-19T00:52:46Z

On Thu, Nov 19, 2009 at 12:17:46AM -0600, Robert Lipe wrote:
> Division by zero is bad. Then again, so is numerical comparison with
> floating point zero. If we change your patch to start with
>
> if( pvt->east < 0.1 ){
>
> would you still like it as much? If so, I'll appy this and the patch
> that turns speed calcs on.

The atan of a division by "almost" zero is well defined. Actually,
in theory, the atan of 1/0 should simply be pi/4 (or whatever it is).

So you're defending against the "east" number being very very small,
but that's not a problem.

In theory, the division can overflow, if "north" is very large, and
"east" very small. But because "north" is a speed from the physical
world, it is unlikely to be near the maximum double floating point
number. That only leaves east, which might be close to the absolute
minimum value for a floating point number. This again is very very
unlikely. Mostly because GPSes deliver their coordinates in
fixed-point-ascii, so such a small velocity is unlikely to be
representable.

So.... I would suggest:

// Although the textbooks recommend against comparing for an exact
// floating point value, we've thought about it and come to the
// conclusion that in this case it's appropriate.

roger

>
> We've shipped this for three years and never had bugreports of crashes
> here? Wow.
>
> RJL
>
>
>
>
> On Wed, Nov 18, 2009 at 1:07 PM, Jeff McFadden <jeff.mcfadden@...>wrote:
>
> > I just delved into this today when working on a problem with velocity data.
> >
> > I noticed that in the function (garmin.c)
> >
> > pvt2wpt(GPS_PPvt_Data pvt, waypoint *wpt)
> >
> >
> > That this code is running (line 635):
> >
> > if ( pvt->east >= 0.0 ){
> > wpt->course = 90 - DEG(atan(pvt->north/pvt->east));
> > }else{
> > wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
> > }
> >
> >
> > Since the north and east values are velocity, my guess is that when the gps
> > is losing a fix it's returning a 0 for velocity, and the program is crashing
> > with a divide-by-zero error.
> >
> > A solution is something like
> >
> > if( pvt->east == 0.0 ){
> > wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please
> > }else if ( pvt->east > 0.0 ){
> > wpt->course = 90 - DEG(atan(pvt->north/pvt->east));
> > }else{
> > wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
> > }
> >
> >
> > That's a guess only, but it seems like it's an error whether that's causing
> > this specific crash or not.
> >
> > -- Jeff
> >
> >
> > Robert Lipe <robertlipe@gp...> writes:
> >
> > > On Tue, Oct 13, 2009 at 6:14 AM, Marc <dkm@ka...> wrote:
> > >
> > > it, I read the sensors' value and add theses value in the output. The
> > > problem I have is that when the GPS looses signal, gpsbabel exits. I
> > >
> > >
> > > It's not supposed to. In fact, that was one of the test criteria for
> > that
> > > mode. Now different GPSes have been added since my original work and
> > they may
> > > have different failure states, but in the absence of debug traces, a GPS
> > model,
> > > connection media, operating system in use, or so on the search area for
> > > guessing is large.
> >
> > Thanks for your answer. I can already provide more info, but I'll
> > investigate exactly what happens by looking more deeply into the code
> > (which I already did some time ago...).
> >
> > I'm using a Garmin Vista Cx through the USB on an Ubuntu 9.04 :)
> >
> > But as I said, I'll gather more info to narrow down my problem.
> >
> > Thanks,
> > Marc
> >
> >
> > ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> > trial. Simplify your report design, integration and deployment - and focus
> > on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now. http://p.sf.net/sfu/bobj-july
> > _______________________________________________
> > Gpsbabel-code mailing list http://www.gpsbabel.org
> > Gpsbabel-code@...
> > https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
> >
> >

> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

--
** R.E.Wolff@... ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-18T22:34:23Z

How about

if( pvt->east < 0.1 && pvt->east > -0.1 ){

since negative east value means moving west, so those are entirely expected.

-- Jeff

On Wed, Nov 18, 2009 at 11:17 PM, Robert Lipe <robertlipe@...> wrote:

Division by zero is bad.   Then again, so is numerical comparison with floating point zero.   If we change your patch to start with

if( pvt->east < 0.1 ){

would you still like it as much?     If so, I'll appy this and the patch that turns speed calcs on.

We've shipped this for three years and never had bugreports of crashes here?   Wow.

RJL

On Wed, Nov 18, 2009 at 1:07 PM, Jeff McFadden <jeff.mcfadden@...> wrote:

I just delved into this today when working on a problem with velocity data.

I noticed that in the function (garmin.c)

pvt2wpt(GPS_PPvt_Data pvt, waypoint *wpt)

That this code is running (line 635):

if ( pvt->east >= 0.0 ){
wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

}else{
wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
}

Since the north and east values are velocity, my guess is that when the gps is losing a fix it's returning a 0 for velocity, and the program is crashing with a divide-by-zero error.

A solution is something like

if( pvt->east == 0.0 ){
wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please

}else if ( pvt->east > 0.0 ){
wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

}else{
wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
}

That's a guess only, but it seems like it's an error whether that's causing this specific crash or not.

-- Jeff

Robert Lipe <robertlipe@gp...> writes:

> On Tue, Oct 13, 2009 at 6:14 AM, Marc <dkm@ka...> wrote:
>
> it, I read the sensors' value and add theses value in the output. The
> problem I have is that when the GPS looses signal, gpsbabel exits. I
>
>
> It's not supposed to. In fact, that was one of the test criteria for that
> mode. Now different GPSes have been added since my original work and they may
> have different failure states, but in the absence of debug traces, a GPS model,
> connection media, operating system in use, or so on the search area for
> guessing is large.

Thanks for your answer. I can already provide more info, but I'll
investigate exactly what happens by looking more deeply into the code
(which I already did some time ago...).

I'm using a Garmin Vista Cx through the USB on an Ubuntu 9.04 :)

But as I said, I'll gather more info to narrow down my problem.

Thanks,
Marc

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-18T22:17:46Z

Division by zero is bad. Then again, so is numerical comparison with floating point zero. If we change your patch to start with

if( pvt->east < 0.1 ){

would you still like it as much? If so, I'll appy this and the patch that turns speed calcs on.

We've shipped this for three years and never had bugreports of crashes here? Wow.

RJL

On Wed, Nov 18, 2009 at 1:07 PM, Jeff McFadden <jeff.mcfadden@...> wrote:

I just delved into this today when working on a problem with velocity data.

I noticed that in the function (garmin.c)

pvt2wpt(GPS_PPvt_Data pvt, waypoint *wpt)

That this code is running (line 635):

if ( pvt->east >= 0.0 ){
wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

}else{
wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
}

Since the north and east values are velocity, my guess is that when the gps is losing a fix it's returning a 0 for velocity, and the program is crashing with a divide-by-zero error.

A solution is something like

if( pvt->east == 0.0 ){
wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please

}else if ( pvt->east > 0.0 ){
wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

}else{
wpt->course = 270 - DEG(atan(pvt->north/pvt->east));
}

That's a guess only, but it seems like it's an error whether that's causing this specific crash or not.

-- Jeff

Robert Lipe <robertlipe@gp...> writes:

> On Tue, Oct 13, 2009 at 6:14 AM, Marc <dkm@ka...> wrote:
>
> it, I read the sensors' value and add theses value in the output. The
> problem I have is that when the GPS looses signal, gpsbabel exits. I
>
>
> It's not supposed to. In fact, that was one of the test criteria for that
> mode. Now different GPSes have been added since my original work and they may
> have different failure states, but in the absence of debug traces, a GPS model,
> connection media, operating system in use, or so on the search area for
> guessing is large.

Thanks for your answer. I can already provide more info, but I'll
investigate exactly what happens by looking more deeply into the code
(which I already did some time ago...).

I'm using a Garmin Vista Cx through the USB on an Ubuntu 9.04 :)

But as I said, I'll gather more info to narrow down my problem.

Thanks,
Marc

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: PATCH: detect serial ports in qt-gui under win32

2009-11-18T21:54:16Z

Much simpler than the approaches I'd considered and it seems to get the job done. Appliled. Thanx.

On Sat, Nov 14, 2009 at 7:31 AM, Tal <tal.bav@...> wrote:

The new gui is great! I use it often in windows.
This patch detects the available serial ports using the
QueryDosDevice() function.
According to an msdn page I've googled, this function is available
from Windows 2000 and later.
A version of windows without QueryDosDevice(), will probably not be
able to load GpsBabelFE.exe at all, because this patch does not look
for the function at runtime. I hope this is acceptable.

See also, a relevant message in gpsbabel-misc:
http://sourceforge.net/mailarchive/message.php?msg_name=82a839a50911130917t41e5fd9es70e75196e351791%40mail.gmail.com

Index: gui/serial_win.cpp
===================================================================
RCS file: /cvsroot/gpsbabel/gpsbabel/gui/serial_win.cpp,v
retrieving revision 1.1
diff -U5 -r1.1 serial_win.cpp
--- gui/serial_win.cpp 2 Sep 2009 19:05:27 -0000 1.1
+++ gui/serial_win.cpp 14 Nov 2009 13:08:04 -0000
@@ -19,10 +19,12 @@
// USA
//

#include "mainwindow.h"

+#if 0 // Does not require Windows 2000
+
static const char *deviceNames[] = {
"com1:",
"com2:",
"com3:",
"com4:",
@@ -33,5 +35,35 @@
{
for (int i=0; deviceNames[i]; i++) {
box->addItem(deviceNames[i]);
}
}
+
+#else // This code assumes Windows 2000 or later
+
+#include <Windows.h> // QueryDosDevice(), Minimum supported: Windows
2000 Professional/Server
+#include <stdio.h>
+
+void MainWindow::osLoadDeviceNameCombos(QComboBox *box)
+{
+ char DevList[64*1024-1]; // a single byte more, and certain
versions of windows
+ // always return QueryDosDevice()==0 &&
GetLastError()==ERROR_MORE_DATA.
+ // see http://support.microsoft.com/kb/931305
+ // Get a list of all existing MS-DOS device names. Stores one or
more asciiz strings followed by an extra null.
+ DWORD res = QueryDosDeviceA(NULL, DevList, sizeof(DevList));
+ if (res == 0)
+ {
+ DWORD err = GetLastError(); // could check for
ERROR_INSUFFICIENT_BUFFER, and retry with a larger buffer.
+ // but DevList is already at the
maximum size it can be without running into kb 931305.
+ fprintf(stderr,"QueryDosDevice() failed with %d.
GetLastError()==%d.\n", res, err);
+ return;
+ }
+
+ for (char *p=DevList; *p;) {
+ int len = strlen(p);
+ if (strncmp(p,"COM",3)==0)
+ box->addItem((PCHAR)p);
+ p += len+1; // +1 to also skip the null character of each string
+ }
+}
+
+#endif

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Question on real time tracking

2009-11-18T11:07:02Z

I just delved into this today when working on a problem with velocity data.

I noticed that in the function (garmin.c)

pvt2wpt(GPS_PPvt_Data pvt, waypoint *wpt)

That this code is running (line 635):

if ( pvt->east >= 0.0 ){

wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

}else{

wpt->course = 270 - DEG(atan(pvt->north/pvt->east));

}

Since the north and east values are velocity, my guess is that when the gps is losing a fix it's returning a 0 for velocity, and the program is crashing with a divide-by-zero error.

A solution is something like

if( pvt->east == 0.0 ){

wpt->course = ( pvt->north > 0 ? 0 : 180 ); // Don't divide by zero please

}else if ( pvt->east > 0.0 ){

wpt->course = 90 - DEG(atan(pvt->north/pvt->east));

}else{

wpt->course = 270 - DEG(atan(pvt->north/pvt->east));

}

That's a guess only, but it seems like it's an error whether that's causing this specific crash or not.

-- Jeff

Robert Lipe <robertlipe@gp...> writes:

> On Tue, Oct 13, 2009 at 6:14 AM, Marc <dkm@ka...> wrote:
>
> it, I read the sensors' value and add theses value in the output. The
> problem I have is that when the GPS looses signal, gpsbabel exits. I
>
>
> It's not supposed to. In fact, that was one of the test criteria for that
> mode. Now different GPSes have been added since my original work and they may
> have different failure states, but in the absence of debug traces, a GPS model,
> connection media, operating system in use, or so on the search area for
> guessing is large.

Thanks for your answer. I can already provide more info, but I'll
investigate exactly what happens by looking more deeply into the code
(which I already did some time ago...).

I'm using a Garmin Vista Cx through the USB on an Ubuntu 9.04 :)

But as I said, I'll gather more info to narrow down my problem.

Thanks,
Marc

Re: delbin patch: recognize device error message

2009-11-18T07:11:09Z

Excellent catch, Paul. I'd missed that. Thanx. Applied.

On Mon, Nov 16, 2009 at 10:44 PM, Paul Cornett <pc-gpsb@...> wrote:

I just saw the report on the users list about somebody having trouble
with a PN. Looking at the debug output he uploaded, I see the device
sending an error message (id 0xa003) with a string of "internal error".
No idea if that is our fault (I'm inclined to think not), but we should
probably just give up if we get an error like that from the device.
Patch attached.

delbin patch: recognize device error message

2009-11-16T20:44:38Z

I just saw the report on the users list about somebody having trouble
with a PN. Looking at the debug output he uploaded, I see the device
sending an error message (id 0xa003) with a string of "internal error".
No idea if that is our fault (I'm inclined to think not), but we should
probably just give up if we get an error like that from the device.
Patch attached.

Index: delbin.c =================================================================== --- delbin.c (revision 39) +++ delbin.c (working copy) @@ -151,6 +151,7 @@ #define MSG_CAPABILITIES 0xb001 #define MSG_DELETE 0xb005 #define MSG_DELETE_SIZE 67 +#define MSG_ERROR 0xa003 #define MSG_NAVIGATION 0xa010 #define MSG_REQUEST_ROUTES 0xb051 #define MSG_REQUEST_ROUTES_SIZE 65 @@ -772,6 +773,10 @@ if (id == 0) { break; } + if (id == MSG_ERROR) { + const gbuint8* p = m->data; + fatal(MYNAME ": device error %u: \"%s\"\n", *p, p + 1); + } message_ack(id, m); if (id == msg_id || time(NULL) - time_start >= READ_TIMEOUT) { break;

PATCH: detect serial ports in qt-gui under win32

2009-11-14T05:31:26Z

The new gui is great! I use it often in windows.
This patch detects the available serial ports using the
QueryDosDevice() function.
According to an msdn page I've googled, this function is available
from Windows 2000 and later.
A version of windows without QueryDosDevice(), will probably not be
able to load GpsBabelFE.exe at all, because this patch does not look
for the function at runtime. I hope this is acceptable.

See also, a relevant message in gpsbabel-misc:
http://sourceforge.net/mailarchive/message.php?msg_name=82a839a50911130917t41e5fd9es70e75196e351791%40mail.gmail.com

Index: gui/serial_win.cpp
===================================================================
RCS file: /cvsroot/gpsbabel/gpsbabel/gui/serial_win.cpp,v
retrieving revision 1.1
diff -U5 -r1.1 serial_win.cpp
--- gui/serial_win.cpp 2 Sep 2009 19:05:27 -0000 1.1
+++ gui/serial_win.cpp 14 Nov 2009 13:08:04 -0000
@@ -19,10 +19,12 @@
// USA
//

#include "mainwindow.h"

+#if 0 // Does not require Windows 2000
+
static const char *deviceNames[] = {
"com1:",
"com2:",
"com3:",
"com4:",
@@ -33,5 +35,35 @@
{
for (int i=0; deviceNames[i]; i++) {
box->addItem(deviceNames[i]);
}
}
+
+#else // This code assumes Windows 2000 or later
+
+#include <Windows.h> // QueryDosDevice(), Minimum supported: Windows
2000 Professional/Server
+#include <stdio.h>
+
+void MainWindow::osLoadDeviceNameCombos(QComboBox *box)
+{
+ char DevList[64*1024-1]; // a single byte more, and certain
versions of windows
+ // always return QueryDosDevice()==0 &&
GetLastError()==ERROR_MORE_DATA.
+ // see http://support.microsoft.com/kb/931305
+ // Get a list of all existing MS-DOS device names. Stores one or
more asciiz strings followed by an extra null.
+ DWORD res = QueryDosDeviceA(NULL, DevList, sizeof(DevList));
+ if (res == 0)
+ {
+ DWORD err = GetLastError(); // could check for
ERROR_INSUFFICIENT_BUFFER, and retry with a larger buffer.
+ // but DevList is already at the
maximum size it can be without running into kb 931305.
+ fprintf(stderr,"QueryDosDevice() failed with %d.
GetLastError()==%d.\n", res, err);
+ return;
+ }
+
+ for (char *p=DevList; *p;) {
+ int len = strlen(p);
+ if (strncmp(p,"COM",3)==0)
+ box->addItem((PCHAR)p);
+ p += len+1; // +1 to also skip the null character of each string
+ }
+}
+
+#endif

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

gpsbabel-gui-serial-win.diff.zip (1K) Download Attachment

Write support for binary lmx

2009-11-06T10:37:56Z

Hi,
I sat down a while and implemented write support for the binary lmx
format.

I also implicitly fixed some mistakes in the lmx xml format:
- XML files support UTF-8, so no need to convert special characters
- Shortnames are now handled just like in gpx
- There was a missing space in the xsi:schemaLocation
- indentation is now with tabs just like it is generated by my Nokia N82
- added a test to testo for the binary format
- I also added a bit to the lmx documentation

Feel free to fine tune the documentation as I am not a native english
speaker.

Unfortunately, just after I finished this, I realized that my mobile
does not support the binary format at all, so I won't use this in
production. But I hope this is of use for someone else. However, it was
a good practice :-)

Regards,
Christian

[lmx_binary.diff]

diff --git a/lmx.c b/lmx.c index f40762b..84fd561 100644 --- a/lmx.c +++ b/lmx.c @@ -32,11 +32,15 @@ static gbfile *ofd; static waypoint *wpt_tmp; char *urllink, *urllinkt; +static char *binary = NULL; #define MYNAME "lmx" static arglist_t lmx_args[] = { + { "binary", &binary, + "Compact binary representation", + NULL, ARGTYPE_BOOL, ARG_NOMINMAX }, ARG_TERMINATOR }; @@ -57,61 +61,181 @@ lmx_wr_deinit(void) gbfclose(ofd); } +static char * +lmx_stag(int tag) +{ + switch (tag) { + case 0xC5: return "lmx"; + case 0x46: return "landmarkCollection"; + case 0x47: return "landmark"; + case 0x48: return "name"; + case 0x49: return "description"; + case 0x4A: return "coordinates"; + case 0x4B: return "latitude"; + case 0x4C: return "longitude"; + case 0x4D: return "altitude"; + case 0x4E: return "horizontalAccuracy"; + case 0x4F: return "verticalAccuracy"; + case 0x50: return "timeStamp"; + case 0x51: return "coverageRadius"; + case 0x52: return "category"; + case 0x53: return "id"; + case 0x54: return "addressInfo"; + case 0x55: return "country"; + case 0x56: return "countryCode"; + case 0x57: return "state"; + case 0x58: return "county"; + case 0x59: return "city"; + case 0x5A: return "district"; + case 0x5B: return "postalCode"; + case 0x5C: return "crossing1"; + case 0x5D: return "crossing2"; + case 0x5E: return "street"; + case 0x5F: return "buildingName"; + case 0x60: return "buildingFloor"; + case 0x61: return "buildingZone"; + case 0x62: return "buildingRoom"; + case 0x63: return "extension"; + case 0x64: return "phoneNumber"; + case 0x65: return "mediaLink"; + case 0x66: return "mime"; + case 0x67: return "url"; + default: return 0; + } +} + static void -lmx_write_xml(int indent_level, const char *tag, const char *data) +lmx_indent(int count) { int i; - char *tmp_ent = xml_entitize(data); + for (i=0; i<count; i++) + gbfputc('\t', ofd); +} - for (i = 0; i < indent_level; i++) { - gbfputs(" ", ofd); +static void +lmx_start_tag(int tag, int indent) +{ + if (binary) + gbfputc(tag, ofd); + else { + lmx_indent(indent); + gbfprintf(ofd, "<lm:%s>", lmx_stag(tag)); } +} - gbfprintf(ofd, "<%s>%s</%s>\n", tag, tmp_ent, tag); +static void +lmx_end_tag(int tag, int indent) +{ + if (binary) + gbfputc(0x01, ofd); + else { + lmx_indent(indent); + gbfprintf(ofd, "</lm:%s>\n", lmx_stag(tag)); + } +} - xfree(tmp_ent); +static void +lmx_write_xml(int tag, const char *data, int indent) +{ + lmx_start_tag(tag, indent); + + if (binary) { + gbfputc(0x03, ofd); // inline string follows + gbfputcstr(data, ofd); + } + else { + char *tmp_ent = xml_entitize(data); + gbfputs(tmp_ent, ofd); + xfree(tmp_ent); + } + + lmx_end_tag(tag, 0); } static void lmx_print(const waypoint *wpt) { - gbfprintf(ofd, " <lm:landmark>\n"); - if (wpt->shortname) { - lmx_write_xml(4, "lm:name", global_opts.synthesize_shortnames ? wpt->description : wpt->shortname); + const char *oname; + char *odesc; + char tbuf[100]; + + /* + * Desparation time, try very hard to get a good shortname + */ + odesc = wpt->notes; + if (!odesc) { + odesc = wpt->description; + } + if (!odesc) { + odesc = wpt->shortname; + } + + oname = global_opts.synthesize_shortnames ? odesc : wpt->shortname; + + lmx_start_tag(0x47, 2); // landmark + if (!binary) gbfputc('\n', ofd); + if (oname) { + lmx_write_xml(0x48, oname, 3); // name } if (wpt->description) { - lmx_write_xml(4, "lm:description", wpt->description); + lmx_write_xml(0x49, wpt->description, 3); // description } - gbfprintf(ofd, " <lm:coordinates>\n"); - gbfprintf(ofd, " <lm:latitude>%f</lm:latitude>\n", wpt->latitude); - gbfprintf(ofd, " <lm:longitude>%f</lm:longitude>\n",wpt->longitude); + lmx_start_tag(0x4A, 3); // coordinates + if (!binary) gbfputc('\n', ofd); + + sprintf(tbuf, "%f", wpt->latitude); + lmx_write_xml(0x4B, tbuf, 4); // latitude + + sprintf(tbuf, "%f", wpt->longitude); + lmx_write_xml(0x4C, tbuf, 4); // longitude + if (wpt->altitude && (wpt->altitude != unknown_alt)) { - gbfprintf(ofd, " <lm:altitude>%f</lm:altitude>\n",wpt->altitude); + sprintf(tbuf, "%f", wpt->altitude); + lmx_write_xml(0x4D, tbuf, 4); // altitude } - gbfprintf(ofd, " </lm:coordinates>\n"); + lmx_end_tag(0x4A, 3); // coordinates if (wpt->url && wpt->url[0]) { - gbfprintf(ofd, " <lm:mediaLink>\n"); + lmx_start_tag(0x65, 3); // mediaLink + if (!binary) gbfputc('\n', ofd); if (wpt->url_link_text) - lmx_write_xml(5,"lm:name", wpt->url_link_text); - lmx_write_xml(5, "lm:url", wpt->url); - gbfprintf(ofd, " </lm:mediaLink>\n"); + lmx_write_xml(0x48, wpt->url_link_text, 4); // name + lmx_write_xml(0x67, wpt->url, 4); // url + lmx_end_tag(0x65, 3); // mediaLink } - gbfprintf(ofd, " </lm:landmark>\n"); + lmx_end_tag(0x47, 2); // landmark } static void lmx_write(void) { - gbfprintf(ofd, "<?xml version=\"1.0\" ?>\n"); - gbfprintf(ofd, "<lm:lmx xmlns:lm=\"http://www.nokia.com/schemas/location/landmarks/1/0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.nokia.com/schemas/location/landmarks/1/0/lmx.xsd\">"); + if (binary) { + gbfputc(0x03, ofd); // WBXML version 1.3 + gbfputuint16(0x04A4, ofd); // "-//NOKIA//DTD LANDMARKS 1.0//EN" + gbfputc(106, ofd); // Charset=UTF-8 + gbfputc(0x00, ofd); // empty string table + gbfputc(0xC5, ofd); // lmx + gbfputc(0x05, ofd); // xmlns=http://www.nokia.com/schemas/location/landmarks/ + gbfputc(0x85, ofd); // 1/0/ + gbfputc(0x06, ofd); // xmlns:xsi= + gbfputc(0x86, ofd); // http://www.w3.org/2001/XMLSchema-instance + gbfputc(0x07, ofd); // xsi:schemaLocation=http://www.nokia.com/schemas/location/landmarks/ + gbfputc(0x85, ofd); // 1/0/ + gbfputc(0x87, ofd); // whitespace + gbfputc(0x88, ofd); // lmx.xsd + gbfputc(0x01, ofd); // END lmx attributes + } else { + gbfprintf(ofd, "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n"); + gbfprintf(ofd, "<lm:lmx xmlns:lm=\"http://www.nokia.com/schemas/location/landmarks/1/0\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:schemaLocation=\"http://www.nokia.com/schemas/location/landmarks/1/0/ lmx.xsd\">\n"); + } - gbfprintf(ofd, " <lm:landmarkCollection>\n"); + lmx_start_tag(0x46, 1); // landmarkCollection + if (!binary) gbfputc('\n', ofd); waypt_disp_all(lmx_print); - gbfprintf(ofd, " </lm:landmarkCollection>\n"); - gbfprintf(ofd, "</lm:lmx>\n"); + lmx_end_tag(0x46, 1); // landmarkCollection + lmx_end_tag(0xC5, 0); // lmx } /* @@ -242,5 +366,5 @@ ff_vecs_t lmx_vecs = { lmx_write, NULL, lmx_args, - CET_CHARSET_ASCII, 0 /* CET-REVIEW */ + CET_CHARSET_UTF8, 0 /* CET-REVIEW */ }; diff --git a/reference/binary.lmx b/reference/binary.lmx new file mode 100644 index 0000000..cceb86e Binary files /dev/null and b/reference/binary.lmx differ diff --git a/reference/nokia.lmx b/reference/nokia.lmx index 1807707..01331e8 100644 --- a/reference/nokia.lmx +++ b/reference/nokia.lmx @@ -1,112 +1,113 @@ -<?xml version="1.0" ?> -<lm:lmx xmlns:lm="http://www.nokia.com/schemas/location/landmarks/1/0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nokia.com/schemas/location/landmarks/1/0/lmx.xsd"> <lm:landmarkCollection> - <lm:landmark> - <lm:name>GCEBB</lm:name> - <lm:description>Mountain Bike Heaven by susy1313</lm:description> - <lm:coordinates> - <lm:latitude>35.972033</lm:latitude> - <lm:longitude>-87.134700</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=3771</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC1A37</lm:name> - <lm:description>The Troll by a182pilot & Family</lm:description> - <lm:coordinates> - <lm:latitude>36.090683</lm:latitude> - <lm:longitude>-86.679550</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=6711</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC1C2B</lm:name> - <lm:description>Dive Bomber by JoGPS & family</lm:description> - <lm:coordinates> - <lm:latitude>35.996267</lm:latitude> - <lm:longitude>-86.620117</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=7211</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC25A9</lm:name> - <lm:description>FOSTER by JoGPS & Family</lm:description> - <lm:coordinates> - <lm:latitude>36.038483</lm:latitude> - <lm:longitude>-86.648617</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=9641</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC2723</lm:name> - <lm:description>Logan Lighthouse by JoGps & Family</lm:description> - <lm:coordinates> - <lm:latitude>36.112183</lm:latitude> - <lm:longitude>-86.741767</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=10019</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC2B71</lm:name> - <lm:description>Ganier Cache by Susy1313</lm:description> - <lm:coordinates> - <lm:latitude>36.064083</lm:latitude> - <lm:longitude>-86.790517</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=11121</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC309F</lm:name> - <lm:description>Shy's Hill by FireFighterEng33</lm:description> - <lm:coordinates> - <lm:latitude>36.087767</lm:latitude> - <lm:longitude>-86.809733</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=12447</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC317A</lm:name> - <lm:description>GittyUp by JoGPS / Warner Parks</lm:description> - <lm:coordinates> - <lm:latitude>36.057500</lm:latitude> - <lm:longitude>-86.892000</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=12666</lm:url> - </lm:mediaLink> - </lm:landmark> - <lm:landmark> - <lm:name>GC317D</lm:name> - <lm:description>Inlighting by JoGPS / Warner Parks</lm:description> - <lm:coordinates> - <lm:latitude>36.082800</lm:latitude> - <lm:longitude>-86.867283</lm:longitude> - </lm:coordinates> - <lm:mediaLink> - <lm:name>Cache Details</lm:name> - <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=12669</lm:url> - </lm:mediaLink> - </lm:landmark> - </lm:landmarkCollection> +<?xml version="1.0" encoding="UTF-8"?> +<lm:lmx xmlns:lm="http://www.nokia.com/schemas/location/landmarks/1/0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.nokia.com/schemas/location/landmarks/1/0/ lmx.xsd"> + <lm:landmarkCollection> + <lm:landmark> + <lm:name>GCEBB</lm:name> + <lm:description>Mountain Bike Heaven by susy1313</lm:description> + <lm:coordinates> + <lm:latitude>35.972033</lm:latitude> + <lm:longitude>-87.134700</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=3771</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC1A37</lm:name> + <lm:description>The Troll by a182pilot & Family</lm:description> + <lm:coordinates> + <lm:latitude>36.090683</lm:latitude> + <lm:longitude>-86.679550</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=6711</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC1C2B</lm:name> + <lm:description>Dive Bomber by JoGPS & family</lm:description> + <lm:coordinates> + <lm:latitude>35.996267</lm:latitude> + <lm:longitude>-86.620117</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=7211</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC25A9</lm:name> + <lm:description>FOSTER by JoGPS & Family</lm:description> + <lm:coordinates> + <lm:latitude>36.038483</lm:latitude> + <lm:longitude>-86.648617</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=9641</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC2723</lm:name> + <lm:description>Logan Lighthouse by JoGps & Family</lm:description> + <lm:coordinates> + <lm:latitude>36.112183</lm:latitude> + <lm:longitude>-86.741767</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=10019</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC2B71</lm:name> + <lm:description>Ganier Cache by Susy1313</lm:description> + <lm:coordinates> + <lm:latitude>36.064083</lm:latitude> + <lm:longitude>-86.790517</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=11121</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC309F</lm:name> + <lm:description>Shy's Hill by FireFighterEng33</lm:description> + <lm:coordinates> + <lm:latitude>36.087767</lm:latitude> + <lm:longitude>-86.809733</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=12447</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC317A</lm:name> + <lm:description>GittyUp by JoGPS / Warner Parks</lm:description> + <lm:coordinates> + <lm:latitude>36.057500</lm:latitude> + <lm:longitude>-86.892000</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=12666</lm:url> + </lm:mediaLink> + </lm:landmark> + <lm:landmark> + <lm:name>GC317D</lm:name> + <lm:description>Inlighting by JoGPS / Warner Parks</lm:description> + <lm:coordinates> + <lm:latitude>36.082800</lm:latitude> + <lm:longitude>-86.867283</lm:longitude> + </lm:coordinates> + <lm:mediaLink> + <lm:name>Cache Details</lm:name> + <lm:url>http://www.geocaching.com/seek/cache_details.asp?ID=12669</lm:url> + </lm:mediaLink> + </lm:landmark> + </lm:landmarkCollection> </lm:lmx> diff --git a/testo b/testo index 2134fb8..4edd485 100755 --- a/testo +++ b/testo @@ -1298,6 +1298,8 @@ compare ${REFERENCE}/umsonstdraussen.gpx ${TMPDIR}/umsonstdraussen.gpx # gpsbabel -i lmx -f ${REFERENCE}/nokia.lmx -o lmx -F ${TMPDIR}/nokia.lmx compare ${REFERENCE}/nokia.lmx ${TMPDIR}/nokia.lmx +gpsbabel -i lmx -f ${REFERENCE}/nokia.lmx -o lmx,binary -F ${TMPDIR}/binary.lmx +bincompare ${REFERENCE}/binary.lmx ${TMPDIR}/binary.lmx # # Swiss Map (.xol) tests diff --git a/xmldoc/formats/lmx.xml b/xmldoc/formats/lmx.xml index 8f512a8..f668be4 100644 --- a/xmldoc/formats/lmx.xml +++ b/xmldoc/formats/lmx.xml @@ -1,6 +1,14 @@ <para> -This format supports Nokia Landmark Exchange (LMX) files used by several -Nokia phones. GPSBabel supports only the traditional XML format and -not the compressed binary format. +This format supports +<ulink url="http://sw.nokia.com/id/9001c8de-c19e-41a0-87d3-5be4297e4d4c/S60_Platform_Landmarks_Exchange_Specification_v1_0_en.pdf"> +Nokia Landmark Exchange (LMX) files</ulink> used by several Nokia phones. +GPSBabel supports the traditional XML format for reading and writing. The +compressed binary format (WBXML) can be written, but most current Nokia phones +do not support it (confirmed with N82 and N95). +</para> +<para> +With this format, landmarks can be imported into the landmark store of the +mobile phone. This landmark store is then used to display them on a map with +several applications. The most common ones are the pre-installed Ovi Maps (or +its predecessor Nokia Maps) and Google Maps Mobile. </para> - diff --git a/xmldoc/formats/options/lmx-binary.xml b/xmldoc/formats/options/lmx-binary.xml new file mode 100644 index 0000000..dbf05fb --- /dev/null +++ b/xmldoc/formats/options/lmx-binary.xml @@ -0,0 +1,9 @@ +<para> +This option specifies if you want to write the compressed binary format (WBXML) +instead of the XML format. However, most current Nokia phones do only support +the XML format (confirmed with N82 and N95). +</para> +<para> +This option has no effect when used for input, only reading the traditional XML +format is supported. +</para>

binary.lmx (1K) Download Attachment

Re: mtk / m241 missing doc

2009-11-04T05:42:44Z

Applied. Thanx.

On Wed, Oct 14, 2009 at 2:28 PM, P. Borgentun <e4borgen@...> wrote:

Hi,
I'm to tiered at the moment to find the correct cvs diff parameters so
I send the requested mtk documentation as-is.

As the mtk and m241 are the same module so the docs should probably
be copied to m241-log_enable.xml also.

Regards
Devlin

> I was just tweaking the doc and noticed that
> several of our newly added options are missing doc. Even
> if you don't do docbook, a few sentences explaining why
> an optio is useful is helpful. It looks like we're
> missing:
>
>
> ./dg-100-erase_only.xml
> ./gtrnctr-course.xml
> ./gtrnctr-sport.xml
> ./itracku-bin-backup.xml
> ./itracku-bin-new.xml
> ./m241-erase_only.xml
> ./m241-log_enable.xml
> ./mmo-ver.xml
> ./mtk-erase_only.xml
>
> ./mtk-log_enable.xml
> ./naviguide-output.xml
> ./naviguide-reorder.xml
> ./pathaway-dbicon.xml
>
> If you've sent it to me before, please feel free to
> call me a bozo before sending it again.
>
>
> -----Inline Attachment Follows-----
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference
> in SF, CA
> is the only developer event you need to attend this year.
> Jumpstart your
> developing skills, take BlackBerry mobile applications to
> market and stay
> ahead of the curve. Join us from November 9 - 12, 2009.
> Register now!
> http://p.sf.net/sfu/devconference
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Patch for WSG-1000 to upload marks

2009-10-15T18:36:21Z

The WSG-1000 is similar to WBT-200/100/201, but it also allows waypoint
(or 'mark') uploads.

This patch adds this in a simple way. Also allows you to specify
erase=1 to pre-erase waypoints before uploading.

Patch generated against cvs version of 2009-10-16.
Files
vecs.c (only for description)
wbt200.c - for mods.

protocol for marks for wsg-1000

Read Mark

PC-->WSG1000: @AL,10,2,idx\r\n
//Idx=0:127

WSG1000-->PC: @AL,10,2,idx,markid,icon,lat,lon,alt,name\r\n

Write Mark
When write a marks list that should be erasing all marks first.
@AL,10,3\r\n //Delete all marks suggest delay 1~5 Sec.

Write a mark
@AL,10,1,idx,lat,lon,alt,name\r\n

Regards
Jamie

diff -u gpsbabel/vecs.c gpsbabel-jh/vecs.c --- gpsbabel/vecs.c 2009-10-12 08:20:27.000000000 +1100 +++ gpsbabel-jh/vecs.c 2009-10-16 11:46:23.000000000 +1100 @@ -479,7 +479,7 @@ { &wbt_svecs, "wbt", - "Wintec WBT-100/200 GPS Download", + "Wintec WBT-100/200 Download, WSG-1000 Marks Upload", NULL }, { diff -u gpsbabel/wbt-200.c gpsbabel-jh/wbt-200.c --- gpsbabel/wbt-200.c 2009-06-17 11:27:34.000000000 +1000 +++ gpsbabel-jh/wbt-200.c 2009-10-16 12:29:59.000000000 +1100 @@ -91,6 +91,7 @@ static FILE *fl; static char *port; static char *erase; +static int markpt_index; /* starts from 0, maybe allow user settable */ static enum { UNKNOWN, WBT200, WBT201, WSG1000 @@ -510,7 +511,7 @@ sprintf(wp_name, fmt, index); - wpt->latitude = lat;; + wpt->latitude = lat; wpt->longitude = lon; wpt->altitude = alt; wpt->creation_time = tim; @@ -956,6 +957,78 @@ do_simple("@AL,2,1", BUFSPEC(line_buf)); } +/* WSG1000 G-TRENDER has the ability to upload (and download) mark points. + * These are slightly different to waypoints (or points of interest). + * Future version should allow start index, since these probably determine + * icon displayed. + * Also, download (although, waypoints are easier to set) in future. + * pre-erase using erase=1 + */ + +static void +wsg1000_writemarkpt(const waypoint *wpt) +{ + char line_buf[100]; + char cmd_buf[100]; + char *name; + + if (markpt_index < 0 || markpt_index > 127) /* index from 0 to 127 */ + fatal(MYNAME ": Maximum of 128 route points\n"); + if (wpt->shortname) + name = wpt->shortname; + else if (wpt->description) + name = wpt->description; + else if (wpt->notes) + name = wpt->notes; + else { + sprintf(line_buf, "%d", markpt_index+1); + name = line_buf; + } + sprintf(cmd_buf, "@AL,10,1,%d,%lf,%lf,%lf,%.32s", + markpt_index, + wpt->latitude, + wpt->longitude, + wpt->altitude, + name); + db(1, "Route write %s\n", cmd_buf); + do_simple(cmd_buf, BUFSPEC(line_buf)); + markpt_index++; +} + +static void wsg1000_mark_write(void) { + char line_buf[100]; + + const char *tmp; + + double ver_hw; + double ver_sw; + double ver_fmt; + + /* Read various device information. We don't use much of this yet - + * just log_addr_start and log_addr_end - but it's useful to have it + * here for debug and documentation purposes. + */ + tmp = get_param("@AL,7,1", BUFSPEC(line_buf)); + db(1, "Route write device \"%s\"\n", tmp); + ver_hw = get_param_float("@AL,8,1"); + ver_sw = get_param_float("@AL,8,2"); + ver_fmt = get_param_float("@AL,8,3"); + + db(2, "versions: hw=%f, sw=%f, fmt=%f\n", + ver_hw, ver_sw, ver_fmt); + + if (*erase != '0') { + /* erase marks from device */ + do_simple("@AL,10,3", BUFSPEC(line_buf)); + gb_sleep(5*1000); + } + markpt_index = 0; /* index from 0 to 127 */ + waypt_disp_all(wsg1000_writemarkpt); + + do_simple("@AL,2,1", BUFSPEC(line_buf)); +} + + static void file_read(void) { char buf[512]; size_t rc; @@ -1032,23 +1105,35 @@ } } +static void mark_write(void) { + switch (dev_type) { + case WSG1000: + wsg1000_mark_write(); + break; + + default: + fatal(MYNAME ": Device does not support route upload\n"); + break; + } +} + /* wbt */ static arglist_t wbt_sargs[] = { - { "erase", &erase, "Erase device data after download", + { "erase", &erase, "Erase log after download, marks before upload", "0", ARGTYPE_BOOL, ARG_NOMINMAX }, ARG_TERMINATOR }; ff_vecs_t wbt_svecs = { ff_type_serial, - { ff_cap_read, ff_cap_read, ff_cap_none }, + { ff_cap_read, ff_cap_read, ff_cap_write }, + rd_init, rd_init, - NULL, rd_deinit, - NULL, + rd_deinit, data_read, - NULL, + mark_write, NULL, wbt_sargs, CET_CHARSET_UTF8, 1 /* master process: don't convert anything | CET-REVIEW */

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: OSM elevation patch

2009-10-14T14:05:47Z

Optional: Because the current practice in Openstreetmap is to not
include elevation in the mapdata. Actually, in the OSM data model,
elevation is not a first class citizen. It is only just an other
attribute tag along with tags like "highway=motorway". I my self think
that GPS elevation data is better than no elevation data. So from now on
I will map with elevation data. But I did not want to force inclusion of
ele-tag for other users of -o osm. But perhaps a reversed no_ele
suboption is even better.

xasprintf/free is fine if that is preferred.

Will you do the merge of this into CVS, according to preferred coding
practice? I just made this trival fix a late evening to meet my need. I
don't think I will do more work on gpsbabel. So I am not particulary
interested in opening a CVS account my self.

BTW: Here is the first road I put into OSM with the ele-tag, using
gpsbabel and JOSM, to verify the concept:
http://www.openstreetmap.org/browse/way/42465546

Egil

Robert Lipe wrote:

>
>
> On Tue, Oct 13, 2009 at 4:41 PM, Egil Hjelmeland
> <privat@... <mailto:privat@...>> wrote:
>
> Hi.
>
> I patched my gpsbabel 1.3.6 to handle altitude for OSM files:
>
> For writing OSM file: If you specify "-o osm,ele", altitudes are
> written
> to OSM as " <tag k='ele' v='%.1f'/>".
>
>
> Is there really any reason for this to be optional? If we know the
> elevation, why not just always include it?
>
> Oh, and xasprintf/free are preferred over staticly buffers. Yes, in
> this specific case it's a bit dorky since you're not going to get 100
> digits of fp....
>
> RJL
>
>
>
>
> When reading OSM, "<tag k='ele' v='%f'/>" is read as altitude,
> unconditonally.
>
> I think it will be useful to merge into the gpsbabel sourcetree.
>
> Best regards
> Egil Hjelmeland.
>
>
> --- osm.c.orig 2009-10-06 22:32:02.265000000 +0200
> +++ osm.c 2009-10-13 00:48:38.804800000 +0200
> @@ -25,12 +25,14 @@
> #include "xmlgeneric.h"
>
> static char *opt_tag, *opt_tagnd, *created_by;
> +static char *opt_ele = NULL;
>
> static arglist_t osm_args[] =
> {
> { "tag", &opt_tag, "Write additional way tag key/value pairs",
> NULL, ARGTYPE_STRING, ARG_NOMINMAX },
> { "tagnd", &opt_tagnd, "Write additional node tag key/value
> pairs", NULL, ARGTYPE_STRING, ARG_NOMINMAX },
> { "created_by", &created_by, "Use this value as custom created_by
> value","GPSBabel", ARGTYPE_STRING, ARG_NOMINMAX },
> + { "ele", &opt_ele, "Include elevation tag for OSM nodes", "0",
> ARGTYPE_BOOL, ARG_NOMINMAX },
> ARG_TERMINATOR
> };
>
> @@ -551,6 +553,10 @@
> if (! wpt->shortname)
> wpt->shortname = xstrdup(str);
> }
> + if (strcmp(key, "ele") == 0) {
> + if ( wpt->altitude == unknown_alt)
> + wpt->altitude = atof(str);
> + }
> else if (strcmp(key, "name:en") == 0) {
> if (wpt->shortname)
> xfree(wpt->shortname);
> @@ -835,6 +841,12 @@
> break;
> }
>
> + if ((*opt_ele != '0') &&(wpt->altitude != unknown_alt) ) {
> + char ele[100];
> + sprintf(ele, "%.1f", wpt->altitude);
> + osm_write_tag("ele", ele);
> + }
> +
> if (strlen(created_by) !=0) {
> gbfprintf(fout, " <tag k='created_by'
> v='%s",created_by);
> if (gpsbabel_time != 0)
>
>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year.
> Jumpstart your
> developing skills, take BlackBerry mobile applications to market
> and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> <mailto:Gpsbabel-code@...>
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
>
>

Re: mtk / m241 missing doc

2009-10-14T13:28:33Z

Hi,
I'm to tiered at the moment to find the correct cvs diff parameters so
I send the requested mtk documentation as-is.

As the mtk and m241 are the same module so the docs should probably
be copied to m241-log_enable.xml also.

Regards
Devlin

> I was just tweaking the doc and noticed that
> several of our newly added options are missing doc. Even
> if you don't do docbook, a few sentences explaining why
> an optio is useful is helpful. It looks like we're
> missing:
>
>
> ./dg-100-erase_only.xml
> ./gtrnctr-course.xml
> ./gtrnctr-sport.xml
> ./itracku-bin-backup.xml
> ./itracku-bin-new.xml
> ./m241-erase_only.xml
> ./m241-log_enable.xml
> ./mmo-ver.xml
> ./mtk-erase_only.xml
>
> ./mtk-log_enable.xml
> ./naviguide-output.xml
> ./naviguide-reorder.xml
> ./pathaway-dbicon.xml
>
> If you've sent it to me before, please feel free to
> call me a bozo before sending it again.
>
>
> -----Inline Attachment Follows-----
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference
> in SF, CA
> is the only developer event you need to attend this year.
> Jumpstart your
> developing skills, take BlackBerry mobile applications to
> market and stay
> ahead of the curve. Join us from November 9 - 12, 2009.
> Register now!
> http://p.sf.net/sfu/devconference
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Gpsbabel-code mailing list http://www.gpsbabel.org
> Gpsbabel-code@...
> https://lists.sourceforge.net/lists/listinfo/gpsbabel-code
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
<para>This option will enable the logger after download.</para>
<para>By default the logger is re-enabled when download is finished if previously were enabled.
But if the download is aborted or failed the log functionality won't be enabled again.</para>

<para>This option will only erase the logger data. No data is downloaded.</para>
<para>This option is typically used as a second step after the data has been downloaded and verified.</para>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: OSM elevation patch

2009-10-13T15:12:45Z

On Tue, Oct 13, 2009 at 4:41 PM, Egil Hjelmeland <privat@...> wrote:

Hi.

I patched my gpsbabel 1.3.6 to handle altitude for OSM files:

For writing OSM file: If you specify "-o osm,ele", altitudes are written
to OSM as " <tag k='ele' v='%.1f'/>".

Is there really any reason for this to be optional? If we know the elevation, why not just always include it?

Oh, and xasprintf/free are preferred over staticly buffers. Yes, in this specific case it's a bit dorky since you're not going to get 100 digits of fp....

RJL

When reading OSM, "<tag k='ele' v='%f'/>" is read as altitude,
unconditonally.

I think it will be useful to merge into the gpsbabel sourcetree.

Best regards
Egil Hjelmeland.

--- osm.c.orig 2009-10-06 22:32:02.265000000 +0200
+++ osm.c 2009-10-13 00:48:38.804800000 +0200
@@ -25,12 +25,14 @@
#include "xmlgeneric.h"

static char *opt_tag, *opt_tagnd, *created_by;
+static char *opt_ele = NULL;

static arglist_t osm_args[] =
{
{ "tag", &opt_tag, "Write additional way tag key/value pairs",
NULL, ARGTYPE_STRING, ARG_NOMINMAX },
{ "tagnd", &opt_tagnd, "Write additional node tag key/value
pairs", NULL, ARGTYPE_STRING, ARG_NOMINMAX },
{ "created_by", &created_by, "Use this value as custom created_by
value","GPSBabel", ARGTYPE_STRING, ARG_NOMINMAX },
+ { "ele", &opt_ele, "Include elevation tag for OSM nodes", "0",
ARGTYPE_BOOL, ARG_NOMINMAX },
ARG_TERMINATOR
};

@@ -551,6 +553,10 @@
if (! wpt->shortname)
wpt->shortname = xstrdup(str);
}
+ if (strcmp(key, "ele") == 0) {
+ if ( wpt->altitude == unknown_alt)
+ wpt->altitude = atof(str);
+ }
else if (strcmp(key, "name:en") == 0) {
if (wpt->shortname)
xfree(wpt->shortname);
@@ -835,6 +841,12 @@
break;
}

+ if ((*opt_ele != '0') &&(wpt->altitude != unknown_alt) ) {
+ char ele[100];
+ sprintf(ele, "%.1f", wpt->altitude);
+ osm_write_tag("ele", ele);
+ }
+
if (strlen(created_by) !=0) {
gbfprintf(fout, " <tag k='created_by' v='%s",created_by);
if (gpsbabel_time != 0)

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

OSM elevation patch

2009-10-13T14:41:53Z

Hi.

I patched my gpsbabel 1.3.6 to handle altitude for OSM files:

For writing OSM file: If you specify "-o osm,ele", altitudes are written
to OSM as " <tag k='ele' v='%.1f'/>".

When reading OSM, "<tag k='ele' v='%f'/>" is read as altitude,
unconditonally.

I think it will be useful to merge into the gpsbabel sourcetree.

Best regards
Egil Hjelmeland.

--- osm.c.orig 2009-10-06 22:32:02.265000000 +0200
+++ osm.c 2009-10-13 00:48:38.804800000 +0200
@@ -25,12 +25,14 @@
#include "xmlgeneric.h"

static char *opt_tag, *opt_tagnd, *created_by;
+static char *opt_ele = NULL;

static arglist_t osm_args[] =
{
{ "tag", &opt_tag, "Write additional way tag key/value pairs",
NULL, ARGTYPE_STRING, ARG_NOMINMAX },
{ "tagnd", &opt_tagnd, "Write additional node tag key/value
pairs", NULL, ARGTYPE_STRING, ARG_NOMINMAX },
{ "created_by", &created_by, "Use this value as custom created_by
value","GPSBabel", ARGTYPE_STRING, ARG_NOMINMAX },
+ { "ele", &opt_ele, "Include elevation tag for OSM nodes", "0",
ARGTYPE_BOOL, ARG_NOMINMAX },
ARG_TERMINATOR
};

@@ -551,6 +553,10 @@
if (! wpt->shortname)
wpt->shortname = xstrdup(str);
}
+ if (strcmp(key, "ele") == 0) {
+ if ( wpt->altitude == unknown_alt)
+ wpt->altitude = atof(str);
+ }
else if (strcmp(key, "name:en") == 0) {
if (wpt->shortname)
xfree(wpt->shortname);
@@ -835,6 +841,12 @@
break;
}

+ if ((*opt_ele != '0') &&(wpt->altitude != unknown_alt) ) {
+ char ele[100];
+ sprintf(ele, "%.1f", wpt->altitude);
+ osm_write_tag("ele", ele);
+ }
+
if (strlen(created_by) !=0) {
gbfprintf(fout, " <tag k='created_by' v='%s",created_by);
if (gpsbabel_time != 0)

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code

Re: Front End

2009-10-13T08:41:32Z

2009/10/13 Verónica Kaufman Acosta <vkaufman@...>

Hi Everyone!

I'm new with gpsbabel. I'm trying to code a java front end for this application but I can't get around with creating new protocols and filters from a GUI. Has anyone try this before??

Look at the existing front ends in the source tree and see how they use -^3 and related flags.

RJL

Re: 1.3.7-beta20091003 usb-ports

2009-10-13T08:37:45Z

On Tue, Oct 13, 2009 at 4:44 AM, <mail@...> wrote:

using the beta-version beta20091003 i have only the opportunity to select between com 1, 2, 3 und 4

Adding device detection for Windows is high on my list and a requirement for leaving beta. If you can't recompiile your own by addnig and entry to deviceNames in gui/serial_win.cpp, just keep watching for new betas or a release.

RJL

Re: Question on real time tracking

2009-10-13T08:36:52Z

Robert Lipe <robertlipe@...> writes:

> On Tue, Oct 13, 2009 at 6:14 AM, Marc <dkm@...> wrote:
>
> it, I read the sensors' value and add theses value in the output. The
> problem I have is that when the GPS looses signal, gpsbabel exits. I
>
>
> It's not supposed to. In fact, that was one of the test criteria for that
> mode. Now different GPSes have been added since my original work and they may
> have different failure states, but in the absence of debug traces, a GPS model,
> connection media, operating system in use, or so on the search area for
> guessing is large.

Thanks for your answer. I can already provide more info, but I'll
investigate exactly what happens by looking more deeply into the code
(which I already did some time ago...).

I'm using a Garmin Vista Cx through the USB on an Ubuntu 9.04 :)

But as I said, I'll gather more info to narrow down my problem.

Thanks,
Marc

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Gpsbabel-code mailing list http://www.gpsbabel.org
Gpsbabel-code@...
https://lists.sourceforge.net/lists/listinfo/gpsbabel-code