Jump to content

Out of order distances


Bunganator

Recommended Posts

Posted (edited)

These are the PQ results for unfound caches within 100 miles of school. I can't even figure out how they are sorted:

 

f074fac6-eff9-4f87-b0ed-416b3c563c6c.jpg

Edited by Bunganator
Posted (edited)

These are the PQ results for unfound caches within 100 miles of school. I can't even figure out how they are sorted:

 

f074fac6-eff9-4f87-b0ed-416b3c563c6c.jpg

 

It looks like it is sorted by type, then by distance.

 

Edit to note that the traditionals are sorted by distance, but backwards from the others. How odd!

 

:) Second edit. I guess my eyes were playing trick on me. As noted, There appear to be no sort order at all.

Edited by Don_J
Posted

I just saw this today as well. Very irritating when the cache you are looking for no longer appears next in the list. I was starting to wonder if it had gotten archived before I found it.

Posted

Is no one else noticing this?

 

Its been broke for several days and is affecting any list that should be sorted by distance (nearest caches, pq previews with a center point, etc).

Posted

Happening hear on any cache you pick the nearest or even nearest home co-ords shows the same problem.

 

Yup, I'm having the problem when searching for cachest nearest my home coordinates too.

Posted
This problem should be fixed.

 

-Raine

 

As others have mentioned, it isn't fixed any longer.

 

Examples on request, but it seems to be obviously wrong on every "nearest" I'm doing.

Posted

A quick glance at the original list included above shows that the list is sorted by Waypoint IDs (aka GC Code). They are in ascending order. Whether this is appropriate or not is a different question. But this is how my Pocket Queries have sorted for as long as I've been using them (<2 weeks).

Posted

A quick glance at the original list included above shows that the list is sorted by Waypoint IDs (aka GC Code). They are in ascending order. Whether this is appropriate or not is a different question. But this is how my Pocket Queries have sorted for as long as I've been using them (<2 weeks).

PQ's that ONLY have a date range or similar usually are sorted by date or waypoint code, I forget which.

 

PQ's and other queries that have a center point should (and have for several years) be sorted by distance from that center point.

 

For this specific example you do appear to be correct but I think that's a fluke and its definitely not true as you go to the 2nd page and beyond.

Posted

OK, I just went back to check both a "nearest" listing and a PQ with a center point, neither was sorted by gc code on even the first page as suggested here and even though both had the same center point, the sort order was different between them.

Posted

Yes i'm having the same problem, seems like this happened before about 1 month ago having the distances out of order drives ne nuts..

Thought I would give this one a check with my PQs and other searches based on a centroid. It is odd that I have not had and problems with distance order, ever. So it appears that it is only affecting certain serches or searchers. For everybody having trouble with this I hope this issue is resolved.

Guest
This topic is now closed to further replies.
×
×
  • Create New...