In article <
[email protected]>,
Solvang Cyclist <
[email protected]> wrote:
> Obviously we have differing needs/desires for a GPS device. I would
> prefer to have only one device on my bike.
So would I, but it's getting to be impossible. I already have my cell
phone with me. I also bring my iPod sometimes. If it's dark, I have
lights. While I could add a big honking GPS display to the mix, I would
much rather use one of the displays I already have with me.
> With the exception of a map
> and maintaining a route, everything that a GPS can provide can be done
> by a cheap cycle computer. I can always map my routes after I return
> using a site such as bikely.com.
This is where our needs obviously differ. I'm of the opinion that most
of the "instant" feedback is useless, but logging data over time paints
a rich picture. Your cheap bike computer won't be the best device to
tell you how you've been improving, say, on a particularly tough hill.
It won't be at all helpful in trying out different routes and seeing
which sections are faster on average.
> Instead, if I'm going to add a GSP, I
> want it to provide a moving map display. The rest would be simple to do.
While that can be handy at times, would you *really* say you need to be
looking at a moving map 90% of the time you're on a bike? I still think
a simple logger is a great start, and if I'm lost and need to see a map
I could whip out my cell phone.
--
My personal UDP list: 127.0.0.1, 4ax.com, buzzardnews.com, googlegroups.com,
heapnode.com, localhost, x-privat.org