SeventhSon

It only sets it to found automatically if you use the "Go to" feature. I am referring to the GPSMap60CSx but others probably work in a similar way. I use the 76csx and use goto, but it won't automatically switch it to found. I have to hit the page button and mark it as found, then it asks if I want to quit or find next. I like the way it is set up, except I'm still looking for the time stamp. Briansnat, thanks for the waypoint name change idea. Edit to delete dumb question.

Thanks. I never looked at the calendar, but mine only shows the caches found and points marked on the date, but no time is listed.

I have the 76csx and can mark them as found. I didn't realize it marked the time/date. How do I see this?

I would like that information also

I am from Beloit, but live in Salina now. Still get home now and then. You can contact me thru the site and let me know what you're looking for.

You have mail from DubyaDee Trade made. Thanks

1. Participating 07/08/07 2. Received Name 07/14/07 3. Mission Complete 07/30/07 4. Package Received! 08/02/07 This was also my first mission. Wow! What a great package. Thanks lindsychris!!! Full of really great stuff

I'm gonna agree with the Sand Dollar. I like it. I'd trade one of my Gear Coins for one.

Since you mentioned the ball of twine, I can't pass up the opportunity to mention this cache.

Interesting the difference in price. They are the same thing. Either one can be attached to an object and tracked thru the site.

Some of us feel caches are meant to be earned

1. Participating 07/08/07 2. Received Name 07/14/07 3. Mission Complete 07/30/07 4. Package Received

Here's an example of how a discover log could have been helpful, and prevented a quantum leap. One of my bugs was at an event, prior to the addition of the discover log. Several attendees wrote down the tracking numbers of several bugs, including mine. The cacher that took my bug with him waited a week to place it, giving the rest time to grab the bug from the event, and then place it back into the event. After he placed the bug into another cache, one of the slow loggers grabbed it, not noticing which cache it was in, and then placed it back into the event. Now the bug has miles it didn't travel, is logged into a cache it isn't in, and is in a cache it's not logged into. The discover log would have left the bug in the cache it was actually in since you don't have to replace a bug you discover.

Someone's gotta ask. How many caches does it take to become an actual geocacher? Do I need to ask Mr. Owl?

Other than logging them on the web site? No, not really. The logs online seem to be a good record for me, and I can retrieve them all with the My Finds PQ. I took the post to mean caches not yet found. Looks like a good system. Wish I would have thought of it before I had access to the pq. My binder of cache pages was way too bulky.

So, are these 3 profiles, that are the same person, all premium profiles, or are they using the "back door"?

Do I see "... coin dedicated to the ...." ?

I don't buy this assumption one bit. Out my 102 caches hidden, the primary caches that "disappeared" were in remote areas, and were open to everyone (non pmoc). The possibility that muggles "stumbled" upon my caches is so remote, that is doesn't even register with me. In one area where I cache, and large swath of geocaches disappeared , and none of them were PMOCs. Most of us figured a "maggot" drove around and removed all of the caches. My "safest" caches all have the following traits (long hikes, PMOCs, and puzzles, or require special equipment.) I was speaking overall, but your example of including just your own and local caches does coincide with the original posters example of including only his own caches. I still believe if all caches were included, it would be evident that most damage was done by non-cachers or nature. I guess I prefer to give more credit to cachers, checkbook notwithstanding.

Could that possibly be because there are more non-paying members?

While the focus of my original post seems to point more toward damage by non-members, I think that the above statement is more indicative of where I intended my focus to be. Three of my six caches are MOCs. On of them, In Their Honor, is in a cemetery near a war memorial. I don't think that muggles will find this one, but I want those dedicated to geocaching (not that paying the money insures that) to be the ones to find it. There is a reverence to places like that. The other two caches each have their own stories as to why I have made them member-only. Like a politician, my viewpoint on this issue may change at any moment. These are the same thing. If you mean non-paying members, and you have seen that non-paying members show less respect to your caches and cache sites than paying members, then I guess making them a SOC might fix the problem. However, since your SOCs are traditional caches, it is possible for non-paying members to locate them by triangulation. I've done that just for fun

Shilo, the one updating the page, is at an event this weekend and wasn't sure if they could get them updated, but would try. Also, the coin page itself doesn't update right away unless the owner recalculates the distance.

If I did that, I'd spoil my new cache I'm working on one that will have a combo lock on it. Two like puzzles: one to get the coords, and one to get the combination.

Do you have data to back up that assertion, or are you just revealing the fruits of your omniscience? In my part of the world, the most damaging thing that happens to caches is that geocoins disappear from them. The members-only caches don't have much trouble with this. This is a great point. A lot of newbies think you can trade for geocoins and keep them. This is very frustrating for the owner because coins typically cost $5-$10. Most premium members would know better but it still could happen. I took the original post as physical damage to the cache. I don't consider missing TBs or coins to be damage to a cache, altho pretty irritating to the traveler owner. I'm also guessing most coins that come up missing aren't owned by the owner of the cache they visited last.

It's up to you. The nice thing about making one of your caches a Member's Only cache is that you can watch who is viewing at your cache and when they are viewing it. Provided they don't get it in a pq and load it into gsak and a palm