Originally Posted by
GV27
I think it's pretty darn good for Denver. And I think you're expecting a bit much from a computer, Artkansas. As far as directions go, you're asking it to take in a lot of intangibles - where there are hills, where there are potholes, etc. Especially the bit where you cut across one parking lot, across a strip of grass and then across another parking lot. How the heck is it supposed to know that? How is it supposed to know there's not a fence between the two parking lots? That's asking an awful lot.
[...]
For every person like you (and me) who thinks that MUPs are good and no sidewalks or shoulders is bad, there are "take the lane" folks who would find the lack of shoulders no hinderance at all and would never take a MUP or a sidewalk.
I was impressed looking around where it sees routes I didn't think it would. For example a path that goes right through the entry plaza and between buildings at a local factory, a weird little narrow "sidewalk" that cuts between some back yards and a golf course. It's impressively complete. Doubly so for an initial rollout.
Denver's pretty flat in my recollection.
As for asking too much, I don't necessarily think so. They know the average speed on roads, and they know elevation. So routing based on elevation isn't all that a stretch; they may do it already. A short map I did seemed to favor smaller roads at the cost of a detour, so it may be taking that into account.
They get this info for the normal auto directions by hiring people to drive around. It's not out of the pale to imagine them getting bicycling info the same way, or provide for user generated additions/comments. If a few people draw a path, start adding it to the instructions or something.
It's not perfect, but they have to start somewhere. Glad it's finally up.