Problems with geocaching provided coordinate checker

[+Kris32]

I had 2 reports from different people that entering correct coordinates into the geocaching provided checker did not go green.

 

I also tried to enter correct coordinates (it was a what3words puzzle) and it did not go green (and then the CO thinking the checker didn't work at all, removed it from the puzzle).

 

Anyone else? I'm on chrome, using laptop.

[+StefandD]

Take a look at the website of what3words: you'll see that every combination is a small square.

In other words: what3words is not as exact as coordinates.

So when the checker is red, try to alter the last digits of N/S and E/W one or two positions.

[+arisoft]

The integrated checker do not verify that coordinates are the same as the puzzle result. Instead it ensures that cooridnates are exactly what the CO reported being the final stage to the reviewer. There are many reasons why these two coordinates do not match, but the reason should always be a difference between reported and solved coordinates. The CO should know if your solution is not the same as the final one.

[+Hügh]

...for example, these four coordinate pairs all share the address powder.soils.issues.

• N 47° 38.938 W 122° 20.887
• N 47° 38.938 W 122° 20.888
• N 47° 38.939 W 122° 20.887
• N 47° 38.939 W 122° 20.888

As a general piece of advice to those creating W3W-based puzzles, always take the final address, convert back to latitude/longitude, and then use the result as the "final coordinates" waypoint (and/or coordinates in Certitude/Geocheck). This will ensure that checkers will correctly accept solvers' coordinates. Geocaching Toolbox’s W3W tool automatically handles this for you: notice that the result coordinates do not match the input coordinates.

 

 

(Same advice applies to Wherigos, if using certain popular Wherigo cartridge along with certain tools.)

[+Kris32]

Maybe this went off the rails, but two people entered in coordinates and got red then later entered in the same coordinates and got green. This was not a what3words puzzle. I own this puzzle. Both sent me the coordinates and they were correct. They later entered the same coordinates and got green after getting red on same coordinates.

Edited January 9, 2023 by Kris32

[+Mingomaus]

Hallo,

seit gestern funktioniert der eingebaute Lösungsprüfer nicht mehr.

Es kommt immer die Meldung:

"Die Recaptcha-Überprüfung ist fehlgeschlagen."

Ich habe verschiedene Brownser ausprobiert und sowohl auf dem PC als auch auf Iphone/Ipad das selbe.

Liegt es irgendwie bei mir oder habt ihr das auch?

Gruss Mingomaus

[+baer2006]

Bei mir funktioniert es.

[+Sorglos02]

Bei mir kommt die genannte Fehlermeldung heute ebenfalls.

Sowohl auf dem PC als auch auf am Samsung Mobiltelefon mit Android :-(

 

[+jennergruhle]

Habe es auch gerade bei einem bereits gelösten Cache probiert, auch die Meldung "Recaptcha Validation failed" bekommen.

[+hcy]

Oh oh, ihr seid alle Bots. Es geht los ... 

[+Sorglos02]

I also have problems with the Groundspeak coordinate checker today.

Alway an error "Recaptcha validation failed."

So I think the "Recaptcha validation" does not work as no window opens "where I have to choose traffic signs or anything like that".

Also in the German speaking forum the problems are mentioned by several users

 

Please check and solve the problem.

Thanks and best regards

Sorglos02

 

 

 

51 minutes ago, Mingomaus said:

Hallo,

seit gestern funktioniert der eingebaute Lösungsprüfer nicht mehr.

Es kommt immer die Meldung:

"Die Recaptcha-Überprüfung ist fehlgeschlagen."

Ich habe verschiedene Brownser ausprobiert und sowohl auf dem PC als auch auf Iphone/Ipad das selbe.

Liegt es irgendwie bei mir oder habt ihr das auch?

Gruss Mingomaus

 

 

 

[+Mingomaus]

Habe am Iphone das WLan abgestellt und jetzt geht es....

komisch

[+Max and 99]

I tried it on Chrome and everything worked as expected. 

[+janrei_]

Derzeit scheint der Lösungsprüfer nur zu funktionieren, wenn man Werbe-Cookies akzeptiert. Das Problem gab es schon einmal und wurde damals durch Neu-Kategorisierung der genutzten Cookies gelöst.

[+SchlauerFuchs007]

Hello,

 

hhis seems to be a bigger problem.

 

No matter what browser I use; nowhere does the Groundspeak coordinate checker work.

 

I also always get the error message "Recaptcha validation failed."

 

The problem should be fixed in a timely manner. Who can be contacted about this?

 

Many thanks and best regards

SchlauerFuchs007 (from Germany)
 

[+Sorglos02]

It seems that the checker only works at the moment when the "advertisement cookies" are accepted.

Please check and also allow the checker when advertisement cookies are not accepted.

[+Mausebiber]

Kein Problem funktioniert bestens.

 

Zu Cookies kann ich nichts beitragen, denn bei mir läuft "I don't care about cookies"

 

 

Edited January 12, 2023 by Mausebiber

[+Team Kipje]

Looks like gc.com is going illegal...

 

According to https://gdpr.eu/cookies/. There are two points that gc.com is not compliant:

• Provide accurate and specific information about the data each cookie tracks and its purpose in plain language before consent is received.
  In the advertising cookies the functionality of the recaptcha is never mentioned.
• Allow users to access your service even if they refuse to allow the use of certain cookies
  The service "Coordinate checker" isn't working if you don't give your consent for advertising cookies.

Earlier on, everything worked, so I think gc.com has something to fix.

 

 

 

[geoawareUSA9]

Merged a duplicate topic.

[+janrei_]

2 hours ago, Team Kipje said:

In the advertising cookies the functionality of the recaptcha is never mentioned.

It is mentioned in the cookie list, look out for cookie names starting with "rc".

 

But you're right, it should be possible to use the checker without accepting advertising cookies. Maybe geocaching.com could use a more privacy-friendly captcha provider that is not repeatedly classified as advertising. Or they could remove the captcha altogether. After all, the checker can only be used by authenticated users.