Thanks for your input. This is exactly the feedback we are looking
for. Bike Paths ARE currently included in the trip planner, but
sometimes there are glitches in the network we are building that don't
allow access to these resources from surface streets. The original
network was built without regard to how bicycles travel, and that is
what we are trying to capture/accomplish here, so this kind of
information is critical.
Can you give me your specific address so that I can run it and see why
you weren't routed onto the bike trail?
Thanks for your input and support.
Mark
It should know about the Eastside trail, though. If you can post some
addresses that demonstrate what's happening, we might be able to give a
more scientific reason as to why it routes you the way it does. (Note:
the addresses don't have to be for your home, work, etc. if you don't
want to post those, just some that give basically the same result)
A general answer is that the TP is set up to take a kind of
middle-of-the-road approach to finding a route: it tries to use the
regional bike network (Metro's Bike There map
<http://www.metro-region.org/article.cfm?articleid=218>) without going
to far out of the way. Similarly, it tries to stay on streets with less
traffic and avoid hills-again without going to far out of the way
(which is also why it picks "red" streets sometimes).
One of the next big thing we are planning to roll out is the ability
for users to select a route preference-safer/faster/flatter/etc. We
have the framework for this in place; we just need to work out some
details. In a future release, we'd like to offer more advanced user
options and the ability for users to save profiles.
This might be a preference thing but I thought I would throw it out
there.
Ryan