From: Ron Parker <ron@gw...> - 2004-06-14 17:21:23
Necessity, they say, is the mother of invention.
I uploaded a recent PQ to my GPS on Saturday. Since I used the
default options, the waypoints got the GCIDs for names. I uploaded
the same PQ to my Palm at the same time, in PalmDoc format. The
bookmarks got named based on the cache names. D'oh!
So, I added a new option to PalmDoc: bookmarks_short. I think it
could use a better name, but I couldn't think of one. What it does
is add the GCID (or other shortname) to the start of the bookmark,
so that it looks like 'GC150C:FiveMedls' When combined with
sort,shortname (is that fundamentally different from sort,gcid?) it
makes it much easier to look up the details of the cache that just
popped up on your nearest waypoints search.
Anyway, I committed that change on Saturday and then forgot about
From: Robert Lipe <robertlipe@us...> - 2004-06-14 18:36:27
> Necessity, they say, is the mother of invention.
As the very existence of GPSBabel as well as numerous features in it
were guided by my own geocaching necessities, I understand. :-)
> I uploaded a recent PQ to my GPS on Saturday. Since I used the
> default options, the waypoints got the GCIDs for names. I uploaded
> the same PQ to my Palm at the same time, in PalmDoc format. The
> bookmarks got named based on the cache names. D'oh!
I've had a few people point out that by having the smart naming done at
the point closest to the target device what we really want is a way to
propogate the name back upstream so that those people using multiple
targets can normalize the names and not have different names on each
(OK, nobody that I've run into in the woods near a piece of tupperware
has ever actually described it quite that way, but that's what they
> sort,shortname (is that fundamentally different from sort,gcid?) it
It is. The problem is that geocaching.com IDs are in just about the
least possible useful form for sorting. They aren't padded/aligned
sensibly, they require excessive clock cycles and special cases with
horrible formulas to generate, and the alphanumeric stuff doesn't work
with normal computer sorts.
The options that I could see were to either special case the "oh, this
has a name that starts with GC so let me do base 31 except when it's
base 16" math (which is horribly geocaching.com specific) or just to
modify the parsers to capture the number on the way in (which is still
geocahing specific, but it at least quarrantines it into a corner less
full of denial)
If you don't care about geocaches with lower numbers than 'GCFFF', the
alphanumeric sort will (I think) work well enough.
P.S. http://www.mtgc.org/mtgc_forum/viewtopic.php?t=11 shows one example
of how this might actually be useful...or at least interesting.