Jump to content

Path Pacer

+Premium Members
  • Posts

    241
  • Joined

  • Last visited

Posts posted by Path Pacer

  1. Is anyone else finding the map page, with all the geocache icons for a given location, is not working? My page basically opens but then no map or icons appear. Also, the filters on the left side are not working and the green bar to remove the filter section, doesn't work.

    I've been having trouble selecting caches from the map. You roll the mouse over, but the name doesn't pop up. (Chrome)

  2. On a recent cross country trip I passed through a very cache popular area. I was surprised to see that the previous finders had bought new cache containers, pre-stamped logs, and loaded the caches. They just picked up the existing caches and put down their new ones. They were the only names in the logs and all the caches were the same yellow/orange pill bottles that stuck out to be seen by anyone driving along the road. Not a fan. But again, not for me to judge, just observe....

    If you were on a power trail that is acceptable behaviour.

     

    People can do this all they want on a power trail. I just don't want them trying to tell me that they were geocaching.

    That seems to be the gist of it. I'm not sure what to call power trails, but they aren't traditional geocaching. Some weird hybrid, I guess. Still, we have event caches and virtual caches and webcam caches, so not all caching is "find cache, sign log, return." Perhaps they should have their own category, like other non-traditional caches?

  3. I generally only look at logs as a last resort if I can't find the cache. I might browse them hoping someone left an additional clue to help me out. If you don't want spoilers, don't look at logs.

     

    That said, it seems entirely appropriate to me to ask the logger to modify his comments so they aren't too blatant. It's one thing to say, "It's not in the sprinkler heads," and another to say, "It's inside the gnome by the gate."

  4. Perhaps it would be helpful to require new account holders (on any platform) to pass a short quiz before getting access to the geocache map. We could ensure they know not to keep trackables, not to take anything from a cache without giving something back, not to move or take the cache, what not to put in a cache, how to log, etc. It might cut down on some of the aggravation caused by people who don't seem to know the basic rules.

  5. Sometimes it's just ignorance. I don't usually revisit caches, but occasionally it happens when I need to drop off a TB or on a new geotour that incorporates caches I've already found. Since I needed to log that I'd been there, I used "found it" without understanding I should have used "write note." Once I learned of my mistake, I went back and corrected the logs, but they would still be there if I'd never found out. (Lost eight "finds" for that!)

  6. I'm not aware of a single cache that has the poisonous plants attribute set due to a possible encounter with stinging nettles. They are just nearly everywhere.

    That depends greatly on your area. I grew up in southern England where they are positively monstrous and literally everywhere. I also grew up in Virginia where I never saw them. I had assumed we didn't have them in the US, until I did a cache here in Colorado the other day and was shocked to see a couple growing nearby.

     

    When I mentioned this to some friends, all of them said, "What are stinging nettles?" If you took your little kid to that cache and it came home with stinging welts on its arm, you wouldn't be happy if you'd walked in blind with no warning.

  7. I disagree with #6. If there is a problem with the cache, the owner and those looking for it need to know. I've run into a few caches that were some distance from their published coords (over 200' in one case). I've also done a couple near poison ivy and stinging nettles that should have the "poisonous plants" attribute.

  8. I've left a new geocoin before, but I've also just picked out something nice, like a penknife or one of those space pens. I usually spend $10-20, although two of my caches didn't have any FTF prize. I felt like I gypped the first finders.

  9. Another approach would be to present an alert for multiple Find logs ("You've already logged a Find on this cache; are you sure?")

    I like that idea. It would have helped me out earlier. I just assumed the site wouldn't count more than one find for a given cache, but I was wrong.

  10. There are a few cases where it is acceptable (and even encouraged) to post more than one Find log to a given cache listing. For example:

    • grandfathered traveling caches, where you can log another Find as long as someone else has rehidden the cache since the last time you found and rehid it.
    • some event caches in areas where the custom is to log the event cache multiple times to reflect the temporary event caches you found during the event.
    • some caches that have been relocated/upgraded, where the owner encourages people who found the previous version to search for the new version, and to post another Find log if they find the new version too.

    Perhaps we could have an "enable multiple found logs" option on caches? Then the owners could make it possible for those caches where it's acceptable, but the ones who don't know any better won't be able to mess themselves up.

     

    Just a thought anyway.

  11. Not a glitch- you originally off it on one day, and whatever else you do, it was still logged that day. Now you can change the date - I've never done it after I logged it, but I think it's an option when you edit the log.

    I did change the date, but the website wouldn't move it -- at first. It took a while, but apparently some internal check system kicked in and put it in the right place.

  12. Disregard. It sorted itself out.

     

    But, since we're talking about website logging glitches, I just changed a bunch of my duplicate "finds" into "write notes." I didn't realize the website would count another find on the same cache. Can we fix that? I imagine a lot of people just don't know and log a "found it" when they revisit a cache, which is what I was doing when I dropped off a travel bug or had to revisit a cache for a new geotour. I just didn't know what it was doing.

×
×
  • Create New...