JustinZ

Google Earth can also help you by finding the best approach to the cache area. A lot of caches in parks are hidden in the back of the part up against a fence. When you drive to the site, your GPS will tell you that the closest road to the cache is the road on the other side of the fence! Then you have to figure out where the park entrance is so you can actually find the cache. Google Earth can help you figure this sort of thing out ahead of time.

To add a couple more data points to this discussion, I found a two benchmarks with my Legend CX this weekend, and here are my results. Benchmark HZ2433: The official coordinates are N 38° 00.966 W 084° 26.346 My CX reported N 38° 00.965 W 084° 26.348. It claimed its accuracy was +/- 8ft. Benchmark AA4603: The official coordinates are N 37° 57.486 W 084° 29.468 My CX reported N 37° 57.485 W 084° 29.474. It claimed its accuracy was +/- 10ft. So the first reading matches the benchmark very closely. According to the calculator on this page, the second reading is off by about 29 ft to the west of the benchmark.

The same thing happens on my Legend Cx. It must be a bug of some kind. Justin

I had the same problem with my new Legend Cx a few days ago. I found that the points show up on the map at the 300 ft resolution. I am suspecting, though, that my real problem is that I have not yet installed the City Navigator software (waiting for version 8). Since I see the "Custom POIs" icon in my Find menu, but no "All POIs", I'm thinking that perhaps custom POIs rely on having the detailed maps loaded. I'll know for sure when v8 arrives. Could this be your problem as well? Justin

I'll bet that it is true, since the GPSr's without memory cards are not listed in the "Recommended Units" list for v8. Justin