cgeo: Strategy of OC/GC duplicate handling

This was discussed a little bit in #2254 or #2311 already.

If I look into the current implementation of oc.de on live map and in searches, I see a lot of caches which are listed double (OC and GC). What to do with these duplicates ?

Several strategies (from users perspective) could be used IMO:

Evaluate the waypoint gccom field and/or the OC-attribute OC-only and filter out caches which are listed on geocaching.com. (This means: Show only OC-only caches)
Evaluate the waypoint gccom field and combine both data into one cache description (and one cache icon, one search result), where the gc.com listing is the master and the OC-wapoint is additionally shown in that listing.

I suggest to at least implement solution 1 as an optional setting if technically possible.

About this issue

Original URL
State: closed
Created 11 years ago
Comments: 21 (16 by maintainers)

Most upvoted comments

But setting GC as an optional data source is not the complete solution for this. In case the user is interested in both he may also switch on both sources and then the results on live map are confusing. It is a mixture of the following cases for caches listed on both platforms:

OC icon is over GC icon, thus GC is not selectable
GC icon is over OC icon, thus OS is not selectable
GC icon is approximated and so GC- and OC icon are not shown on the same position

In my opinion we have to have a duplicate handling !

Lineflyer on Feb 16, 2013

I suggest to completely ignore any duplicate handling. Instead it seems more logical to make the GC connector an optional data source (like the OC connector already is) by means of having a checkbox to disable it.

In the meantime, there is also a workaround in place for cache lists at least: I’ve added a normal cache filter to filter by origin (i.e. by connector).

Bananeweizen on Feb 15, 2013