legacypac

1. Any cache owner can modify the cache size from the cache page. Simple, no permission required. 2. If you contact the reviewer, and they agree, a reviewer can change the Cache Type - from Multi to Traditional, or Puzzle to Traditional. We will be seeing a bunch of this as former ALR caches listed under Puzzles get converted to Traditionals. Cache Owners can't change the Cache Type themselves. 3. You can't list new Virtuals at gc.com. Changing the page on a muggled cache to make it a "virtual" does not make it so. That is just lazy maintenance and confusing to seekers who expect to find a cache there. Any cache that has been changed into a "virtual" by the CO should be archived ASAP. If the CO really feels the spot deserves a cache they better figure out how to hide one in a sistainable way. Or they can turn the spot into a virtual waypoint to start of a multi.

Looking at this log on the same page, I can see where the farmers could get upset too. Would be nice if cache owner addressed proper access to prevent or reduce further issues with the neighbors. What seems obvious to the placer, might prove to be a problem later. "October 21, 2008 by MBFace I squelched my way up 'cow pat alley' and soon had my hands on the cache before visiting the stones. As I looked back towards the stile by the gate I saw a herd of cows waiting to welcome me back to the field but wondered why they suddenly dispersed - the arrival of three muggles explained all, fortunately by then the cache was back in its hidey hole. TNLN. TFTC"

When logged in, Click on your name up in the top right corner of the page Right side menu: "View My Account Details" Look for "My Account Preferences" down near the bottom Change to Metric.

If you can decal up your car with Security Company magnets, people will actually welcome you snooping around homes, businesses and parking lots etc. Cops never give us any trouble when we have the security decals on. Cache On.

I hunted down the only cache in Kuwait not on a military base. I was sad that I could not get on the base to hunt the cache there (drove to the gates, but did not ask to go in), but not upset that I could not hunt it. I am just happy our troops can get some caching R&R.

Another principle I've seen articulated here by TPTB is that every cache needs an owner. An owner that has not logged in after two years is not paying attention to the cache. (Exceptions may be made for historic cache that have volunteers taking care of them.) Shelter III is a very differant kind of deal. Established caching area. Active owner. Obviously a very tough hide. Not a good example of why we should not clean up the playing field of missing caches with MIA owners in Asia. In Asia 3 DNFs logged over a period of several years is a pretty strong indication that it was not listed right, was never placed, got muggled, or something went very wrong. The reviewers make the calls - A SBA just brings it to the reviewer's attention, the cache owner's attention (if they even get email), and flags it to potential seekers as potentially a problem cache. If you've ever crossed a city by taxi to try and get a find to fill in a new country on the map, only to find the cache has been missing for years, you would appreciate the efforts to clean up the playing field more.

Some of the funniest (and saddest) logs are the "Found it but did not find it type". Read some cache pages and get a good laugh. Stuff like: "Got to the park but the gate was locked - logging it found" "looked for 15 minutes, must be muggled, logging a find". If you need to get the owners permission to figure out if you found it - its not found. If you find a toy under the shopping carts, but no cache, its not a find. "Found it but didn't really find it" just hides the fact the cache might actually be missing, and they cheat the cacher out of a correct count.

No way I know of to assemble a list of DNF's for someone else except look at hundreds of cache pages one by one to see where they might have been. And anyway, around here a lot of people never log DNFs so any list is not going to be complete. If they are your friend, they can use their own account to pull up the DNF list. If they are not your friend, why would you care?

I'm not technical either, but have had good success with logicweave's Cachestats. Pretty simple to use.

Easy. 1. Log in to site 2. Click on your caching name to go to your Profile Page 3. Above your logs you will see "Caches" - click that to filter out the Bugs. 4. Select the type of log you want to see (DNF in this case). There is your list.

OP may not return to forum, so I posted note to the cache page on how to archive. Glad to see the cacher being responsible and not just abandoning the cache.

Sounds like a good candidate to archive to me. Seen a few like that in China. Get placed - bad coords, bad spot, or whatever - and never get found. Reviewer erik88l-r usually gets on top of the cache pages without caches that are just cluttering up the game as soon as he becomes aware of it. The SBA note draws Reviewer attention to the cache. It MAY also draw owner attention to the cache IF they still get emails or still care. It also flags the cache for other seekers that maybe there is a problem with the cache and they better read the logs first. To chowder-heads question: Protocal is be nice and polite when contacting other cachers. You are looking for a favor right? Many cachers are very happy to help you.

As noted above, it seems to me that the order logs display within a day has changed. It is most noticable in on the cache pages, but also shows up on the public profile page funny. I suspect this will mess up which cache is counted as a milestone too in Cachestats (not verified this). I feel the correct way on all lists should be: April 22 Log #6 April 21 Log #5 April 21 Log #4 April 20 Log #3 April 20 Log #2 April 20 Log #1 (FTF) April 20 Published Currently the logs read like this for the same cache. April 22 Log #6 April 21 Log #4 April 21 Log #5 April 20 Published April 20 Log #1 (FTF) April 20 Log #2 April 20 Log #3 I also prefer that my Finds List or on a list of my logs that the logs are based on the order I log (same as the order I visited) Cache 5 Found Cache 4 Found Cache 3 Found Cache 2 Found Cache 1 Found but now if the caches are found on the same day, the site reorders the logs so that each day reads from first to last but the days read from last to first. That might look like this over 3 days: Cache 5 Found (day 3) Cache 3 Found (day 2) Cache 4 Found (day 2) Cache 1 Found (day 1) Cache 2 Found (day 1) The best illistration might be a stack of paper you just keep adding too over time. Next paper goes on top. Forget about sorting by day in reverse order and then stacking each day on top of the last.

China near Macau. Got the taxi driver to follow my direction though he could not speak English, or I speak Chinese. Wandered into someone's (apartment building) back yard and searched under, in, up etc until I realized I had punched in the coords wrong. Then 1.9 Km away found a nice park/shine and made the FTF. http://www.geocaching.com/seek/cache_details.aspx?wp=GC14VJ2 Sarawak - At a great waterfall where I did some swimming http://www.geocaching.com/seek/cache_detai...=y&decrypt= Middle of winter in the dark just inside Minn. in the middle of no where cache wise. Look up "nearest caches" on the blackberry and find one published that day is the closest cache. No one else attempted it for months. http://www.geocaching.com/seek/cache_details.aspx?wp=GC1HFJE And for total amusement check out Free The Bench http://www.geocaching.com/seek/cache_details.aspx?wp=GC1B45F

1. Caches aren't "approved." They are published if they meet the site's listing guidelines. I publish many caches that I do not "approve of." One reason to avoid the word "approved" is to dispel any false sense that the listing service has endorsed the placement. 2. Read the listing guidelines top to bottom and try to find the word "safety" or "safe." You won't. You will see the word "danger" just once -- where the guidelines talk about how muggles perceive our activities as possibly being dangerous. The guidelines do not regulate safety; otherwise, I have a lot of terrain 5 caches to go archive. Thanks for the good points Keystone. I've found a few caches I don't approve of either. There is no way for the site to regulate safety - and yes some caches are dangerous.

49 caching alone (driving myself, hunting myself) but part of a cache machine in Yakama. That was just from midnight on during the actual Cache Machine Day - I scored a bunch of others the evening before. We avoided a lot of micros and parking lot caches too. It was fun, and differant. It helped that Yakima was completing virgin territory for me but it hurt that I had no idea where I was going as I'd never been there before.

I use the WAP all the time on my BB. Works great on the 8700 and my new Curve. I can't get Cacheberry to work - I'm a technopeasent. "Gripe 1 no way to keep signed in. Why? Not everyone has a "dumb" phone. " I stay signed in for a while, but after inactivity the WAP site seems to log you out. Kind of annoying. "2 the only way to look up a cache is by waypoint." No, you can search by coords too. You can't search by cache name if that is what you are wanting. If working in an area I have no downloaded caches on the GPS I do a coord search. If my GPS has the GC# and I'm looking for info or to log, no problem. "3 the find a cache is in decimal coords. So I have to switch my GPSr to decimal for the search and back to min.sec to input a waypoint. Why not have the search in min.sec which is the way it's listed on the cache pages?" I used to do that to => until I read the WAP accepts coords in min.sec too. Saves me a ton of time! Just enter like this 49 11.300 -122 15.800 No need for a degree mark - just a space instead. If you want you can even skip some or all the numbers after the dot (sec) for a general area search. "4 all phones scroll. Can't we have the cache page info on one page instead of three or four?" I wonder that too. I have no issues displaying the www.gc.com site on my 8700 or the curve. It's slow, but sometimes I want to see more logs or what size the cache is or whatever that is not in the WAP site. Also you need to go to the main site to filter out finds.

I get that some caches are placed near dangerous areas and that is ok. A cache in the publicly accessable viewing area near a waterfall makes sense even if part of a normal search circle would put you out of bounds in the danger area. I have a hide near the freeway - searchers obviously should stay behind the fence on the abandoned road. My grandfather was nearly killed when hit by a truck as he walked across a crosswalk. He was being careful too. Add a GPS arrow to follow and a desire to "spot" the cache...

I found a cache that is inside an intersection. http://www.geocaching.com/map/default.aspx...;zm=19&mt=k Is this an acceptable placement? While everything is dangerous to a point, wandering into traffic with your nose in the GPS seems pointless. Also what about caches that have been confirmed missing for more then a year? Are there other examples?

Cache in a new location = another find for me. We had a cache in a series get moved to the next town a 30 min drive away. I was watching waypoint changes, this one came up, and two of us went for it. Our names were in the log book already, we just signed again. Who cares that they recycled the GC# - it was even a new park to us.

Thanks for all of the advice. I sent the newbie an Email last night and kindly explained that the caches had not been destroyed and were still tucked away in there hiding places. I also told the newbie that they were not your ordinary run of the mill cache containers and were made to blend into the environment. This highly motivated newbie then returned today to find all 3 caches. I had not yet logged an Owner Maintenance but for some odd reason though, all 3 of my needs maintenance logs have been removed. Maybe the local reviewer had removed them after seeing 3 find logs by the same cacher. All is well with the force! I'm guessing the newbie deleted his own Needs Maintenance logs. Our reviewer does not even pay attention to most SBA's. Are there reviewers that actually get on top of NM logs? They don't even get the NM logs so they would have to go looking for them. If I check one of my caches I always post a Owner Maintenace log just to say I was there. That clears the little NM attribute. You can also modify it under the attributes page if you want.

Thanks for all of the advice. I sent the newbie an Email last night and kindly explained that the caches had not been destroyed and were still tucked away in there hiding places. I also told the newbie that they were not your ordinary run of the mill cache containers and were made to blend into the environment. This highly motivated newbie then returned today to find all 3 caches. I had not yet logged an Owner Maintenance but for some odd reason though, all 3 of my needs maintenance logs have been removed. Maybe the local reviewer had removed them after seeing 3 find logs by the same cacher. All is well with the force! I'm guessing the newbie deleted his own Needs Maintenance logs. Our reviewer does not even pay attention to most SBA's. Are there reviewers that actually get on top of NM logs? They don't even get the NM logs so they would have to go looking for them. If I check one of my caches I always post a Owner Maintenace log just to say I was there. That clears the little NM attribute. You can also modify it under the attributes page if you want.

I'm closing in on 1700 finds and I'm happy if I find 6 out of 9 attempted. We all can't find some caches - a lot of people just don't admit it. I usually look until I get bored too.

I've seen lots of busted/disassembled sprinkler heads with no cache in the area. Don't assume its the cachers. My sprinkler head hide is no where near a real sprinkler system so it should be ok. Hiding a fake sprinker in the real sprinklers is asking for trouble.

I think your issue involves people giving out coords to others before they are public on the website. That happens, but it is like letting some runners start today's race yesterday then declaring them the winner. For some reason now the found logs show up after the publish log does if they are on the same day. That might be part of the issue. In one case I planted a cache way out on a logging road. Then I gave the two other teams (who had been running jeeps through a stream not looking at my hiding activities) the coords. They found the cache, confirmed my coords, signed the log but did not claim "FTF" as they had an early start. They then logged the finds after it was published. I have no issue with these finds as they are legit - just pre-publish. I've actually found 3 unpublished caches. One was part of a series. Finding the published caches got us the info for the unpublished one. Another pre-publish find was because we were looking for a spot to hide and we found a pre-published cache where we were thinking of putting one. The last had been out a long time but likely never was published because it was too close to another multi-cache. The hider never retreived it. FTFs are fun to count - for your own benefit and enjoyment. Otherwise who cares!