Forums Geocaching in Wisconsin General Cache series

Viewing 15 posts - 1 through 15 (of 41 total)
  • Author
    Posts
  • #1728304

    Time for a discussion. (Why? Well, I could say it’s all about the numbers, but that is just too much ………)

    There are quite a few series of caches being published. Most have long names.

    What’s wrong with long names? Most become unreadable when displayed on Palm and GPS units.

    I like series, but get frustrated with trying to figure out which cache I might be looking at.

    Yes, I know if you stuck to GC # it would not be a problem. But I prefer smart names, as generated in GSAK. And so, therein lies the problem. I’m sure there are other cachers out there doing the same.

    Here are some examples. I’m not picking on anyone in particular……

    For older units, there is a limit of 6 or 8 digits. This results in entries such as….

    buerga – for Buerger Trail – South View
    buergt – for Buerger Trail – Tall Stump

    GSAK assigns a random 6th digit to distinguish between them but it really does not help.

    Or, even on a 60 CSX with longer displays, you can see something like

    Wisconsin Spirit Quest – St J

    ( …. so, it that John, James, Joseph? Oh, John? Which one ………..? )

    Assinging a number to each cache in the series helps.

    So, the Another Walk in the Park series will show up as something like ….

    Anot71
    Another71
    Another Walk 71,
    etc. depending on how many characters show on your GPS.

    But………….

    CacheMate does not work the same. It displays all the characters, and so you get

    Another Walk in the Par
    or
    Wisconsin Spirit Quest – St J

    Hard to tell which one. BTW, there are some 70 Walks. And 49 of those ‘other’ WSQs.

    What is needed is a numbering system which places the number early in the name. That will take care of both GPS and CacheMate displays.

    When I started placing my cemetery caches, I came up with an acroymn and number system which worked out quite well. A bit of thinking it out, and some dumb luck, but it works.

    WCC 106, became
    WSQ 106, which became
    WSQ 106 St Mary, and finally
    WSQ 106 St Mary (Kaukauna).

    They will all display clearly as WSQ106 …………..

    Many of the cache names being considred here do not start with an acroymn. So the number might appear a little awkward at first, but should work out. Here are some examples …………

    71_Another Walk in the Park
    01: Card Shark: Breaking Hearts
    05: Flags of Our Fathers – Isle of Valor
    FOG 10 – St Michael’s Cemetery
    06 – GR8 River Road – Fishin’ on the Big River
    04: Nano – DaVinci Code – Central
    03: Old West Shootouts: Dodge City
    04 – Simpson’s Trivia Puzzle
    02: Villian Series – The Joker
    01: What’s Missing?

    Something to consider.

    Flak jacket on, head down, lights out…………….

    #1908262

    Well Ill pull out the bazooka first, Its been hashed out in the past about our Wisconsin Spirit Quest Caches, They are pattered after the Indiana Spirit Quest caches and sorry but we will not change them, I might consider numbering them, but don’t remember the order the were placed, but now they are not just in Oconto county, we have put out another 20 this year that are in Langlade, Oneida, Forest, and Marinette. We have never had any other complaints about them, If you would set your smart names to unique in GSAK before you put it in you palm and GPS, they will be different.

    Barry of sweetlife

    #1908263

    quote : Wisconsin Spirit Quest – St J

    you got that much into a 60csx?

    #1908264

    Not everybody uses GSAK either. And All the info I need is on my Ipod using Cache Magnet, which puts into 2 lists. GC number and title.

    #1908265

    Our little receiver just kicks all but the first one out when they all start the same.
    TE

    #1908266

    Well Marc you and I have had this discussion before and we did end up putting the numbers after our Shawano County cemetery caches, which does make it easier to sort and find that particular series.

    But ultimately it comes down to the cache-finder’s responsibility to keep track of things in the way he/she sees fit. It’s not the owners’ responsibility to make things easy.

    On the Left Side of the Road...
    #1908267

    @gotta run wrote:

    It’s not the owners’ responsibility to make things easy.

    But it would be nice …………..

    #1908268

    @marc_54140 wrote:

    But it would be nice …………..

    My philosophy is that since the cache owner has already put forth the time, effort, and expense to put out caches and create a series, the least that cache finders can do is put a little effort into keeping track of what they have found. I don’t think that’s too much to ask!

    It also seems to be a bigger concern with the number-hunters, though that’s just my perception.

    On the Left Side of the Road...
    #1908269

    @sweetlife wrote:

    …We have never had any other complaints about them…

    I have a few times from a few cachers that reside in and around Forest County.

    #1908270

    @ToyotaRyan wrote:

    @sweetlife wrote:

    …We have never had any other complaints about them…

    I have a few times from a few cachers that reside in and around Forest County.

    Well then they really should not be seeking these caches if they have complaints about them! Finding caches is not obligatory!

    Honestly, I have no patience for trivial complaints like that. Gripe about lack of owner maintenance or the like, not how owners choose to name their caches.

    On the Left Side of the Road...
    #1908271

    Here is a GSAK macro that I have found to shorten series names automatically. I have found it very useful to make waypoint names more manageable for me.

    Shorten Series Name Macro

    #1908272

    @Team B Squared wrote:

    Here is a GSAK macro that I have found to shorten series names automatically. I have found it very useful to make waypoint names more manageable for me.

    Shorten Series Name Macro

    One warning about this particular macro. Each cache that is modifies is “locked”. This is necessary to prevent future downloads of the cache from changing the name back. The problem with locking a cache in GSAK is that it also prevents anything else from changing, including coordinates, cache description, hint, etc. It will add the new logs, however. I have written my own macro for this purpose, and it suffers from the same limitation.

    And since I am commenting, numbers help a lot, but another way to make this better is to reverse the naming system, as Sloughfoot did on his Tail of the Serpent series. A cache called “The Source – Tail of the Serpent” works much better than a cache called “Tail of the Serpent – The Source”.

    #1908273

    We put the Usort number in front of the smartname before exporting them to the GPS. It makes it much easier to seperate them. We also use the usort number to define our routes.

    #1908274

    What’s a “defined route”? 😈

    #1908275

    Oh yeah, that right, you like to just clean out all the caches on either side of you while you drive down the road.

    The defined route is what had us not driving up the farmers driveway to get to the caches in the park behind his house.

Viewing 15 posts - 1 through 15 (of 41 total)
  • You must be logged in to reply to this topic.