Some views on and wishes for use of Geocaching4Locus/live map with "corrected coordinates" of gc.com:
I (and many other cachers that I know) solve a great number of mystery/unknown caches, and usually take a lot of time before having an opportunity to find the actual cache. I have these "solution coordinates" entered into the "corrected coordinates" system of gc.com. In all I have probably a couple of hundred unfound caches with "corrected coordinates" entered. Locus with G4L has some handling of this, but I think it could be better, or perhaps I need help in how to use it in a better way.
As it is now, I almost always use the "live map" feature of Locus + G4L, see a lot of traditional caches, unknowns, multis etc. The ones I've "solved" are in the wrong/public location, but if I select the cache and view the details, the cache icon is moved to the "corrected" location on the map. However, it seems as if as soon as the live map does an update, the cache icon is moved back to the wrong/public location.
Furthermore, the icon displayed for a "corrected" cache is the same as for a normal cache of the same type, making it impossible to see which cache icons indicate real locations, and which are "fake", without going into details view.
These are my wishes and hopes:
1. Let live map do a scan of displayed caches for "corrected coordinaes" and automatically and immediately move the cache icon to the "corrected coordinates" (automatically on cache load, or, if this would be too resource intensive, triggered by the user). (feature request?)
2. Use differentiated icons or a flag/marker on existing cache type icons to indicate a cache which has "corrected coordinates". (like c:geo handles the same case) (fix?)
3. Do not let a "live map" update revert a "corrected" cache icon back to the "public" location. (fix?)
4. Allow filtering out non-corrected unknowns/multis/etc - or rather, add an extra option to "force" (unfound) caches with corrected coordinates to be displayed regardless of cache type hide settings. (example use: "hide unknown caches, but override this for caches with corrected coordinates") (One possible issue here would be the "challenge" unknown caches, that are actually at the public coordinates, but these have as requirement to have "challenge" in the cache title, so that could be sorted out automatically too.) (feature request?)
Perhaps some of these things would work better with imported PQs instead of live mapping(?), but for me this is not a good option since I visit a lot of different areas and do not want to set up PQs all the time.