As a part of a project to make OTP more useful for people with disabilities Mele and I have begun to map sidewalks as separate features (from the road). However, the addition of these features has complicated the itinerary. The principle problem is that during a walking leg of a trip, whether the user is routed along the segment that represents the street or the segment that represents the sidewalk, when the trip is executed they are (generally) going to travel on the sidewalk if one exists. OTP doesn't presently understand this so when a walking trip routes from a street to a sidewalk or vice versa it tells you something like "left at street crossing, right on Foo Street (sidewalk)", but during that phase of the trip the user is just continuing along the sidewalk.
Another problem related to this issue occurs when a trip routes along a sidewalk then continues straight into a crosswalk. The crosswalk gets its own step in the itinerary so it reads something like "south on NE 15th Ave (sidewalk), continue on NE 15th Ave (path)". Crosswalks should not have their own step in the itinerary whether the route turns when the crosswalk meets the perpendicular street at its center or continues through to the sidewalk on the other side. In the example above the crosswalk is named, but ideally the crosswalk step will be eliminated from the itinerary whether it is named or not. Finally, if a route travels straight for a number of blocks over multiple sidewalk and crosswalk segments this should appear as one step in the itinerary, however this type of action is presently described as follows "south on NE 15th Ave (sidewalk), continue on NE 15th Ave (path), continue on NE 15th Ave (sidewalk), continue on NE 15th Ave (path)...)
As a part of a project to make OTP more useful for people with disabilities Mele and I have begun to map sidewalks as separate features (from the road). However, the addition of these features has complicated the itinerary. The principle problem is that during a walking leg of a trip, whether the user is routed along the segment that represents the street or the segment that represents the sidewalk, when the trip is executed they are (generally) going to travel on the sidewalk if one exists. OTP doesn't presently understand this so when a walking trip routes from a street to a sidewalk or vice versa it tells you something like "left at street crossing, right on Foo Street (sidewalk)", but during that phase of the trip the user is just continuing along the sidewalk.
Another problem related to this issue occurs when a trip routes along a sidewalk then continues straight into a crosswalk. The crosswalk gets its own step in the itinerary so it reads something like "south on NE 15th Ave (sidewalk), continue on NE 15th Ave (path)". Crosswalks should not have their own step in the itinerary whether the route turns when the crosswalk meets the perpendicular street at its center or continues through to the sidewalk on the other side. In the example above the crosswalk is named, but ideally the crosswalk step will be eliminated from the itinerary whether it is named or not. Finally, if a route travels straight for a number of blocks over multiple sidewalk and crosswalk segments this should appear as one step in the itinerary, however this type of action is presently described as follows "south on NE 15th Ave (sidewalk), continue on NE 15th Ave (path), continue on NE 15th Ave (sidewalk), continue on NE 15th Ave (path)...)
The link below points to images that display examples of each of these issues described above: https://docs.google.com/drawings/d/1XH0PzgMAEMQKRq9fybqVA3-mDqc5OkSJbgKmA2IuIT4/edit