Jump to content

BoMS

+Premium Members
  • Posts

    64
  • Joined

  • Last visited

Posts posted by BoMS

  1. I would like to be able to select which language the app uses. I'm Danish, but I prefer my geocaching related programs to be in the English language. The app used to be in English, but after an update it was suddenly in (poor) Danish. This is of some annoyance to me, and I would like to be able to change the language back to English. But it seems there's no way to do this, except changing my phone's language to English. And I'm not interested in doing that.

     

    Can a language option please be added?

    Thanks

     

    Related topic: http://forums.Groundspeak.com/GC/index.php?showtopic=304200&st=0&p=5155223

  2. I've never seen any language option either, and the website states "The Android Application is currently available in English." ...although it maybe out of date.

     

    Did you download it from the Danish Android Market?

    Thanks. Now I know I'm not blind :)

     

    I wasn't even aware that there's a Danish Android Market. But checking now I notice that the menus etc. are in Danish. But the fact is: the app used to be in English and now it's in Danish. No warning and no option to switch back to English that I can see.

     

    Is there somewhere I can ask Groundspeak, how to switch language in the app?

  3. I use Groundspeak's geocaching app on my Android phone. After an update the language in the app has been changed to Danish. I would really like to change the language back to English, but I can't find anywhere to select the language for the app. Am I blind? Or does the app automatically follow the language settings for my phone?

     

    I appreciate any help I can get on this.

     

    Thanks

  4. it may take a cacher several days or longer to get around to logging their finds (and trackables)

    Lazy! I do it right from the spot on my phone! I assumed everybody would log at least later the same day, but I guess it can take a few weeks for folks who are traveling without a computer. I have no idea why anyone would be willing to go weeks without a computer... are these Amish geocachers or what?

    I guess I'm lazy then... :blink:

    I don't have internet access on my phone and often on a holiday to another country we don't have internet connection for 2 weeks because it's just too expensive.

    If that makes me lazy - so be it!

  5. I can understand, I've always loved the outdoors, and to explore and see things in person, but I've never had the drive to go camping just to camp, or go hiking out in the wilderness just to hike, or get a boat, just to boat. This gives me a reason or a purpose to go out in the woods to hike or boat or even 4 wheel on approved trails, doing it just for the fun in doing those things was never enough for me, now I have a reason. Is that weird, or is that the case for alot of cachers?

    That's exactly how I feel :blink:

  6. Reviewers are unpaid volunteers who do the reviewing in their spare time. They can't possibly go find every new cache they are asked to publish and they are not required to. It's your responsibility as a cache hider to make sure it's a good location. The reviewers are willing to help, so try communicating with them in a positive way. Explain the situation to your reviewer openly and politely and listen to what they say.

     

    About the reviewer not answering promptly: The reviewer might be busy at the moment, did you consider that? Maybe - just maybe - your listing isn't the most important thing in the world at the moment. And have you checked your cache listing to see if a reviewer note has been posted? The reply from the reviewer might have been been waiting for you all along.

  7. I would not mark a traveler as missing from my cache unless I personally verified that it was gone.

    I would only mark a trackable as missing from our cache if

    1) we personally verified that it was no longer in the cache and

    2) no recent finder has written in the log book that they have retrieved the trackable (gotta give people a chance to log online) and

    3) none of the cache finders between the time of the trackable drop and the present has the trackable in their possession (I would email everyone and ask)

     

    The same goes for our own trackables but I would rely on information from the CO of the last known location for 1) & 2).

     

    \Mette

  8. In Denmark it's traditional to place a First Finder Certificate in new caches. Some are very creative and some are just a handwritten note with "Congratulations - you were first to find GCxxxxx cache name" or something like that. Most FFCs we have seen has been been made on a computer, printed and laminated. It's nice to have something extra to remember a first find by.

     

    Also many hiders put the name of the FTF on the cache page afterwards.

     

    I really like the naming of the cache idea and we might try it out someday.

     

    \Mette

  9. Here's how I visualize it though. Gen 1 and Gen 2 would have to be intrinsically separate thus separation guideline would not apply. It could be that once you log in here to find geocaches you choose Gen1 or Gen2 caches and that's all that comes up on your screen. Accidental finds would certainly happen BUT perhaps could be largely avoided by A) incorporating a .01 ( = about 50 feet or 75// 80/90???) ) or some such separation limit into the Gen2 cache placement program only from Gen1 caches.

    For me this would have exactly the same effect as if Groundspeak changed the proximity guideline to .01 miles (or whatever). I wouldn't go on a caching trip to a specific area without checking for all caches there. It wouldn't matter to me if they were Gen1 or Gen2. The separation between the two would only serve to make my prep work a little more time consuming*. There are so many places I haven't seen yet so I prioritize going somewhere new on each trip and thus rarely come back to an area I already visited. And if I'm taking a walk in that area anyway I'll do my best to find all the caches hidden there. Not to have a huge find count, but just because they are there waiting to be found.

     

    I think the current proximity guideline is fine as it is - it wouldn't be fun if you couldn't go anywhere without tripping over a cache. Then we could really start talking about geolittering. I think (like some of the other posters) that an effort to clear away the neglected caches will serve geocaching much better.

     

    * Now that I think about it, it probably wouldn't even be more time consuming for me personally.

     

    \Mette

  10. Teglgårdsparken hidden on 02/25/2009. Archived on 05/03/2010 because we moved too far away to do maintenance. It was a small multi in a park (old insane asylum ground) just across the street from our old apartment. We were sad to archive it, but we decided it was better than to adopt it out. We would rather open up the space for some new caches - which unfortunately hasn't happened. The place really deserves a cache.

     

    \Mette

  11. After 20 days this reply was posted on the feedback site:

    Status: declined

     

    Hi BoMS,

    Thanks for writing to us. The Web developers and the community relations team are monitoring this feedback site. Some things take time, like the non-US dates feedback suggestion, but please trust us that we truly are considering it when we mark it "under review".

     

    I'm "declining" this to return all of your votes, but never hesitate to post something here or to write in to contact@geocaching.com

    sara_k Admin

  12. We're not new anymore, but we have gotten some friends into caching. The problems they have encountered besides how to use the GPS is learning the difference between the cache types. Looking for a cache at the parking coordinates of a multi or at the fake coordinates for a mystery for instance. Often it seems that the D/T rating and the size of the cache goes unnoticed by a new cacher, so when at GZ (or trying to get there) they have no idea what they are looking for.

     

    So for a complete newbie I think emphasis should be on cache type, waypoints, D/T, size, how to follow the arrow and GPS accuracy. Logging, trading and trackables would also be good subjects.

  13. Whatever you decide I think it would be a good idea to explain how you rated it in the cache description. Something like "The D/T rating of this cache is based on having to find all the other 20 caches in the series" or "The D/T rating of this cache is based only on the effort needed once you have the correct coordinates".

     

    I can see it both ways too and since there's no rules or guidelines to help decide and interpret the D/T for a cache like this, explaining how you did it will clear away any misunderstandings before they happen.

     

    \Mette

×
×
  • Create New...