GunniGirl

I have a Verizon LG enV2 with Verizon's Mobile Web. I am able to access cache pages through the Geocaching WAP site and http://coord.info with it. Can also go directly to http://geocaching.com, but I have not found a way to display the cache descriptions on my phone from any of these sites. Descriptions display on my computer but not my phone. I don't think my phone uses Windows Mobile, so apparently GeoScout will not work on it. Has anyone found a way to view descriptions on this phone?

Rain, Snow, Sleet, Hail are for the postman. We cachers also deal with floods, fires, ticks, chiggars, poison plans and snakes. A little flooding is nothing more than part of the challenge. Those not equipped will turn around and go home. Those equipped will find the cache. The cache is probably fine. I agree with you, but I think they need to be warned that it's wet now, although that isn't usually the case. This is a tourist area, and people coming from out of town without understanding this year's unusually high spring-runoff flooding are thinking I put a cache in a permanently wet place without saying so. Hence the note on the cache page.

Fixed. Either action works with the scenario as stated. A scenario not mentioned: I would venture to say whatever barriers the local authorities put to keep people from entering the area would trump a simple note and a temporary disablement would be in order. Thanks for the url fix. The barriers have been removed. Area is accessible but wet. I'm thinking I'll give it three weeks as is, then reconsider temporarily disabling.

One of my caches (Little Gunni #8; inserting link did not work) is high and dry in an area that is temporarily covered with shallow water due to minor river flooding. The cache could be reached with appropriate footwear but is best avoided until the area dries. I have noted this in red on the cache page. Question is, should I temporarily disable the cache to keep it out of pocket queries, etc., or just let it ride? I am guessing it will not be dry for about three weeks.

Wow! I know a couple of Kansas Geocachers who are going to love this!

I have temporarily disabled a vanished cache which I own. My intent was to replace it, but I unexpectedly had to leave town due to a family medical emergency. I will be away for a month. I would prefer to replace the cache and keep the continuity rather than permanently archive it and start over with a new cache when I am able. Is five weeks (the cache has already been down for a week) too long for a temporary disable?

Is the mileage feature on the TB pages broken? My friend owns this bug: TB11NKR, and its mileage is not appearing.

I sure wish the "reverting to Mapquest" topic would get pinned! As has been stated a number of times in various places, all you have to do to see the Mapquest map is click "Make this page print-friendly" on any cache page.

Attention, everybody: When you click "make this page printer friendly" on a cache page, voila, the old map!

Any chance of adding a "Make this page printer friendly" option to the category details page? When visiting a site with the idea of making it a waymark, it would be nice to have a printout of the category listing requirements along. Specifially, I am thinking of creating a waymark of a site for the Guinness World Records category.

No thanks. With the number of micros out there, it may be 20 finds in the future before I'm able to drop a bug I've picked up. I really don't want pointless nag messages popping up every time I post a log. Besides, there's already the drop-down list that only appears if your have something in your inventory, which you have to scroll past to get to the Submit button. Isn't that more than enough of a reminder? Sorry, Prime - I think you're missing it. This has NOTHING to do with a nag for bugs already in YOUR inventory. So this doesn't involve micros. If you have a cache in your inventory, and the cache has nothing in its inventory, this feature request will not affect you. This request is that if there is a cache that already has bugs in the cache's inventory, when you log the cache, it says "There were three Travel Bugs in the cache. Did you pick any up?" and then it gives you the list again. Obviously the newbs aren't seeing the list and figuring it out. This might help them, or prompt people that might otherwise forget. Not a bad idea. I thinks it's a great idea. Sounds like it would solve the problem of people not logging TBs. There are a lot of instances where a cacher picking up a bug merely mentions in his/her online log that they picked it up, thinking that's all it takes, never actually going through the TB logging process.

As I read the comments about the new Google maps, I see a lot of people are wondering how to access the old maps for printing or pasting into a PDF. For now, the old map appears and can be used as it always has if you go to the "Make this page printer friendly" view. Yay! I, for one, hope this is always the case. I also think it might be nice if this topic were to be pinned for awhile to provide a quick answer to a common dilemma.

This is also my caching technique. Try going to the "Make this page printer-friendly" screen. For now, the old method still works there.

I hope so, too. I cache in a lot of remote mountain areas. The Google maps for these areas have nice squiggly lines where the Forest Service and other little roads are but do not identify the roads. How helpful is this: Also, a person cannot right click and print the Google map. For those of us still using paper, printing a Mapquest map on the back of the cache sheet is extremely useful. On the other hand, there are features I like on the Google maps, such as being able to drag the Google map to view and look up other caches in the area. I'd appreciate having continued access to both map systems.

Are you sure it wasn't Shiprock in New Mexico? That towers about 2000 feet above its surroundings. It is about twice as far south of Grand Junction as you estimated, however.

That looks like a fine policy example for other park managing entities to adopt. Bless Florida!

As I interpret the OP, the bug wasn't taken; its tags were taken. A cacher who doesn't log would probably not be the culprit. I think muggled caches happen to almost all of us at some point. Don't let it ruin your fun. Relocate the cache and try again. (Trouble is, if someone has a GPSr and is on a quest for free TB tags, they will keep at it.)

It is. Stolen Tb's Oh goody, I got to markwell something!

Me, too. I wish everyone would! It's a pain to keep restoring them to your inventory when they are grabbed from you. Just when you re-log them, thinking enough time has elapsed, someone else pops in with the catch and release.

I should add that I also dropped my new bug into the cache so late that it didn't make the bug list handout at all, although some others with no number were at least listed by name. I guess that explains my good fortune that the only person who has logged MY bug is the person who took it. Others catching and releasing my bug wouldn't be as much of a pain as people grabbing and dropping the bugs I physically have in my possession, though.

Just airing a complaint... I recently physically retrieved and took home three travel bugs from an event cache. Naively, I logged them that evening. They were grabbed from me right away, then dropped back into the event cache for a succession of grab and drops. Sadder and wiser, I waited four days, until there had been no activity on the bugs for three days. Then I deleted my original logs (to keep my bug count accurate) and relogged the bugs. Within an hour, ZAP! Grabbed from me again to be logged and dropped back into the cache. Now I must "retrieve" the bugs a third time. This practice is becoming quite an art. Shortly after I dropped my own newly activated TB into the event cache, I was contacted by a person who was compiling a list of TBs and their tag numbers to hand out at the event to aid with the grab and drop. I chose not to provide my tag number. It doesn't matter to me how people want to count their travel bugs, but shouldn't there be some sort of etiquette regarding how long after the event this is done before the people who actually HAVE the bugs are safe to log them?

While caching... nothing out of the ordinary so far. Once while Jeeping... nuclear waste dump - behind a hill within five miles of my home!

Go to this cache, select "view all the logs on one page," and scroll down to the log for November 28, 2002.

So did you enter your adventure in the essay contest?

Did what you said, with the addition of grabbing it from its present location after deleting my drop log, and it worked. Mileage and map now correct. Thanks!