Jump to content

Aim High!

+Premium Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by Aim High!

  1. Aim High!

    Travel Bugs

    Now I like that idea. Expand the TB section a bit to give some helpful tips on how to keep your travel bug moving and not go MIA so quickly. I know Snoogans (don't misinterpret this incorrectly--it's not a slam but any means) has a topic concerning TB Logevity here on the forums but basically it's wasted space for individuals that are new to geocaching and TB stuff and aren't on the forums. Unless a cacher comes to these forums (honestly) I tend to avoid the national forums because of how nasty they can get. I believe that most new cachers place their first caches and send TBs into the world before they ever log onto these forums. So, it seems more appropriate to beef up the section pertaining to activating their TB to cover some of the ideas that have been offered. AH!
  2. Jeremy, I did read through those posts and some additional posts that pertained to the total mileage but your quote: "The Travel bug distance calculation has changed. There will be a few days before the distance calculations update correctly so please be patient." doesn't address the mileage from cache to cache... If you meant by this statement that the mileage moved from cache to cache would magically appear at a later date then that answers the question; however, to redirect us back to that quote still didn't answer the question. So, I take it by your post that all is well in "total mileage" as well as seeing the mileage the TB moved from cache to cache? AH!
  3. I agree--I started a new thread on this exact topic and have asked the moderator to delete that thread so as to not duplicate the topic. Here's my post: I noticed that with the latest updates to TBs that the mileage that the bug moves from cache to cache has been eliminated. I would really like to see this feature put back on to the bug's page. I for one track the mileage that I personally move TBs and can tell you exactly how many miles I've moved all the TBs I've found. There's others--a great example is MaxB on the River that tracks a lot of information on all 4,000+ TBs they've moved and can definitively state they've moved these bugs over 4 million miles. Besides our own personal interests in tracking, it's fun to see the really good moves cachers have made on different TBs. All we see now is that it went from AZ to NM (example)--so did that TB move 10 miles just across the border or did it move a few hundred miles. I know I'd really like to have that feature back. Thoughts everyone? Aim High!
  4. Moderator--please delete this new topic. I found the same one below. Thanks...AH!
  5. Started this discussion on the TB Forum but looks like it needs to happen here. Here's the post: I noticed that with the latest updates to TBs that the mileage that the bug moves from cache to cache has been eliminated. I would really like to see this feature put back on to the bug's page. I for one track the mileage that I personally move TBs and can tell you exactly how many miles I've moved all the TBs I've found. There's others--a great example is MaxB on the River that tracks a lot of information on all 4,000+ TBs they've moved and can definitively state they've moved these bugs over 4 million miles. Besides our own personal interests in tracking, it's fun to see the really good moves cachers have made on different TBs. All we see now is that it went from AZ to NM (example)--so did that TB move 10 miles just across the border or did it move a few hundred miles. I know I'd really like to have that feature back. Thoughts everyone? Aim High!
  6. It's not a matter of "losing mileage". It appears that with the update that the total mileage at the top of the logs is all that shows...not the mileage to the right of logs that showed what the mileage was for one move. I don't see where this issue has been discussed in a previous thread. I read Jeremy's post about the total mileage but the individual move mileage hasn't been addressed as far as I can see...AH!
  7. I noticed that with the latest updates to TBs that the mileage that the bug moves from cache to cache has been eliminated. I would really like to see this feature put back on to the bug's page. I for one track the mileage that I personally move TBs and can tell you exactly how many miles I've moved all the TBs I've found. There's others--a great example is MaxB on the River that tracks a lot of information on all 4,000+ TBs they've moved and can definitively state they've moved these bugs over 4 million miles. Besides our own personal interests in tracking, it's fun to see the really good moves cachers have made on different TBs. All we see now is that it went from AZ to NM (example)--so did that TB move 10 miles just across the border or did it move a few hundred miles. I know I'd really like to have that feature back. Thoughts everyone? Aim High!
  8. Just one other thought on how to get the serial number. Just email the bug owner and explain it and ask for them to send you the serial number. Occassionally this won't work because the bug owner is inactive or they don't know the serial number (I've actually had bug owners email me for their serial number). So, another way is to look down through the log entries and you might notice that one of the more buggier cachers like MaxB on the River may have moved the bug. I know that MaxB has the serial numbers for every TB they have moved--over 4,000 now! I also have an excel spreadsheet where I track name, serial number, cache retrieved from, date, cache placed in, date, and mileage moved--I know, pretty anal uh! But, we all get our kicks in different ways. Hope this helps...Aim High!
  9. Aim High!

    Travel Bugs

    I really don't believe Groundspeak needs to do anything additional in educating new members since I truly believe that new members are so overwhelmed by how to work their new GPS, finding caches, etc. that it would all go in one ear and out the other anyway. Not to be offensive to new cachers but we've all been there and know what it's like. I truly believe that the education of potential TB movers lies directly with the TB owner. If a TB is released without anything attached to it explaining what it is and what its goal is (there's many examples of how to do this), then you may expect your TB to go MIA earlier than one with detailed instructions attached. Another thing that I refer to is the proper "nurturing" by the owner of his/her TBs. I try my hardest to thank each cacher that picks up my bug and move it. This is really a good way to help cachers know that you're watching and appreciate their efforts. Then one more thing...We all watch a variety of caches and TBs for a variety of reasons and when we see a cache log entry stating that a cacher picked up the TB and then the TB never comes off the cache page, it's a good bet that that person just picked up the bug thinking that it was SWAG. I have emailed cachers (BTW--not even my bug) that I believe have the bug, welcome them to geocaching and then explain to them about the TB and in every case I have done this the person has said thanks I didn't know that. Lastly, unfortunately there will be those that steal TBs, coins for whatever reason and that is upsetting. That's my take on this particular subject--bottom line: the TB owner needs to take more responsibility for their TB through the whole process. Aim High!
  10. I already know what I believe True Mileage to be but the question was for jrnana specifically since they brought the term up.
  11. I personally have had upwards of 30 to 40 TBs in my possession at one time and for myself, I'm so anal about how I handle TBs, it's no big deal for me. As a matter of fact, I maintain an excel spreadsheet on every TB bug I've moved to include serial number, date picked up and where, date placed and where, and finally the mileage moved. I guess we have our own pet peeves in caching but as long as you're truly working earnestly to help these bugs move, not a problem. However, I can see where other cachers might have a problem because they're not organized. Recently, we added a bulletin board on our states's Forum to help facilitate moving TBs. Check out it Cacher's Traveling Itinerary Bulletin Board I place 5 TBs with a cacher headed to the midwest because I could see their Travel Plans. I also had 30 TBs dropped in a local cache for me to pickup--I've actually begun looking at myself as a Travel Bug Brokerage House. I sat at the computer that night logging in all the bugs and divided 18 TBs into 2 piles for separate cachers going on a road trip and one flying to Chicago. I've made a couple of trips to Flordia and have hoarded over 20 TBs both times and with some of the bugs had held them for 3 months before traveling. Of course I let the owner know my travel plans and let it up to them whether they wanted me to hold it and place it immediately. In every case, the bug owner wanted me to hold on to it because they knew that I was almost meeting the bugs goal on that one move. So, bottom line--if you're paying attention to what you're doing, there's not a problem with hoarding bugs. AH!
  12. Can you please define for us what you mean by "true mileage"? If I'm on a road trip say from UT all the way down to FL, I've never felt "true mileage" for a TB was ever from, for example, Point A in UT to Point B in FL because that's as the bird flies. Like someone else mentioned, if it helps to drop/retrieve the TB along a road trip and take pics along the way, I truly believe that's more represenatative of "true mileage" and the owner really gets a truer picture of where his bug has been. So, what's your definition of "true mileage"--straight line from A to B? AH!
  13. One of our cachers found the following link Jeep Promo at which many of us have registered to receive these notifications but doesn't appear to be functioning. Groundspeak: What's the status on fixing this problem or have they just eliminated this feature? AH!
  14. Happy to report we're moving the White Jeeps throughout UT and into WY and many were placed today and are on the move. They are very nice!! So, what's up with the notification of a White Jeep being placed within 50 miles of the specified zip code? Definitely isn't working at this point. AH!
  15. I can't remember if I've logged a bug in/out of a Virtual but I see absolutely no problem with doing that. One of the biggest problems I see with many cachers that pick up bugs is that they don't take many pics of the bugs they're moving--I realize that everyone doesn't have the means to do that. But, I think for the most part that cachers don't take pics because it takes additional time. And, most of the bug owners would like to see pics of their bugs at different locations. So, actually if you're on a road trip with the bug and decide to log it in a virtual, so what. Especially if the cacher takes a pic of that bug at that location. I honestly believe there doesn't need to be a ruling on this issue. I also believe that if you're moving a bug along a route and that includes noting and possibly taking a pic of where the bug has been is more showing the "true" mileage of the bug. And, that would be for logging the bug in/out of of a traditional cache for the "true" mileage and the overall experience of the bug. My .02cents worth...AH!
  16. It's actually a blast being in the outdoors during the snowy months of winter. Check out a recent geocaching event we had in Utah that involved snow shoeing and X-Country Skiing. We had a a couple of metal detectors with us also. We had 21 geocachers participate in this event that lasted all day--incredible time. http://www.geocaching.com/seek/cache_detai...7-C7744CBFDD36} http://www.geocaching.com/seek/cache_detai...f2-a31abd316f63 http://www.geocaching.com/seek/cache_detai...1d-993398c66c82 http://www.geocaching.com/seek/cache_detai...c4-c978e70f497d Besides the event cache, we only found one of the three caches that were attempted. Even with the metal detectors, was difficult to locate the ammo boxes below 6-8 ft of snow! Cache on!
  17. Appears to be a problem with the geocaching site not automatically emailing users when their caches have been found and also not receiving notifications when the caches on the watch list are found. Anyone else have the same problem? I'm not having a problem with my email service at all. I'm receiving everything else, just not what I normally receive from geocaching. Aim High!
  18. I personally believe it's great that cachers go back to caches they have previously logged. I've found that the cachers that do this know what's going on with the travel bug and ensure that it's logged properly. I also believe that if the cacher is going to get the bug that they should always leave something in the cache--regardless if they've been to the cache or not. Aim High!
×
×
  • Create New...