Re: [Gpsbabel-misc] Gpsbabel v1.4.1, 1.4.2- Leading quotes in csv, garmin_poi

[Jim D. <jd...@ve...>]

Yes, it (POILoader) does work with gpx, but it seems like most Automotive
and non-geocacher/non-outdoors Pedestrian gps users are terrified of using
gpx to the point of 3 and 4 column "csv" being most popular.
 
Since they can jam an address of sorts into the 4th column with commas
passing through, and just load it up into POILoader, then into their nuvi's,
they're happy. 
 
I'm trying to mod my Excel add-in (that parses gpx into rows, cells so it
isn't so scary and make bulk edits/sorts easier) to run Babel and go
straight to gpx/.gpi, so at least they can make use of the extra
capabilities of a gpx compiled poi even if they don't edit. I can parse the
input in the spreadsheet for them, but I was hoping to use Babel to allow
for a 'quick & dirty' csv to gpx/gpi option without the spreadsheet parsing
adding extra possible error. The add-in has other Garmin poi related
functions like @xx speed parsing/adding/clearing, and geocoding options, or
just using Babel by itself would be the  logical choice- even if it too
parsed the commas.
 
 

Is preservation of a comma possible with a style file, or am I against a
wall due to a basic reader limitation?


The latter.  It sounds like the POI Loader format should not have been
implemented with our xcsv plumbing.

Doesn't POI Loader work with GPX these days?  That should eliminate this
whole issue.

RJL