Ham fam 5 Report post Posted July 23, 2018 I could see a benefit in adding the ability to ignore via settings if a cache's most recent X caches are DNFs. I hate getting to a cache only to find that it's not been found the last 5 times. 2 Raiden38 and Lone R reacted to this Share this post Link to post Share on other sites
0 Lone R 1 Report post Posted July 23, 2018 8 hours ago, Ham fam said: I could see a benefit in adding the ability to ignore via settings if a cache's most recent X caches are DNFs. I hate getting to a cache only to find that it's not been found the last 5 times. Hopefully we'll see this feature in the future. Back in Feb 2017 Nic said "This is a good idea. Filter caches with recent DNFs. Will add this to our list." He's really great at implementing requested features that are do-able, so hopefully, filtering for rows of DNFs has moved up the list near the top. Share this post Link to post Share on other sites
0 Nic Hubbard 637 Report post Posted July 23, 2018 This would be possible to add for offline filtering. But online filtering doesn't have an API available to do this. 1 Lone R reacted to this Share this post Link to post Share on other sites
0 Ham fam 5 Report post Posted July 24, 2018 Does it pay for me to drop a line to Groundspeak to see if they can alter the API? Share this post Link to post Share on other sites
0 rragan 200 Report post Posted July 24, 2018 How about post-fetch filtering in the Live tab? The only odd thing would be the user asked for 50 and only got 40 since 10 were discarded (or hidden) by the "too many DNFs" filter. The user didn't want to see them anyway. This isn't too far off what you do for FTF marker. 1 Ham fam reacted to this Share this post Link to post Share on other sites
0 Nic Hubbard 637 Report post Posted July 24, 2018 5 hours ago, Ham fam said: Does it pay for me to drop a line to Groundspeak to see if they can alter the API? I have direct connections to HQ as a partner, so I can talk to them. Share this post Link to post Share on other sites
0 Nic Hubbard 637 Report post Posted July 24, 2018 2 hours ago, rragan said: The only odd thing would be the user asked for 50 and only got 40 since 10 were discarded (or hidden) by the "too many DNFs" filter. The reason I don't do this is there could be some search results where we filter out all caches, and the next request might be the same. So they user might be confused why they over and over are loading caches but nothing is showing. A sever side solution is ideal, a client side solution is not. Share this post Link to post Share on other sites
0 rragan 200 Report post Posted July 24, 2018 How about a post-fetch icon decoration like FTF but saying DNF? It would be an option like FTF is. Share this post Link to post Share on other sites
0 Nic Hubbard 637 Report post Posted July 24, 2018 10 minutes ago, rragan said: How about a post-fetch icon decoration like FTF but saying DNF? It would be an option like FTF is. You are meaning, if the last x logs were a DNF then alter the cache icon? Yeah, this is possible. 2 Lone R and Raiden38 reacted to this Share this post Link to post Share on other sites
0 rragan 200 Report post Posted July 24, 2018 Yes, that's what I'm saying. I think it meets his need in that he would just skip those and not even look at them on the map. Share this post Link to post Share on other sites
0 Nic Hubbard 637 Report post Posted July 24, 2018 2 minutes ago, rragan said: Yes, that's what I'm saying. I think it meets his need in that he would just skip those and not even look at them on the map. It would require load of full caches to get the logs, but that option can be turned on. Share this post Link to post Share on other sites
0 Ham fam 5 Report post Posted July 24, 2018 37 minutes ago, Nic Hubbard said: It would require load of full caches to get the logs, but that option can be turned on. I like it. I think others would too. Also if you could make it user settable as to how many DNFs trigger the icon. Some days you may feel lucky and other days, you just want caches that are probably there. 1 Lone R reacted to this Share this post Link to post Share on other sites
0 rragan 200 Report post Posted July 24, 2018 The only sad thing is that after the DNF threshold is reached, no one will go there to make the crucial "needs maintenance" to kick the CO and awaken the reviewer to start the days until archived counter. Some thought is needed though regarding just DNF counts. A group of 3 may not find it on the same day. Should n DNFs on a single day count as 1? I tend to think so. I guess if Needs Maint is the status, DNF icon would not show. Does 1 find override a string of previous DNFs. I think it has to. Share this post Link to post Share on other sites
0 Lone R 1 Report post Posted July 25, 2018 13 hours ago, rragan said: A group of 3 may not find it on the same day. Should n DNFs on a single day count as 1? My preferences, I'd like to see them count as 3. If those 3 people are seasoned cachers, the cache may actually be missing. It would be nice (but probably too complicated) if we could choose whether we want DNFs on the same day to count as 1. Share this post Link to post Share on other sites
0 rragan 200 Report post Posted July 25, 2018 I thought of the seasoned cachers case but didn't want to make the checking too complex. Sometimes you are just going to hit a DNF for a case like this but I expect they will be uncommon. You still have the logs to show multiple DNFs that you could consult before heading there. Share this post Link to post Share on other sites
0 Bolling 99 Report post Posted July 28, 2018 On 7/24/2018 at 6:05 PM, rragan said: The only sad thing is that after the DNF threshold is reached, no one will go there to make the crucial "needs maintenance" to kick the CO and awaken the reviewer to start the days until archived counter. Some thought is needed though regarding just DNF counts. A group of 3 may not find it on the same day. Should n DNFs on a single day count as 1? I tend to think so. I guess if Needs Maint is the status, DNF icon would not show. Does 1 find override a string of previous DNFs. I think it has to. Locally I use GSAK to do this. I'm a pain. Share this post Link to post Share on other sites
I could see a benefit in adding the ability to ignore via settings if a cache's most recent X caches are DNFs. I hate getting to a cache only to find that it's not been found the last 5 times.
Share this post
Link to post
Share on other sites