Jump to content

justintim1999

+Premium Members
  • Posts

    2427
  • Joined

  • Last visited

Posts posted by justintim1999

  1. Bought an Oregon 450 about 6 months ago and I love it. GPS City has it for $189.95 delivered right to your door. The only down side is to get turn by turn auto navigation you will have to buy garmin city navigator (not included in my unit) for about $80.00. I don't believe that the Oregon 450 will allow voice audio so you won't get the directions audibly spoken to you. I also have a Nuvi 1350 so auto navagation is not a problem for me. For geocaching I love it. Rugged, and easy to use. The battery life is ok.

  2. If the travel bug owner had been absent from geocaching for some time feel free to add a little something to the travel tag and move it along. doesn't seem right not to have something attached to a tag, unless that is what the owner intended.

     

    I came across a tag only traveler some time ago and realized that the item that was attached to it had gone missing. I e-mailed the owner and asked if it was ok to attach something that was similar to the original item to the tag. The travel bug owner was very grateful. It now has more than 10,000 miles and is spreading cheer all around California.

     

    I guess the question is...what would you do? I know one thing. It will bring a smile to whomever is the next to find it.

  3. travel bugs go missing for all sorts of reasons. It's up to the travel bug owner to mark them as missing Also, cache owners can mark travel bugs "missing" if they have been listed as in there caches for an extended period of time.

     

    As a travel bug owner I mark my travelers missing if they show no movement for one year or I'm cretin that it is lost.

     

    As a cache owner I will mark a travel bug missing that is suppose to be in one of my caches but isn't. I usually check up on my caches every three months or so. If a traveler has been listed in the cache since the last visit I will remove it.

     

    As a travel bug/geocoin nut it's important to me to keep cache inventory accurate. We've all been disappointed at not finding a traveler listed in a cache.

  4. Would set a bad precedent. I think the archive and adoption process should be streamlined. Lets get un-maintained caches out and new maintained caches in. Is there a way to view caches that are up for adoption in a specific area? It would be nice to be able to search for adoptable caches by zip code. This way caches could be adopted by people who want to take care of them. At the very least caches would have a heads up on areas that will become available once a caches is officially archived.

  5. In my opinion If you don't have the cache in hand you can't log it as a find.

     

    What was the difficulty and Terran rating on the tree cache? If you didn't actually climb the tree and retrieve the cache you really didn't earn whatever the cache rating was. To some people this would mean very little and for most it would mean even less. The beauty of this game is you can play it any way you want to. For me it's all about retrieving the cache and signing the log.

  6. Don't want to drop it in a cache that's not frequented often or is in bad shape.

    Leave it alone in the cache you found it, log a Discover. At week two, place it back into the container you found it. Or place it into the not frequented one.

     

     

     

    some of my travelers have been in the hands of a cacher for months between when it was picked up and when it was dropped off. It's nice to see that the cacher is still active and my travel bug is still moving even if it's only visiting caches along the way.

    This is the most common reason for Visit logs... the taker is unable to part with it. The taker insisting there's just nocache worthy of placement, cachers insisting that all the Visits are proof that the TB is still moving. If there are at least some decent logs among the Visits, that's something.

     

    The problem is TOs rightly concerned about 500 "took it to" logs over a period of months, and takers that fail to post any human response. And cachers ignoring or poo-pooing the real problems and pronouncing how wonderful that practice is. :ph34r:

    Don't want to leave it alone. I enjoy moving travel bugs. Again, These are legitimate reasons why a cacher would hold on to a travel bug longer that they should. Most are moved along within a week or so.

    I actually had a travel bug owner contact me and asked me to hold on to the TB and cache with it for a while. It was her 9 year old daughters travel bug and she was concerned that it would go missing.

     

    I personally don't care if someone caches with my travel bug for a month or two. It's traveling along picking up miles. I think I release travelers more for the people who find them than I do for myself.

    always exciting when you find a travel bug or geocoin.

    Why did you bother asking "what people think" when you dismiss what people think?

     

    Exactly. Not agreeing is not dismissing.

  7. Don't want to drop it in a cache that's not frequented often or is in bad shape.

    Leave it alone in the cache you found it, log a Discover. At week two, place it back into the container you found it. Or place it into the not frequented one.

     

     

     

    some of my travelers have been in the hands of a cacher for months between when it was picked up and when it was dropped off. It's nice to see that the cacher is still active and my travel bug is still moving even if it's only visiting caches along the way.

    This is the most common reason for Visit logs... the taker is unable to part with it. The taker insisting there's just nocache worthy of placement, cachers insisting that all the Visits are proof that the TB is still moving. If there are at least some decent logs among the Visits, that's something.

     

    The problem is TOs rightly concerned about 500 "took it to" logs over a period of months, and takers that fail to post any human response. And cachers ignoring or poo-pooing the real problems and pronouncing how wonderful that practice is. :ph34r:

    Don't want to leave it alone. I enjoy moving travel bugs. Again, These are legitimate reasons why a cacher would hold on to a travel bug longer that they should. Most are moved along within a week or so.

    I actually had a travel bug owner contact me and asked me to hold on to the TB and cache with it for a while. It was her 9 year old daughters travel bug and she was concerned that it would go missing.

     

    I personally don't care if someone caches with my travel bug for a month or two. It's traveling along picking up miles. I think I release travelers more for the people who find them than I do for myself.

    always exciting when you find a travel bug or geocoin.

  8. Don't want to drop it in a cache that's not frequented often or is in bad shape.

    Leave it alone in the cache you found it, log a Discover. At week two, place it back into the container you found it. Or place it into the not frequented one.

     

    Don't want to leave it alone. I enjoy moving travel bugs. Again, These are legitimate reasons why a cacher would hold on to a travel bug longer that they should. Most are moved along within a week or so.

    I actually had a travel bug owner contact me and asked me to hold on to the TB and cache with it for a while. It was her 9 year old daughters travel bug and she was concerned that it would go missing.

     

    The only time I would put a Travel Bug in a cache that's not frequented often is if I lived close enough to pick it back up if it sat for to long. I Have a TB in a puzzle cache right now that's been sitting for 4 months. The cache has been visited once and that cacher didn't grab it.

     

    some of my travelers have been in the hands of a cacher for months between when it was picked up and when it was dropped off. It's nice to see that the cacher is still active and my travel bug is still moving even if it's only visiting caches along the way.

    This is the most common reason for Visit logs... the taker is unable to part with it. The taker insisting there's just nocache worthy of placement, cachers insisting that all the Visits are proof that the TB is still moving. If there are at least some decent logs among the Visits, that's something.

     

    The problem is TOs rightly concerned about 500 "took it to" logs over a period of months, and takers that fail to post any human response. And cachers ignoring or poo-pooing the real problems and pronouncing how wonderful that practice is. :ph34r:

    I personally don't care if someone caches with my travel bug for a month or two. It's traveling along picking up miles. I think I release travelers more for the people who find them than I do for myself.

    always exciting when you find a travel bug or geocoin.

  9. It's nice to see that the cacher is still active and my travel bug is still moving even if it's only visiting caches along the way.

     

    A vist does not mean the bug is still moving or active. Take a look at this bug TB2EJMR almost 41 pages of visiting and they the figure out that they did not have it.

    I've heard of this happening but I'm sure that this is an exception and not the rule.

  10. I wouldn't say that "visits" are as good as drops. the beauty of a travel bug is that it travels long distances via many different cachers. Everything about a travel bug is random and arbitrary. Dropping it off at one cache instead of another completely changes that travel bugs history. You become part of that history for the time you have it. As far a thinking you can keep a travel bug indefinably because you are logging visits is a stretch. I don't think any experienced cacher thinks that. There are many reasons to hold on to a travel bug for an extended period of time. I've gone weeks and found nothing but micros and nanos. Don't want to drop it in a cache that's not frequented often or is in bad shape. Could be that I'm planing on visiting a cache that's relevant to the travel bugs goal. some of my travelers have been in the hands of a cacher for months between when it was picked up and when it was dropped off. It's nice to see that the cacher is still active and my travel bug is still moving even if it's only visiting caches along the way.

  11. I think we can all agree that travel bugs should not be kept for extended periods of time. I will normally carry a travel bug for a week or two which means 6 or 7 "visited logs" by me. I've seen travel bugs that have 4 or 5 pages of visited logs from one cacher. I personally enjoy seeing all the places my travel bugs have visited. too bad you couldn't set the display preferences for each of your travel bugs to show or not show "visited" logs.

  12. I was always of the opinion that a travel bug should visit as many caches as possible. It seems that there is a camp that subscribes to the idea that visiting logs just clutter up the travel bug page and therefor are a nuance unless the site visited is germane to the travel bug goal. When I log a cache I always select "visited" for each travel bug I have in my inventory. Is this wrong? Lets hear what you think.

  13. I think people simply get frustrated when they do post a "Needs Maintenance or Needs Archived" log and nothing happens. It takes way to long to have a cache archived when it's painfully obvious the owner has abandoned it. Couldn't this process be automated? By automated I mean:

     

    If a needs maintenance log is posted on a cache and an owners maintenance logs hasn't been logged in lets say two weeks the cache is flagged and an automated message is sent to the cache owner "reminding" them of the problem which starts the clock ticking. It may be a simple matter of the cache owner not knowing that they need to post an "Owners maintenance Log" to clear the needs maintenance attribute. After a predetermined amount of notifications the cache is automatically disabled. It stays that way for another predetermined amount of time at which point it's archived and the space opens up for another cacher to hide a new cache.

     

    At least there will be a list of flagged caches that can be reviewed and monitored periodically. and caches that are not being attended to can be put up for adoption or eliminated to open up new areas for cachers that are still dedicated to geocaching.

     

    I think its just fine replacing a log sheet or log book, as is slapping on a piece of duct tape as a quick fix. Replacing a cache is a little trickier. If a cacher notices that a cache has a needs maintenance log attached to it it's a good idea to take the time to check out the logs and see what's going on. Check the cache owners profile, see if they are still active. If not then I think it's ok to replace the cache with something similar if your so inclined. the only reason I replace caches is I can't stand the thought of a new cacher or a child finding there first cache and having it full of water and ruined.

     

    as a cache owner I think you should visit your caches at least twice a year regardless of maintenance logs. If there is a problem with one of your caches you should be able to fix it within a week or two.

     

    I chuckle when I hear of cachers who have 100, 200, 300 hides or more. I wonder how (or if) they are maintaining all those caches in a timely manor. I don't think people realize the commitment involved in being a cache owner.

     

    Couldn't the adoption system be revamped also. Is there an easy way to list and search for caches that can be adopted?

  14. Why couldn't Ground Speak enlist the help of some experienced, trustworthy geocachers to:

     

    Monitor local caches and identify caches that have been abandoned

    verify trackable inventory

    check to see that cache co ordinance are at least close ect.

     

    I already note in my logs trackables that are not in caches.

     

    Many caches I visit have "need maintenance" attributes. many of them are just fine even though the cache owner seems to have abandoned it. Some should be archived or put up for adoption.

     

    Many cachers already post alternate coords in there logs.

     

    The problem is none of this valuable information can be implemented unless your the owner of the cache or traveler.

     

    As for me nothing is more disheartening than finding a cache that is rotting, or expecting to find a traveler only to be disappointed. I wonder how a new cacher feels.

     

    We have Travel Bug Rescue to help verify that travelers are still in caches and to get them moving again. How about taking it a step further.

     

    I'm all for giving cache and trackable owners a chance to manage there own accounts. Many just need someone to help them along the way. But sooner or later the amount of bad information will ruin the game.

  15. Check out this place, "Travel Bug Plaza Hotel & Suites" (GC3JQQ1) It's located near Clearwater, FL. This may be the nicest Travel Bug hotel I've ever seen. Had one of my TB's visit it recently. 864 records posted which I assume is 864 TB's. The cache has 174 favorite points. Amazing.

  16. Strange but looks like an honest mistake. I would give it a little more time. The cacher just logged in on Monday 6/3. If after a few weeks he doesn't respond and he is still actively caching I would just activate the travel bug and release it. If he contacts you at some point you can transfer ownership to him then.

  17. This may sound silly but when I load a cache with my Oregon 450 (which I just purchased) I no longer have the line from my current location to the cache. I did have it at one time but I must have configured something and it disappeared and no matter what I try I can't get it back. Any ideas?

  18. "Also is it right to travel around with a TB and log it as having been to numerous caches before it is actually placed in a cache?"

     

    Yes. When you log a cache you have the option at the bottom of the log to select an action for each travel bug you have in your inventory. You can select "visited" for each travel bugs you did not leave in that particular cache. The "visited" option allows the travel bug to get credit and mileage between each cache you do until it is actually dropped off.

     

    Obviously it's wrong to do this if the person dose not physically have the travel bug in there possession.

×
×
  • Create New...