Filtering issue

December 17, 2023, 05:55:45 AM

Hi

I have found that the filtering is done after all the caches have been loaded from the API.
I'm not sure about the reasoning behind this, but I have came across some issues.

If I want to find one or 2 specific caches that I have solved and they are placed in a big city with lots of caches, it is impossible to find them.
I create the filer "Is Corrected", but if I don't find the spot on the map where the caches is among the 300 loaded, they are not shown.

The same if I want to look at rare cache types. I only get to see the ones that are within the border of the nearest 300 caches.
Example; If I search for Wherigos in Copenhagen I only get one (and I don't know where all the oether ones are, because I can't see how far the search goes.

In my home city I have found a lot of the caches around, Filtering those out leaves me with a rather small amount of caches on the Live map.

This functionality is different on the official app, where the load of caches from the API is done with the filtering "integrated". This gives you a much better view of which caches are actually there. Evem the map on the webpage uses this approach.

Is it possible to somehow make a change or perhaps a switch so you could decide how the filtering should be done?

Re: Filtering issue

Reply #1 – December 17, 2023, 10:04:31 AM

The reasoning is to reduce API and network calls for multiple filter changes... quicker/easier to filter a previously downloaded list of all caches and then filter them on-device versus retrieving a new set for every filter change.

It's on a to-do list to see about alternatives.

Re: Filtering issue

Reply #2 – December 17, 2023, 11:09:31 AM

Yes, I must admit that the filtering is quicker, than on the official app, where it has to get the caches through the API first.

But the shortcomming is quite annoying when caching in cachedense areas and wanting to filter out/in thinigs.

If you need any testing or feedback on ideas feel free to reach out.

rgds
Jacob