Movables - possible code change request
-
- 1650 or more caches found
- Posts: 29
- Joined: 18 April 08 10:28 pm
- Location: Panania NSW Aust.
Movables - possible code change request
Is it possible for the "Found" Log on a MOVABLE cache to flag the co-ords as deleted or similar.
I know, I SHOULD read the logs first, but have been caught out on a few where the cache still shows on the maps as in a spot, but it has been found and removed (eg. todays attempted cache was removed 3 weeks ago), but not yet placed elsewhere.
That may need choices of Found-taken, and Found-left-in-place on the log options.
just curious,
thanks
Steptoe
I know, I SHOULD read the logs first, but have been caught out on a few where the cache still shows on the maps as in a spot, but it has been found and removed (eg. todays attempted cache was removed 3 weeks ago), but not yet placed elsewhere.
That may need choices of Found-taken, and Found-left-in-place on the log options.
just curious,
thanks
Steptoe
- CraigRat
- 850 or more found!!!
- Posts: 7015
- Joined: 23 August 04 3:17 pm
- Twitter: CraigRat
- Facebook: http://facebook.com/CraigRat
- Location: Launceston, TAS
- Contact:
Re: Movables - possible code change request
It's a good idea, however it causes a multitude of other problems with peoples gps's etc if we essentially 'blank' the co-ords apon a cache being found.
Let me think about about it for a bit, there might be something better we can do.
Let me think about about it for a bit, there might be something better we can do.
- caughtatwork
- Posts: 17025
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: Movables - possible code change request
Be careful.
A cache that has been logged as "found left behind" doesn't mean someone else hasn't found it a few minutes before you rocked up.
You have to change your way of thinking about a moving cache.
They have a challenge that the cache may not always be where you think it is.
Sometimes the onus falls on to you rather than the site to tell you where the cache is or isn't.
A cache that has been logged as "found left behind" doesn't mean someone else hasn't found it a few minutes before you rocked up.
You have to change your way of thinking about a moving cache.
They have a challenge that the cache may not always be where you think it is.
Sometimes the onus falls on to you rather than the site to tell you where the cache is or isn't.
-
- 1650 or more caches found
- Posts: 29
- Joined: 18 April 08 10:28 pm
- Location: Panania NSW Aust.
Re: Movables - possible code change request
I realise that it could have "just gone etc"
It was more a matter of flaggin the more obvious ones if possible
It was more a matter of flaggin the more obvious ones if possible
- caughtatwork
- Posts: 17025
- Joined: 17 May 04 12:11 pm
- Location: Melbourne
- Contact:
Re: Movables - possible code change request
It's the "if possible" that you can't trust.
I'll be interested to see what ideas CR has without creating confusion in "what type of log" people should use.
I'll be interested to see what ideas CR has without creating confusion in "what type of log" people should use.
- Richary
- 8000 or more caches found
- Posts: 4189
- Joined: 04 February 04 10:55 pm
- Location: Waitara, Sydney
Re: Movables - possible code change request
I think we would need a Taken/Grabbed/Retrieved type as a log entry, which would automagically flag it as Found for the stats, but also mark it as no longer at the coords.
The problem still exists that unless you check the cache listing immediately before going out it may have moved since your last download, and the person who has found it to move on may not get a chance to log that immediately. That's one reason if I know I am going for a movable I will log that as a note on the page so if someone goes out later they may know why they couldn't find it, before I get a chance to get home and log it. I will then delete the note once I do the found one.
The problem still exists that unless you check the cache listing immediately before going out it may have moved since your last download, and the person who has found it to move on may not get a chance to log that immediately. That's one reason if I know I am going for a movable I will log that as a note on the page so if someone goes out later they may know why they couldn't find it, before I get a chance to get home and log it. I will then delete the note once I do the found one.
- solomonfamily
- 1700 or more caches found
- Posts: 238
- Joined: 28 September 05 9:02 am
Re: Movables - possible code change request
I only download caches to my GPS that I have not found - Once I have found a moveable, I would happily find it again if it moves back close enough to me but I have to be careful as they become excluded by my filter.
If found (by me) and then moved (by someone other than me) - mark as unfound (except for the stats)...... hummmm....
If found (by me) and then moved (by someone other than me) - mark as unfound (except for the stats)...... hummmm....
Re: Movables - possible code change request
I like the idea of a "picked up" log.
Another thing with moveables (and it might be too hard), would be to calculate stats based on where it was when it was found, rather than where it is now. A while back I was scratching my head as to why I had a find in South Australia when I've never been there - then I realised, the moveable that I found was now in SA. When I found it though, it was only about 20km from home.
Another thing with moveables (and it might be too hard), would be to calculate stats based on where it was when it was found, rather than where it is now. A while back I was scratching my head as to why I had a find in South Australia when I've never been there - then I realised, the moveable that I found was now in SA. When I found it though, it was only about 20km from home.