CoyoteRed Posted June 2, 2004 Share Posted June 2, 2004 Right now &f=1 is only filtering the caches that I've found and not the ones I own. This isn't a permenant change is it? Link to comment
Jeremy Posted June 2, 2004 Share Posted June 2, 2004 No. It was an oversight. I have uploaded the patch to fix it. Link to comment
+jon & miki Posted June 2, 2004 Share Posted June 2, 2004 A couple of locationless caches started showing up on our first unfound page today. It's true we haven't found them, but I thought locationless would have been excluded from a zip code search, and we're pretty sure they weren't on our nearby unfound cache list yesterday. We're using a URL of http://www.geocaching.com/seek/nearest.asp...23&dist=100&f=1 while logged in as Jon & Miki. The unexpected caches are Somewhere in Time and The Chameleon Cache. We can work around it with a pocket query, but I thought you'd like to know about the change in filter behavior. Jon & Miki Link to comment
+WalruZ Posted June 2, 2004 Share Posted June 2, 2004 I too am seeing locationless on my nearest (filter finds) link. This is just plain annoying, as they come up depending on some arbitrary location when what i'm looking for is physical caches. Not that I have anything against locationless caches. I think you should auction them off on ebay occasionally to make extra cash. Link to comment
Happy Boy Posted June 3, 2004 Share Posted June 3, 2004 Same thing with my page. They don't have an actual location, so their "spots" should not come up. The website is acting strangely today. For some reason, although the LCs show up, they are not in the actual count, as my 100 find radius that I have not found is at 357, only one up from yesterday. Link to comment
+Great Scott! Posted June 9, 2004 Share Posted June 9, 2004 Does "&dist=" not work anymore for distances over 100 miles? I have a PQ that is set for 101 miles and I get 379 caches listed. Using "&f=1&dist=101" (or anything over 100) I get only 352 caches listed on the website. Link to comment
CoyoteRed Posted June 9, 2004 Author Share Posted June 9, 2004 Does "&dist=" not work anymore for distances over 100 miles? I have a PQ that is set for 101 miles and I get 379 caches listed. Using "&f=1&dist=101" (or anything over 100) I get only 352 caches listed on the website. You're right! Can't search over 100 miles anymore! I didn't notice because we're working on clearing out our 60 mile radius so we have our bookmark set to that. Link to comment
Recommended Posts