WA state DeLorme checker

I'm trying to reconcile a difference in the PGC WA state DeLorme checker data and that from GSAK. A user has a find that PGC says is on Page 34 but Cachly which uses GSAK data says is on page 35.

I don't know the original source of PGC page boundary data for WA state. The true authority would be to get a WA printed DeLorme atlas and see what it says.

Here is a look at Cachly/GSAK data for pages 34 and 35.
48.499858,47.983164,-120.709541,-121.251229,Page 34
Page 34 W range is between -120.709541,-121.251229

48.499868,47.983182,-120.167858,-120.709549,Page 35
Page 35 W range is between -120.167858,-120.709549

Page 34: GC3QQ5W - Bridge Creek Detour is the problem cache with coords of
48.496067, -120.708517

Cachly sees page 35 because
-120.708517 is outside the Page 34 W range -120.709541,-121.251229

We are looking at a difference of 0.001024. I doubt that the DeLorme atlas lists coords to this accuracy so one theory for the discrepancy could be rounding errors in calculation. - just speculation.

Can you help me figure out what is correct and the source of the PGC polyset data?
Thanks, Rich

In regards to a challenge I would say that the cache page is the true authority, not a random delorme atlas. The cache page has a .kml available for download which you can map in Google Earth. Mapping the .kml from the cache page and the coordinates of the cache you mention (GC3QQ5W) shows it's clearly on page 34 and in a similar position to where it appears when making a visual comparison of the cache on geocaching.com map vs the delorme page location on the map in the checker. See image from Google Earth below.



The coordinates used for page 34 in the .kml are these:
[ -121.249999908199996, 48.500000057900003 ], [ -121.249999935100007, 47.983333375500003 ], [ -120.708333305699995, 47.983333408199996 ], [ -120.708333263, 48.500000063400002 ],

The coordinates used for page 34 in the checker are these:
"Page 34":{"rect":[47.98333,48.50000,-120.70833,-121.25000]},

There's a difference in coordinates between these two that looks like the checker-tagger rounded the numbers correctly to get five decimals instead of the fifteen used in the .kml before using them in the checker. Why these numbers don't match the ones used in GSAK/Cachly I have no idea, but as I said, the .kml linked on the cache description is what I would consider the actual authority in the matter of a challenge cache like this. And since the checker matches this .kml while GSAK/Cachly does not match this .kml. I would consider this an issue with the GSAK/Cachly-data.

Thanks. I got the data I needed from the challenge owner