Hello,
I've just observed an oddity with the FindStatgen3 macro (v4.6.20). My apologies if this has already been raised.
When determining one's "Most Northerly/Southerly/etc cache found", this GSAK macro seems to be using the cache's corrected coordinates (if present) whereas geocaching.com's Statistics page uses the cache's actual coordinates (not the solved coordinates). This results in a discrepancy between the two statistical displays as they will each show a different cache if there is a another found cache located between the most northerly cache's actual and corrected coordinates. Do you follow me? In my case, GSAK shows a different most northerly cache than geocaching.com. I believe that the FindStatgen3 macro should be updated to use a cache's original coordinates so that it matches what geocaching.com displays.
Cheers,
rocketphish
I've just observed an oddity with the FindStatgen3 macro (v4.6.20). My apologies if this has already been raised.
When determining one's "Most Northerly/Southerly/etc cache found", this GSAK macro seems to be using the cache's corrected coordinates (if present) whereas geocaching.com's Statistics page uses the cache's actual coordinates (not the solved coordinates). This results in a discrepancy between the two statistical displays as they will each show a different cache if there is a another found cache located between the most northerly cache's actual and corrected coordinates. Do you follow me? In my case, GSAK shows a different most northerly cache than geocaching.com. I believe that the FindStatgen3 macro should be updated to use a cache's original coordinates so that it matches what geocaching.com displays.
Cheers,
rocketphish