When using analysis functionality (specifically isochrones) we would expect the same on-street mode to be used for all stages of routing, yielding smooth-edged isochrones.
Observed behavior
The chosen street mode (bike or car) is used in the initial routing to find travel times to street vertices, but the walk speed is used for the final traversal of the street destination itself, for the last leg from the street vertices to the sample points. This creates "orphaned" isochrone blobs. See discussion at: https://groups.google.com/d/msg/opentripplanner-users/BJSsrHJfHj4/lr1i2CMjAQAJ
Version of OTP used (exact commit hash or JAR name)
Expected behavior
When using analysis functionality (specifically isochrones) we would expect the same on-street mode to be used for all stages of routing, yielding smooth-edged isochrones.
Observed behavior
The chosen street mode (bike or car) is used in the initial routing to find travel times to street vertices, but the walk speed is used for the final traversal of the street destination itself, for the last leg from the street vertices to the sample points. This creates "orphaned" isochrone blobs. See discussion at: https://groups.google.com/d/msg/opentripplanner-users/BJSsrHJfHj4/lr1i2CMjAQAJ
Version of OTP used (exact commit hash or JAR name)
Problem still exists in 1.1 release.