Return to Project-GC

Welcome to Project-GC Q&A. Ask questions and get answers from other Project-GC users.

If you get a good answer, click the checkbox on the left to select it as the best answer.

Upvote answers or questions that have helped you.

If you don't get clear answers, edit your question to make it clearer.

+2 votes
66 views

Hi,

the feature ProfileStats shows a wrong result:

The item "Furthest cache found:" shows 9,594.57 km, TAKE OFF TO THE RAINBOW’S END, GC1YTJ2 

This cache lies in Iceland and is NW 2568.5 km from your home

My real furthest cache found lies in Vietnam.

This problem exists since yesterday.

What went wrong?

Thanx in advance for your support.

Kind regards, eltopo00

in Bug reports by eltopo00 (970 points)
closed by Jakuje (Moderator)
Same problem for my profile.  Its correct in the badgegen calculation, but furthest away is wrong

1 Answer

0 votes
There was an unfortunate incident while programming, causing distance calculations to become wildly wrong. It's been fixed already, but the incorrect values will be shows until the next time your Profile Statistics page is regenerated.
by pinkunicorn (Moderator) (158k points)
Thank you for fast responding! Tomorrow I will check the changes.
I'm sorry but after refreshing and checking Profile Statistics the situation is still the same:

The item "Furthest cache found:" shows 9,594.57 km, TAKE OFF TO THE RAINBOW’S END, GC1YTJ2

This cache lies in Iceland and is NW 2568.5 km from your home

My real furthest cache found lies in Vietnam.
Did the "data from" date at the top of the page have today's date on it?
Thank you for your reply.
Date on the top of the page is "Daten vom 2020-01-21"
This is always the first what I do when I open the ProfileStats page: to look whether it's the today's day.
The problem (distance shown is ok, but cache indicated is wrong) exists since two days.
This is the status:
Furthest cache found:    9,594.57 km, TAKE OFF TO THE RAINBOW’S END, GC1YTJ2
Apparently we only fixed half the problem last time. We've now fixed a similar problem in a different spot.
Now it works fine - again!
Thanx for your support!
...