new & interesting places for your GPS

GPSBabel & Garmin CSV files

 

>>... we're having a few probs ???
>> here's a couple of lines from the "Diners" CSV file - which in Notepad appear on their single lines
>> without the embedded CR/LF -
>>
>> -94.59577,39.05689,39th Street Mama's,"3906 Waddell St.
>> Kansas City, MO 64111
>> (816) 531-6422"
>> -69.77449,44.22993,A1 Diner,"3 Bridge St.
>> Gardiner ME 04345
>> (207) 582-5586"
>> -82.53071,27.28828,Alpine Steakhouse,"4520 S. Tamiami Trail
>> Sarasota, FL 34231
>> (941) 922-3797"
>> -93.23572,44.98062,Al's Breakfast,"413 14th Ave. S.E.
>> Minneapolis MN 55414
>> (612) 331-9991"
>>
>> and here's the GPSBABEL execution from the GUI,
>> with the generated error.....
>>
>> gpsbabel.exe -p "" -w -i garmin_poi -f "C:\Diners.csv" -o gpx -F
>> "C:\diners.gpx"
>>
>> Invalid latitude 641.183333 in waypoint .
>
> No, there is a 641 in your input -- it is the first 3 digits in the zip code for Kansas City. I had a similar problem with GPSBabel -- it is very finicky with the input fields: I had a couple of extra fields that confused it. Just shorten up your large address fields and try the conversion again.

I suspect that the conversion is not recognizing and processing the 4th field of enclosed ---> "xxxx"

Tried to find the STYLE information,
or see how/what is being used by the "Garmin POI" selection,
but haven't found it as yet..... that's probably the challenge -
how to tell Babel that the 4th field has embedded CR/LF's and is enclosed by "xxx"

Perhaps the comma in the

Perhaps the comma in the address after the Kansas City is causing the problem in spite of the double quotes.

GPSBabel & Garmin CSV files - POI vs Geocache

hmmm - could be -
As an old programmer, it's always the "exceptions" that cause the most coding challenges....

So - if the ["] is not being handled at all, then the 4th comment field might be stripped out, and then any next [,] might indicate a new waypoint and the 641 would be treated as the coord.

Might have to try some experiments with a test file.
----

It would appear that the GPSBabel POI style was created from the Geocaching reqs,
and NOT from the CSV files now found on the web for the Garmin GPS units.... unfortunately, the file is called POI vs probably a more appropriate CACHE.

http://gpsbabel.cvs.sourceforge.net/gpsbabel/gpsbabel/style/...

# gpsbabel XCSV style file
2 #
3 # Format: Garmin POI
4 # Author: Robert Lipe
5 # Date: 10/07/2005
6 # Reference: http://forums.groundspeak.com/GC/index.php?showtopic=110641&...
7 #
8 DESCRIPTION Garmin POI database
9 #
10 #
11 # FILE LAYOUT DEFINITIIONS:
12 #
13 FIELD_DELIMITER COMMA
14 RECORD_DELIMITER NEWLINE
15 BADCHARS COMMA
16 SHORTLEN 24
17 # PROLOGUE Longitude,Latitude,Name, comment
18
19 #
20 # INDIVIDUAL DATA FIELDS, IN ORDER OF APPEARANCE:
21 #
22 IFIELD LON_HUMAN_READABLE, "", "%08.5f"
23 IFIELD LAT_HUMAN_READABLE, "", "%08.5f"
24 IFIELD SHORTNAME, "", "%s"
25 IFIELD DESCRIPTION, "", "%s"
26
27 OFIELD LON_DECIMAL, "", "%08.5f"
28 OFIELD LAT_DECIMAL, "", "%08.5f"
29 OFIELD SHORTNAME, "", "%-.24s"
30 OFIELD GEOCACHE_TYPE, "", " %-.4s", "no_delim_before,optional"
31 OFIELD GEOCACHE_CONTAINER, "", "/%-.4s ", "no_delim_before,optional"
32 OFIELD GEOCACHE_DIFF, "", "(%3.1f", "no_delim_before,optional"
33 OFIELD GEOCACHE_TERR, "", "/%3.1f)", "no_delim_before,optional"
34 OFIELD DESCRIPTION, "", "%-.50s"

Troubles with GPSBabel

Give this page a glance: http://tinyurl.com/353497 It provides a fairly detailed overview of creating custom POI files for the nuvi and some of the limitations inherent in both the various file formats and conversion tools for gps data.

As for your suspicions about GPSBabel,

ps56k wrote:

It would appear that the GPSBabel POI style was created from the Geocaching reqs,
and NOT from the CSV files now found on the web for the Garmin GPS units.... unfortunately, the file is called POI vs probably a more appropriate CACHE.

The page highlights GPSBabel's limitations and suggests, as you do you, that they results from poor parsing/reverse engineering of Garmin's proprietary GPI format for POIs.

linked article wrote:

GPSBabel's GPI support was reverse engineered and can only create simple GPI files. It lacks support for proximity alerts, links to sounds and pictures, and Tour Guide files...

If you're really committed to the idea of improving GPSBabel, the article goes on to mention a conversion tool for the mac called, MAC GARMIN TOOLs. Apparently, it's based on a solid reverse engineering effort and converts various POI file types into the GPI format with ease. More to the point, the developer is willing to share his notes on the project if your willing to follow a few requirements.

Cheers.

--
Trucker Phil www.TractorGeek.com

sponsored links