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.

Missing solved mysteries

0 votes
100 views

In October I am going on a big geotrip, so I was refreshing my solved mysteries. I have found a group of 20 solved mysteries that do not show in the solved mysteries list. Now I am wondering what others are missing?

An example is GC6WZ6P.
It has  S41 05.436 E175 14.781 Under rocks at the fixed end of the gate. as the cache note and it has these coordinates entered as corrected coordinates.

The cache note parser does not appear to handle this common form of expressing coordinates. I must have used this before, so I am fairly sure it used to work with these.

In the meantime I am converting the notes on these 20 caches tS 41° 05.436 E 175° 14.781 format, but I have about 500 solved mysteries - I would rather not have check them all!

Addendum: May be a bigger problem. All 20 show just off the coast of Africa in Map Compare, at N0 0.000 E0 0.000 I have used self support to refresh cache notes and individual caches, no change. - refresh cache notes was AFTER I changed cache note coordinates to S 41° 05.436 E 175° 14.781 format.

Looks like a bug in parsing corrected coordinates.

asked Sep 12, 2018 in Bug reports by the Seagnoid (Expert) (34,190 points)
edited Sep 12, 2018 by the Seagnoid (Expert)

1 Answer

+2 votes
 
Best answer

The cache note parsing seems to be correct. The database stores both the note itself, and the latitude and longitude it has parsed from that note, in decimal form.

However, the database table for "corrected coordinates" those you edit with the pen on the cache page says 0.000000, 0.000000.

I can see that we have a total of 3782 corrected coordinates at 0,0 in the database (over all users), so while it seems to be an issue, it doesn't seem to be huge. These are divided between 20 different users. In some cases it might even be a fact that someone has 0,0 as corrected. I do however notice that one user (not you) has 3287 corrected coordinates at 0,0. That's not very likely.

It's hard to say if it's an issue with the API from HQ or an issue in our parsing from just looking at the numbers. I will start by running an update on all these 3782 where we have an active token, to see what happens.

UPDATE 1: You now have 0 caches with corrected coordinates at 0,0. I will go through a few others as well.

answered Sep 12, 2018 by magma1447 (Admin) (208,230 points)
selected Sep 12, 2018 by the Seagnoid (Expert)
Fixed, thank you!
...