Hi, and welcome
On Jan 26, 2008 5:14 PM, Franziska Simmank <franziska.simmank@...> wrote:
> ,
> I like GPSBabel for converting .loc files to .gs files for my Magellan
> Explorist. I noticed that, after converting, the description of the cache
What you're describing is known in this crowd as the alchemy problem.
You're
converting from a format that's not very smart, has multiple fields jammed
together
and such, and trying to convert it into a format that does have unique
fields for
different things.
As you can guess from the name we've given it, it's kind of hard to do this
well in
the general case. :-)
At various times, we've actually done both variations of what describe.
Both were
utlimately changed as not all the world's data is geocaches and people with
waypoints
named "by river" got annoyed when we shortened their names to (gulp) 0
bytes, for example.
The 'nuke_placer' option
http://www.gpsbabel.org/htmldoc-development/fmt_geo.html does exactly what
your first
patch does, only it's optional - it doesn't change input unless you ask for
it.
In general, we strongly discourage our writers from trying to "fix" quirks
of the readers.
Do let me say that if you want to do anything other than the simplest "send
to GPS"
functions that LOC files are a dead end. Pocket Queries from Groundspeak
aren't
free ($3/month, $30/year) but they're a boon to programmatically
manipulating geocache
info.
RJL
|