myotis
-
Posts
1204 -
Joined
-
Last visited
Posts posted by myotis
-
-
I have been told to turn mine off before. So I always keep it out of sight to avoid possible problems. Not allowing them never made sense to me either.
I have the 60CSX too and have been wondering how it would do on a plane. Did you still have to stay in the window seat for it to work or would it work elsewhere in the cabin?
I always change the units on mine to knots when in a plane. Is not that what you use for flying?
I used mine on my Southwest flight from Albuquerque to Phoenix. I didn't even check the list and no one had a problem with it. Max speed: 445mph.
I had mine hooked up to my laptop with nroute so i could see it on the big screen. The 60csx didn't even have to be against the window to get a good signal.
-
Do you have any proximity POIs loaded?
Try, set up, system, and turn off proximity alarms.
When I load POIs with proximity alarms, the map will freeze. I had my GPS replaced twice before I figured out what the problem was and how to get around it.
-
Actually, that is not the case. I had City Select V 5, City Select V7 and City Navigator all loaded and working in Mapsource at the same time. When you upgrade, the previous version is still installed and still works. You have to uninstall the older version seperatly.
Well, one of the other things I don't like is that with the upgrade you essentially toss the prior version out the window and don't have access to it anymore. I've used some software wherein I liked the prior version better and reloaded the earlier version because I felt the revised version was bloated. Once you update, there's no going back to any of the prior versions as I understand it. It's good to hear that they're good to work with - but it does bother me to have to pay extra to use something in the interim while waiting for the map I want. Good thing I have the World Cup to distract me a little bit from this. How about that Shaka Hislop? Hate that the warranty clock is ticking while my unit sits there mapless. Thanks for the history of how they've backdated the release date and given folks discount for the update.
-
Not sure if I am understanding your problem, but why don't you put all your waypoints in the same file and then upload it to your GPS?
If you are saying you can only get one waypoint in your mapsource file and have to upload each file to the GPS, try this. Open Mapsource and open your first waypoint. Open mapsource again (you will now have two copies of Mapsource open) and then load another waypoint. Then rightclick on the waypoint and select copy. Then go to the other copy of mapsource and past the waypoint. Then go back to the other copy of Mapsource open the next way point and cut and past it too. Then when you get all your waypoints into the first copy of Mapsource upload them to your GPS.
I've saved all the waypoints for the caches i want to attack, as instructed on geocaching.com but using mapsource to get them into my Legend Cx seems to be more time consuming than the old plug'n'chug... I can only open one waypoint file at a time and it has to establish a connection with my unit everytime i transfer... It doesn't let me open more than one waypoint file at a time...
[mapsource 6.8.0 - usb connection provided with unit - uploading .gpx files saved directly from geocaching.com - current method used = file -> open -> my garmin -> file.gpx -> transfer to unit]
-
I am using NiMH bateries.
To the two who did not get the same result, maybe you did not get it set up exactly like I describe. It only happens under the conditions I describe. When you cycle through the pages, you should get the day view twice. When you get it the second time is when the problem occurs. If you press menu on the first time it occurs or in some view besides day view, it works fine.
-
There is a problem with the calendar menu and I have had similar issues with all 3 of my 60 CSXs (they have exchanged it twice) so there is a software problem. Here is how I get the same behavior. I add the calender to the page sequence. Then I set day view as default view which makes it show the day view twice when you go through the sequence (a bug). When you go through the page sequence and go to the second occurance of the calendar page, if you select menu or some other things, it does what you describe (fades and shuts down). Its done it in all versions of the firmware. While it is not exactly the same thing, it sounds like the same software bug causing the problem.
After a day of caching I was logging my finds and using the Geocaching function to show the ones I had found that day. I had marked a couple of waypoints were the coords were off. As I was logging I deleted those. The first one I deleted I watched the screen dim and fade away. Restarted deleted another same thing. Switched batteries, same thing. I had turned off the GPS on the satellite page, so I left it turned on, same thing. I was deleting these from the the calendar menu, when I deleted a waypoint found on a different day from the find menu it stayed on. When I deleted a geocache waypoint found on a different day from the calendar menu it stayed on. I can delete a geocache waypoint that I found today from the find menu and it stays on.
Also, when hunting for caches today under heavy tree cover, there were several times when the needle on the compass seemed to freeze, I could walk in a direction see the distance to next number decrease, but the needle continued to point away from were I was going. I don't think the two issues are related. Any one else experience either of these.
-
With no help from Garmin, I think I got the problem narrowed down to proximity POIs. When I load a file that has some POI with a proximity alert, the problems begin. When I go into system setup and turn off proximity alerts, the problem goes away. What is also interesting is the file has a POI about 3/4 of a mile from me, but I do not have a proximity alert set for that POI just other POIs in the file over 100 miles from me. But there are two spots between my house and the POI in the file that it almost always will lock up at (it does not with the proximity alerts turned off). So apparently when you load a file with a proximity alert in it, it does something that locks up the map. I have given Garmin this informaiton and I am hoping this time someone who knopws what they are doing addresses it and figures it out.
Anyone out there with proximity alert POIs without this problem?
-
Do you have Custom POIs with proximity alerts enabled? If so, try turning off proximity alerts. After returning my unit twice and many headaches, I have discovered this is my problem. ON mine, the map locks up in certian locations (not near the POI with proximity alerts). It will lock up in the same place over and over again. It does not do it on topo maps. Just City Select and City Navigator.
-
I live in IL by St Louis. I have had 3 60CSXs now (I have had to return 2 since Garmin kept telling me it was a hardware problem when it was my custom POIs locking up the maps) and up until I took a trip to WV over the weekend, I was never able to get a WAAS fix. In WV, I was able to get a WAAS fix with no problem. I forget which number I locked onto, but I got the Ds. Now back in IL, I cannot get a WAAS fix.
-
I was having problems with City Select 7 and I got Garmin to send me Navigator 7 so I can tell you there is a big difference besides file sizes. Navigator has much more information and does a better job navigating. Here is an example, if you follow I-64 through IL and then take I-57 South, City Slect will draw on the map the proper route but it never tells you to switch from I-64 to I-57. City Navigator will. I said that is a defect, Garmin says it is designed that way. The issue is I-64 and I-57 merge and you never take an exit to get from I-64 to I-57 so while City Select draws it right on the map, it never tells you to swith Interstates. I thought that was a pretty significant error.
Are not the files merged together when they are loaded on the GPS? On the card reader there is only one file. So I do not think it makes it easier to calculate routes. It just does a better job of telling you what to do.
I also noticed City Navigator also has better info on names. For example, when a road has a name and highway name, City Select just gives you one, City Navigator gives you both.
-
I got City Navigator and tried it and it locked up within a few minutes too.
But I think I may have determined the problem, my custom POIs. I have about 5,000 of them in several different files. I took and only uploaded one of the files that did not have files anywhere near here and I was not able to get it to lock up. So I have to go to a meeting now and I will take my GPS with me and see what happens.
-
Darn. Now I am worried that CitySelect is not the problem. This is simply really strange. Tech support finally agreed to burn me a DVD with City Navigator on it (none in stock) and overnight it to me to see if that fixes it. I am going on aq long trip Thursday so I sure hope this fixes it. I also tried changing it back to 2.70 from 2.71 and it still locks up on City Select and works fine on topoUSA.
-
Well they overnighted me a new unit. And guess what it does the exact same thing. The problem appears to be with City Select. Is anyone operating City Navigator 7 with the firnware 2.71 abd software 2.5 and it working OK? I went out with city select on my card and topousa on the card that came with the unit. I am waiting on hold for tech support.
-
Well, I talked to Garmin and they said to return it.
I messed around with it some more on my bike today. City Select messed up right away. I tried and tired to get it to lock up on topoUSA and it finally did once. So city select is much worse.
-
Thanks,
Compass has always been off. It does it when it is driving and biking. I've never had it do it when I was hiking. Which is interesting as I turn off City Select when I hike. I was out tonight and it kept acting up. I turned off City Select and just had USA Topo showing and it worked fine. I turned City Select back on and it locked up in about 5 miles when I made a sharp turn. I turned off City Select and I tried hard to get it to lock up and could not. I went to some spots where it usually locks up and it would not lock up. While I have not used it enough with City Select off to feel confident that it is the problem, I am suspecting it is. Maybe there is an issue with the unlock code or something.
Is this happening while driving in your vehicle or walking/hiking? Is the compass on when it happens? I'm asking only to help narrow the conditions down that may be contributing.
Olar
-
I've been having a problem with my maps locking up. I had the problem with my first 60CSX and exchanged it and I am having it again. Sometimes (now on a regular basis) when you make a turn (a 180 turn causes the problem most often), the GPS stops reading the map from the card. The map will generally keep moving (sometimes it just freezes) and anything not on the screen at that point will be blank and it will not rotate. If you do zoom in or out, it just freezes up and shows drawing. Most times when you turn it off and back on the map will reappear. Sometimes it will not reappear at all and the map will be blank. Usually if you zoom way out and turn it off and then on, it will then work.
The problem happens most often with my 1 gig card, but it also happens with my 512 meg card, and the card that came with it. I've tried reformatting the cards and run check disk on them. I've reloaded maps and loaded different map sets.
I have the most problems with the 1 gig card. Sometimes it takes it forever before it will recognize it. When it is not recognizing it, none of the POIs or my custom POIs show up in the find menu. Under these circumstances I can load the card into a reader and access everything. Likewise, I access everything on the card when it is not being recognized via the USB interface.
Has anyone else had this problem?
The first unit I had, Garmin told me to return it so I exchanged it at REI. When I called them again about it, I thought it was related to the elevation problem but I am still having the problem with 2.71. When I was running 2.60, I called Garmin and they had me do a master reset. It did not work. A day or two latter it just started working and worked well for a couple of weeks. Now it is driving me crazy again. I am going to call Garmin in the morning but am wondering if anyone else is having this problem.
-
Prime Suspect,
When you ignore the facts, it is easy to be critical of others.
Just how am I misleading someone on if the cache is there or not when I specifically tell people exactly what is happening. If you don't want to hunt the cache with the way the thief is being dealt with, no one is forcing you to. I am warning people exactly what to expect so it is not like being told incorrect information.
An analogy to what you want is you think the store owner has an obligation to help the thief out by leaving the door open for them.
As an analogy, that's more than a bit off base. This is more in line:
You look up an entry in the Yellow Pages and find a 24hr copy shop. Just what you need, since it's 4am and you need the copies by 6am. So you drive there, only to find the place is closed, and doesn't open for hours.
Later you contact the owner to find out what's going on. He says, "Oh, we were having too many break-ins. I figured the thief was using the Yellow Pages to find out which places were closed at night. So I called up Yellow Pages, and had my listing changed to show that we're open 24hrs. Great idea, right?"
"Have the break-ins stopped?"
"Well, no. But it's still a great idea, right?"
"Don't customers get P.O.ed when they drive all the way to your shop, and find you're not actually open?"
"Well, yeah. But it's still a great idea, right?"
Sheesh.
-
Cow Spots,
I am glad you agree (contrary to what some have asserted) there is no way to stop a determined thief.
You obviously have not had to deal with anything like we have and you gave up much easier than we did. If we gave up as easy as you did there would be no caches in the area. Is having no caches in the area a better situation that what currently exists?
You say, "Telling people about a cache thief absolutely is proving accurate information. It's just not telling a hunter the full story." How is that? I am telling them exactly what I am doing. When the thief steals the cache over and over, there is no way I can let anyone know for sure it is there. All I can do is try to make it more likely it is there. That is what I am trying to do.
You state, "My opinion is that there are better ways to handle it. It's my opinion that you should provide the best information you can about the cache."
Yes but you acknowledge he cannot be stopped. So what is your better way? I am providing the best information I can about the cache. The problem is you can never be sure it is there.
You state, "The only burden I share as a cache hunter to prevent a cache from being stolen is to rehide the cache as well as I found it, and in the cache of high-traffic areas, not to be too obvious to non-geocachers while searching for it. What other duties should I have for your cache?"
What about being more understanding of the situation? What about not helping the thief out by making it easier for him to know when he needs to go steal the cache?
How many of your caches have been stolen and how many times?Let's see. I'm listed as owner of 14 caches.
Of the three that have been archived --- one got stolen 3 times, and I chose to archive it because I felt that I had made a poor choice of location in retrospect. One was a co-hide with my brother that was archived after he left the area, and the third archival was due to the cache being buried by rising floodwaters.
Of my 11 currently active caches, I've had to replace 2 : 1 that was stolen, and one that was inadvertantly taken away by workers in the course of their duties.
Fortunately, I have never suspected a habitual cache thief --- just muggles, would be my guess.
How is telling people what the situation with the thief is not providing accurate information?Telling people about a cache thief absolutely is proving accurate information. It's just not telling a hunter the full story.
When the caches get stolen after they are replaced there is no reasonable way to know if the cache is there. So it is not possible to provide accurate information on if the cache is there.
This is where a "temporarily disabled" option, or even a note is entirely appropriate - something to the effect of "The cache may have been stolen, and I will check this at my earliest opportunity and replace it if necessary."
While I could tell people when it is gone and replaced, that just makes it more likely it will not be there when someone looks for it.You act like it is all about you as a cache hunter and all the burden of dealing with the thief should be on the cache owner. Why should not cache hunters share the burden of dealing with the thief?
Because it's your cache -- you chose to place it there, you chose to agree to maintain it, you chose to be responsible for it.
The only burden I share as a cache hunter to prevent a cache from being stolen is to rehide the cache as well as I found it, and in the cache of high-traffic areas, not to be too obvious to non-geocachers while searching for it. What other duties should I have for your cache?
No one is forcing you to go hunt caches there and no one is concealing the situation.By listing the thief problem on the cache page, you are providing a caveat emptor to a prospective searcher. But by deleting pertinent information about the cache being missing or not, you're certainly concealing information, aren't you?
Most people appreciate the hundreds of hours we have put into fighting the thief so they can have a good time. So would not the solution be people who do not appreciate the efforts to provide quality caches go find some other caches and stop complaining about our efforts to provide others a good time?You can't stop a thief that is determined enough. They can pay for premium membership. They can solve a puzzle. They can create a sock puppet to get the coordinates directly from you in email.
As I said previously, I absolutely sympathize with fighting the thief. My opinion is that there are better ways to handle it. It's my opinion that you should provide the best information you can about the cache.
Of course, that's just my opinion. I could be wrong.
-
He can express his opinion of how I should deal with it and I cannot express my opinion of how he should deal with it?
Why is not those who don't like the way we are trying to combat the thief not hunt our caches not a valid and reasonable solution?
Myotis,
Cow Spots is entitled to express a contrary opinion to yours. Even if Cow Spots has never lost a cache to a thief, he is entitled to an opinion about this lost cache situation and its impact on finders. Telling Cow Spots to go find some caches and stop complaining is not adding much to the discussion. Please stick to debating the merits of what this community member had to say. Thanks.
-
Cow Spots,
How many of your caches have been stolen and how many times?
How is telling people what the situation with the thief is not providing accurate information? When the caches get stolen after they are replaced there is no reasonable way to know if the cache is there. So it is not possible to provide accurate information on if the cache is there. While I could tell people when it is gone and replaced, that just makes it more likely it will not be there when someone looks for it.
You act like it is all about you as a cache hunter and all the burden of dealing with the thief should be on the cache owner. Why should not cache hunters share the burden of dealing with the thief?
No one is forcing you to go hunt caches there and no one is concealing the situation. Most people appreciate the hundreds of hours we have put into fighting the thief so they can have a good time. So would not the solution be people who do not appreciate the efforts to provide quality caches go find some other caches and stop complaining about our efforts to provide others a good time?
Maybe I'm missing something.
To me, part of your responsibility as the owner of a cache is to make an honest effort to provide accurate information about the cache to prospective fellow geocachers.
This includes reasonably accurate coordinates and the current status of the cache, be it missing, damaged, or "good to go." Removing information that accurately reflects the current status of the cache, or the last known status of the cache, does a disservice to anyone that may seek it in the future.
Hey --- I sympathize with someone dealing with a cache maggot. But this one's cut and dried. Removing pertinent info about the status of a cache does more harm than good.
-
Vinny & Sue Team,
You are the one making the personal attacks even after you said you were going to mind your own business. It would appear that you think if you talk about God and St. Jude it excuses your not acting like a Christian. I do not see how insulting and attacking someone who has spent hundreds of hours trying to provide others a good time is acting like a Christian. How many people who were spending their time to help others did Jesus attack and insult? You are invoking St. Jude. When did St. Jude accuse someone trying to do things for others of having "an undisclosed (and perhaps unconscious) agenda or motive, or that there may be extant impairments or personal factors of which we are largely unaware." Would Jesus say something like this or some of the other insults you have thrown at me?
Its people like you that make me wonder why I have not just given up and let the thief have their way of no caches down there. But fortunately, most people act like Jesus did. They show appreciation and support for the efforts those of us have made to try to provide good quality caches in a very difficult situation.
I also appreciate the many people on here who have made CONSTRUCTIVE suggestions and shown support for our efforts to provide people quality caches in a very difficult situation (as opposed to those who throw insults, don't know what the situation is, and just claim there is some simple solution without pointing it out).
IMHO, people should also be complaining to geocahing.com that they are not doing a better job helping cache owners dealing with cache thieves.Ah, I see. Do you complain to the Yellow Pages when you get a prank phone call?
And, do you complain to Google search engine when a website listed in the results of a search turns out to have been hacked by hackers, bitterly telling them that it is their job as a search engine which lists billions of websites, to protect all of those websites against hackers?
What continues to amaze me here is that the cache owner has made an appearance on this forum and has repeatedly refused to implement the simple common-sense measures for each cache listing page which would stop this problem once and for all with a likely efficiency of over 98%. In fact, he has reacted with anger at the merest suggestions of such prophylactic measures, much as he has reacted with anger at almost anything else which has been said in this thread, as well as directing his anger repeatecly at the OP (Cybret) for imagined offenses. To me, this chronic pattern of behavior suggests that the cache owner may have an undisclosed (and perhaps unconscious) agenda or motive, or that there may be extant impairments or personal factors of which we are largely unaware. In the meanwhile, I would like to invoke the intercession of St. Jude, much as an earlier poster has already proposed. . .
And, in closing, I would like to respectfully request that either this thread be immediately closed or alternatively, that the cache owner's on-forum behavior be managed (i.e., moderated) more tightly by the moderators, since it appears that this thread is fast turning into a venue for unreasonable and unwarranted personal attacks, as well as specious arguments, launced by the owner of the cache in question. I do not think that the original poster (OP) nor subsquent posters deserve to be targets of this kind of behavior. If someone wants to rant or rage in an unreasonable fashion, there are entire foums where that is the accepted norm, including some forum threads at the site known as The Cacher's Sandbox.
-
Yes I have and GeoJoe has much more. He is a nut case. He even thinks some of us are watching his house. He claims we do not have permission, thinks it is a National Park, etc. I've told him it is a National Forest, we have permission, who gave it, etc. He also claims they are all causing damage etc. which is not the case. If one of my caches was causing a problem, I would shut it down. I also recently talked to the Forest Supervisor about setting up an informal process for the Forest Service to review cache locations to make sure there is no problem with it and he thought that was a good idea. I've talked to GEOJoe and IL Adm about it but have been sidetracked dealing with this stuff.
I'm asking this in all seriousness - have you talked to the thief?
-
Let me reply to several at once.
briansnat asked, "Does it really make sense to let the cache thief know exactly what is going on? Never mind that you are giving him the attention that he obviously craves and actually encouraging him." He also presented a slightly different twist on how to deal with it. First, thanks for the suggestion. I don't know what is the best way to deal with it. This is the best I can think of. I think your suggestion would also get the people who don't like my efforts to provide people quality caches in a very difficult situation upset too. I want to let him know for reasons I will only tell you off line as he may be reading this.
For the record, we know his 3 user accounts, we know his name, and we know the area he lives in. Geocaching.com won't ban him. So we have to use Plan B.
Keystone stated: "Just a note to indicate that I am not aware of any published rule, guideline or TOU that says "If you are not pleased with not being able to log a find due to the thief, geocaching.com says you are not supposed to be able to log a find." Cache owners and cache finders work out the rules and etiquette for logging. If Geocaching.com had logging rules, a number of high-profile forum threads wouldn't exist, would they?"
They have threatened to shut down my caches for me doing it. While I have told them I am not trying to convert it into a virtual cache, plan to promptly deal with a missing cache, and just trying to deal with the bad situation, I am told doing that makes it a virtual cache and that is not allowed. Dealing with the reviewers and geocaching.com is almost as frustrating as dealing with the thief. You would think they would be more understanding. CYBret's log is still locked on my cache page.
Keystone then asked, "It's a website based in Seattle Washington that lists information about tupperware in the woods. Not a law enforcement agency. What would you have them do?"
First I would have them be more supportive of the cache owners. There should be specific guidance that rules can be bent or waived in order to deal with a thief instead of bending the rules to make it harder to deal with the thief. For example, when you disable a cache because it is stolen again, they should give you more time to get it fixed than normal before they start to threaten to archive it because you have not replaced it fast enough for them.
They should also provide us more information to help identify the thief. For example, why should not we be able to know who is watching our caches or getting them in pocket queries?
They should also have a FAQ to give to cache owners on how to deal with a thief.
When you know who it is beyond a reasonable doubt and you have given the accused a chance to defend themselves, ban them.
Finally, use our dues to develop more technology to fight the thieves.
OzGuff stated:
"Back on topic -- I have always felt that my logs (Finds, Notes, DNFs) are records of my experiences, the good, the bad, and the ugly. I would be pretty upset if a log of mine was deleted. I understand the cache owner's frustration at having caches stolen, but there has to be another way to deal with this other than deleting logs on the cache page. [Though I have no ideas.] The thief MUST be watching it so already has the info."
As I said before, I have had caches stolen that no one was watching them. If I was going to steal caches, I would not point myself out by watching caches. I am betting he does not know that we have not been able to find out who is watching the caches.
Would you be upset at the thief or the person who has spent hundreds of hours trying to provide you a good time under very difficult circumstances? Should everyone share in the efforts to deal with the thief? Or is the cache hunters the only thing that matters? Others come across to me this way. When someone is stealing the caches over and over again, it is not a perfect world. You say you do not know a solution. I don't either. So is it right for the cache hunter to expect it is all about them and the heck with those who spent hundreds of hours trying to provide them a nice experience? IMHO, one who thinks their accuracy is more important than dealing with the thief should go cache somewhere where it can be all about them.
-
Ed,
I agree there is no way to stop a determined thief. We know who he is and geocaching.com/reviewers won't do anything other than hassle me for trying to provide cachers quality caches under very difficult circumstances. Since we have not been able to stop him, I am simply trying to do everything I can to make it more likely there will be a cache there when someone goes to look for it. My strategy is to conceal from the thief the status of the cache. Many of these caches are long drives for the thief. So if he does not know if there is a cache there that needs to be stolen, it will be more difficult for him to continue to steal the caches. He could go on wild goose chases. It is much harder to steal something if you do not know if it is there.
If someone logs a DNF, as you point out you are not going to go look for it until it is replaced. So if there is a DNF, there is a need for me to indicate it has been replaced. As soon as I do that the thief knows to go steal it again. So you could see that I replaced it and then go and look for it and it would not be there.
So doing things the way you suggest results in the thief knowing when he needs to steal it and users not knowing the status of the cache.
If I went and spent hours looking for a cache that was stolen, I would be upset too. That is why I have no problem with someone logging a find when they find the spot but the cache is stolen. The cache police in goecaching.com have a problem with it, but I don't.
I would also point out the first thing on all my caches down there is a note in bold telling people about the thief and how I am addressing things with the cache. So if you knew the situation, why would you look for hours for it? I am warning people about the situation. So they know what the situation is like and if they choose to do the caches, they know the situation.
I've been working on the wording for the caches. Here is what I have on it now:
<B> There is a problem with a cache thief in Southern IL who keeps stealing all the caches over and over again. We are pretty sure who it is. If you do not find the cache, do NOT post a did not find or anything in your log to indicate it is not there. Email me and let me know it is gone so I can get it replaced without alerting the thief. If you do something like take a picture of yourself or your GPS in the correct place or tell me about the spot, I won’t object to logging it as a find. I have also placed more than one container at some of the caches, so if you find more than one container, do NOT say anything about it in your log. While this won’t stop the thief, this will make things much more difficult for the thief.</b><p>
Here is what I am now thinking of changing it to:
<B> There is a problem with a cache thief in Southern IL who keeps stealing all the caches over and over again. We are pretty sure who it is. If you do not find the cache, do NOT post a did not find (DNF) or anything in your log to indicate it is not there. Email me and let me know it is gone so I can get it replaced without alerting the thief. I would appreciate people carrying a replacement container and log in case the thief has stolen the cache. If you replace it for me, sign the log, log a find and do NOT mention in the log you replaced the container, and email me that you replaced it. If you don’t have a container and are not pleased with not being able to log a find due to the thief, geocaching.com says you are not supposed to be able to log a find. But if you do something like take a picture of yourself or your GPS in the correct place or tell me about the spot, I am not the cache police and logging it as a find will help confuse the thief on the status of the cache. I have also placed more than one container at some of the caches, so if you find more than one container, do NOT say anything about it in your log. While this won't stop the thief, this will make things much more difficult for the thief.</b><p>
Bottom line is the problem is the thief not me. If the thief was not stealing the caches over and over again, there would not be a problem. I have spent hundreds of dollars in gas and hundreds of hours replacing these caches over and over again so people can have a quality caching experience.
I know it is not a perfect solution. But it is the best I can think of. While people claim there are simple solutions to stop the thief, they have not pointed one out. It sure seems like you and others think all the burden of dealing with the thief should go to the cache owner and the cache hunters who enjoy the work of cache owners should not have to share in any of the burden of dealing with the cache thief. Should not the cache hunter be appreciate of the efforts to provide caches in spite of the thief and have understanding that things cannot be perfect for them?
IMHO, people should also be complaining to geocahing.com that they are not doing a better job helping cache owners dealing with cache thieves.
When a cache is being stolen on a regular basis, a find on the cache page does not mean the cache is there. It could easily be stolen again. Likewise, a note that the cache has been replaced does not mean it is there as it could be stolen again.
It is just me. or is this the weirdest logic I have ever read??
A find on the cache page OF COURSE means it there...someone just logged that they found it!...duh.
A note on the cache page that the cache has been replaced OF COURSE means it's there...you are saying you just replaced it!...duh.
Deleting DNF is a diservice to future cachers. If I read Cybret's DNF, I would not have looked for the cache the next day. If the log is deleted though, I have no way of knowing it ISN"T there, and I could look for hours not knowing. I would be pissed if I spent time looking for a cache that is confirmed missing, but the owner deleted the DNF logs.
The whole idea of deleting logs is lame and serves no real purpose. There is no way to stop a determinded cache thief by messing with the cache page logs.
Ed
Good Case To Attach To Backpack Strap For 60csx...
in GPS technology and devices
Posted
I attach mine to my camel bak and backpack with the clip that comes with it. It works great. When you want to look at it, you just release the GPS from the clip and then you have easy access to it. However, make sure you securely attach the strap to something in case you drop it or it comes loose. I use a longer wrist strap than the one that comes with the GPS.