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.

0 votes
449 views
https://project-gc.com/Challenges/GCTJYG/2605

The results disagree with GSAK Macro and with mygeocachingprofile.com
in Bug reports by allenmabry (220 points)

2 Answers

0 votes
 
Best answer

I made a new checker https://project-gc.com/Challenges/GCTJYG/59865 but this did not solve the problem.

Eventually I found out that the boundary data for the US at the moment is from "TIGER data" from census.gov.

This is causing a mismatch between the mapdata and cache data 

https://coord.info/GC936F is according to de cache data in United States / Kansas / Morton County (KS)

However, it's likely that PGC will switch to using OSM data for USA as well the coming months.

by vogelbird (Expert) (56.5k points)
selected by allenmabry
Thank you for the detailed explanation!
0 votes
There is a mismatch in the boundary data, the checker does not allow for the latest OSM data. After Eastern I will check if I have the correct DeLorme data and make a new checker for you
by vogelbird (Expert) (56.5k points)
...