Re: [Gpsbabel-misc] GPX -> CSV did not work, please crosscheck

[Robert L. <rob...@us...>]

P. Roosen wrote:

> Although the prog does not issue any error message the CSV file produced 
> was empty. Could someone crosscheck on that? I could not retrieve a CSV 

Can you provide the GPX file in question and the precise command issued?

> exported file when communicating directly to a MeriGold, either, so i 
> expect the problem to lie in the CSV part as a GPX download does work 

While I don't use CVS very much, I use magellan on Linux serial several
times a week.

(robertl) rjlinux:/tmp
$ gpsbabel -i magellan -f /dev/ttyS0 -o csv -F /dev/fd/1 | tail
36.36363, -86.86868,
36.84362, -86.88690, Old Bank Robbery
36.14860, -86.81230,
36.05598, -86.90258,
36.05485, -86.91817,
36.16487, -86.77570, Cumberland Cache
36.22583, -87.03617, Creekers Cashe
36.57037, -86.60498, The Tavern
35.87045, -88.02197, Centerville Stop  I-40E
36.05648, -86.90697,



> Another thing: According to my inspection of the CSV exporting source 
> code only lon, lat and description is exported. I'd love to include a 
> datum/time field as well, as this will help, as a good discrimination 

That makes it a new format.   Adding new formats will be made easier
by the stuff Alex is working on.

> stamp, exclude a repeated postprocessing error. I tried to include one 
> by printf()ing the wpt->creation_time after some conversions, but did 
> not achieve any usable results. This might have collided with the 

You probably want some invocation involving gmtime() or localtime().  If
you need help creating custom formats, post a patch for review.

> problem described before, though. But my question is if the CSV part 
> maintainer could please add this by himself, probably as a third export 
> field, as he will know the code definitely better than I do.

Alex's new stuff that's in progress makes this easier.  In the interim,
if it's not an official format you're supporting, just add the output in
your local copy.

RJL