Bike Forums

Bike Forums (https://www.bikeforums.net/forum.php)
-   Fifty Plus (50+) (https://www.bikeforums.net/fifty-plus-50/)
-   -   Bike Computer with GPS (https://www.bikeforums.net/fifty-plus-50/795447-bike-computer-gps.html)

jimmuller 02-27-12 12:49 PM


Originally Posted by John_V (Post 13904877)
When my wife and I start cycling in areas of Florida and the U.S....

Both Florida and the U.S.! Is that an inclusive or exclusive and? :)

Dudelsack 02-27-12 01:48 PM


Originally Posted by jimmuller (Post 13904736)
Here are a few random thoughts, offered after the realization that I haven't been able to follow a lot of this discussion.

First, about using a GPS unit to track mileage. A GPS unit is a sampling device. So is a cyclomputer but with GPS the sampling interval is very much greater. Also a cyclomputer does a linear measurement whereas GPS attempts to localize in 3-D, or at least 2-D. Here's what all this means.

Suppose you ride in a straight line. Your GPS samples at some interval, but also places you as moving sideways by its average positioning error. If your lateral sampling error is half the sampling distance, i.e. evenly distributed between left and right, your "distance travelled" appears to be 11% greater than your forward progress. On the other hand, successive position samples can be such one is some distance from an upcoming turn, and the next is some distance around the turn. The distance travelled will see you as having cut off the corner. So your apparent distance travelled depends on the reliability GPS reading, not always great through trees, and your particular route. It isn't surprising that GPS does not produce readings precise enough for training.

There seem to be many possible goals for a GPS unit. One is to track where you have ridden. Another is to provide instantaneous readouts of current speed and distance travelled. An inexpensive cyclomputer can do that. Yet another is to carry maps, and display them when required. Paper maps can do that, although not as conveniently. Yet another is to show you where you are, either continuously or when asked occasionally.

For riding through unfamiliar territory, especially while touring, the map access and "where am I" features would seem important, which is why I'm interested. I'm not sure maps need to be displayed continuously, which suggests that neither battery life nor display legibility are quite so critical.

Unfortunately GPS-for-bike discussions end up all sounding the same. I'd really like to see discussion driven by the intended uses, and then specific products recommended based on that discussion. Thanks!

I'm working on a migraine and this post just made it worse.

It's not your fault.

Digital Gee 02-27-12 01:57 PM


Originally Posted by Dudelsack (Post 13905237)
I'm working on a migraine and this post just made it worse.

It's not your fault.

A perfect recipe for a tombay. Just sayin'

Dudelsack 02-27-12 02:08 PM


Originally Posted by Digital Gee (Post 13905277)
A perfect recipe for a tombay. Just sayin'

That might be part of the problem. It's beautiful out there....and I'm in here.

jimmuller 02-27-12 03:08 PM

1 Attachment(s)

Originally Posted by Dudelsack (Post 13905237)
I'm working on a migraine and this post just made it worse.

It's not your fault.

Sorry about your migrane. That's just the way the world works.

Here's a pic to illustrate, purely hypothetical, mind you.
http://bikeforums.net/attachment.php...hmentid=239118
On the left is an example of how lateral errors can increase the apparent distance travelled. The numbers shown assume that for every increment x travelled forward there is a lateral error x/2. This isn't a true picture but one can suppose that there is a "typical" sampled interval both laterally and forward. The forward errors from sample to sample will cancel because for each interval too short the next will be too long. The lateral errors will randomly swing left and right. With the x/2 assumption one appears to travel the hypoteneus of the triangle.

On the right is an example how sampling the course results in corners being cut off. The apparent course from point to point is less than the actual distance travelled. The greater the distance between points, the greater the possible error.

On a real course the apparent distance travelled could be either less or more than actual, depending on how tight the curves were and how precise the GPS positions were. In any case, one would surely like better than +/-6% precision for training purposes.

volosong 02-27-12 03:22 PM


Originally Posted by Dudelsack (Post 13904460)
I purchased an Edge 500 off Ebay for $200, free shipping...

Good score! You did well.

byte_speed 02-27-12 08:42 PM


Originally Posted by jimmuller (Post 13905623)
Sorry about your migrane. That's just the way the world works.

Here's a pic to illustrate, purely hypothetical, mind you.
http://bikeforums.net/attachment.php...hmentid=239118
On the left is an example of how lateral errors can increase the apparent distance travelled. The numbers shown assume that for every increment x travelled forward there is a lateral error x/2. This isn't a true picture but one can suppose that there is a "typical" sampled interval both laterally and forward. The forward errors from sample to sample will cancel because for each interval too short the next will be too long. The lateral errors will randomly swing left and right. With the x/2 assumption one appears to travel the hypoteneus of the triangle.

On the right is an example how sampling the course results in corners being cut off. The apparent course from point to point is less than the actual distance travelled. The greater the distance between points, the greater the possible error.

On a real course the apparent distance travelled could be either less or more than actual, depending on how tight the curves were and how precise the GPS positions were. In any case, one would surely like better than +/-6% precision for training purposes.

What you say is correct, but I think my Garmin Edge 500 does not wander laterally nearly as much as your example. The plots of my ride look like the points fall quite close to the actual path, even at fairly high zoom.

Now for altitude, your argument is 100% true. If you use the raw data directly, the total ascent might be twice what is displayed on the unit (which has data smoothing for altitude). It may smooth the distance data too, I never thought of that, but I doubt it is needed.

I have the speed cadence sensor, but I haven't figured out how the data from the sensor is used. I have the unit set to auto stop at speeds less than 3 mph. The unit goes into autopause occasionally on climbs of about 6 mph through tree lined ascents. I am pretty sure it is losing the GPS signal and pausing because it thinks I have stopped.

I would think it would use the more accurate speed sensor over GPS, but it appears to me that GPS rules until the signal is completely gone. Since the plots don't show any sign of the pauses, it may be that the stored data uses the wheel sensor, while the display sticks to GPS.

jimmuller 02-27-12 09:49 PM


Originally Posted by byte_speed (Post 13906971)
What you say is correct, but I think my Garmin Edge 500 does not wander laterally nearly as much as your example.

Oh, I'm sure my example was extreme. After all, it did assume the error was equal to the sampling interval, which is highly improbable. I was merely trying to illustrate how there could be error at all, both high and low.

There is one more source of error I didn't show. That is when you get one or more more bad positions because of momentary poor satellite readings. One bad data point which misplaces you by half a mile can ruin your whole day!


All times are GMT -6. The time now is 08:53 PM.


Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.