I have not been able to figure out a consistent behavior for walking trails. Addresses I've tested sometimes route to the end of the trail, then don't, then do again. Waze has never to my knowledge really explained what is the intended behavior for walking trails.
This is very difficult for me to test, as address searches in general have recently changed for me. They now route to the street in the address for me in the client.
My standby test has been to 1600 Ritchie Hwy, Arnold, MD 21012 as discussed here
. Currently due to waze actually using the street name as the destination, the client gives me a route to Ritchie Hwy even though both Baltimore Annapolis Blvd and the B & A Trail are closer to the pin. However, the live map routes
some where near the end of the trail.
I don't see as many issues reported with walking trails anymore. But some failures to get any route still seem to occur when the route is near a long walking trail. If I try to route to 1820 Wiehle Ave, Reston, VA, I can't get a route in the live map as discussed here
. But the client now routes me to a point on Wiehle Ave.
I think I remember that at one time waze stated that intended the routing to work like the diagram in the wiki. But I'm not sure I've ever actually seen it work that way. Rather, the routing (when the walking trail effects the routing) seems to be to some point near the end
of the walking trail, regardless of whether other segments come close (or ever cross) the walking trail in the middle.
This walking trail behavior has been unpredictable. I know others have attempted to use it as you have to get good routing to parking lots without success
. I wish we could predict the behavior of walking trails better and use them to some benefit.