Help creating .gpx file

Thanks for some suggestions. Still no success though.

I made a quick hex viewer, and the .gpx file that I'm creating contains what
I am writing (i.e., 0D+0A, just 0D, or just 0A).

corrupt (or something like that) and won't read it.

I'm not sure if my XML declaration line has the proper encoding. I've
primarily been using ISO-8859-1. When I use UTF-8, I still get the diamonds
at the end of each line.

I have not had much luck finding a Garmin-friendly .gpx file online to
files to gpx, but when fed a multi-line description in the csv file, the
converter either choked or only used the first line.


Any tips?

--
-Brian

Google for "POIConverter Version 3.14" - if you can't find it (having
trouble finding the home page myself), I can email a copy...

I've checked on my copy and it does appear to handle .gpx files and
can cross-convert between pretty much any format you're likely to come
across.

I hadn't tried POI Converter last night, so I tried d/l'd it this AM and
tried it. Nice propgram for converting between a bunch of formats. The
a simple .csv file to convert, but when I used a multi-line name field in
the .csv, POI Converter would not read the file.

Thanks for the suggestion. I'm going to try to find a Garmin .gpx file to
inspect with the hex viewer to see what is used for line breaks in the

--
-Brian

I wonder if the seperate util POIconverter uses to do its' thing has
been updated to allow multi-line CSVs...

Do you have any multi-line csv files you could post ?

I found plenty of .gpx files, but none of them did multi-line descriptions
properly. Actually, only one had multi-line descriptions, and those POIs
had the same little diamond after each line.

It appears that Garmin's MapSource does not allow multi-line descriptions
when creating waypoints. Since .csv file descriptions display properly, I'm
going to attribute this whole "diamond at the end of lines" to a bug in the
POI Loader. I contacted Garmin about this, and they wouldn't give me any
guidance because they thought that I was trying to make 3rd party software
(presumably to compete with MapSource?).

Although the .csv files will display multi-line descriptions without the
diamond, I think that I'm just going to tolerate it for now. The .gpx files
just afford much nicer control over the waypoint details (like symbol,
display type, cleaner proximity control, ...) compared to .csv files.

Only other annoyance that I've found ... I wish that the GPS's Custom POIs
the .gpx file's filename. I just want to have one POI file to maintain, not
one for each POI category.

--
-Brian