Originally Posted by
chasmm
Had he loaded the ride as a course, or was it just a ride that he uploaded later?
Some have complained about problems with longer courses on the 500 having problems. We've also been pushing Garmin to give us a better idea of the memory usage so the user community can help figure out some of the bugs affecting the 500. No luck with that so far.
If you use a power meter with the 500, you can set the sampling rate, down to I believe once/second. If you don't use a power meter, the 500 uses an auto-sampling rate, which seems to be about every 3 seconds...but we're not certain about that. Users have complained of the corner cutting, especially under cover, since if the GPS isn't reading when the sample is taken, later when you upload the ride, the software will try to figure out the route.
No pre-loaded course (as far as I know, he doesn't know it can do this), and no power meter. Much of the route was on public roads with not a lot of tree cover, actually there's probably more tree cover in the park I mentioned than on any of the roads, and it's pretty accurate there.