You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 27, 2024. It is now read-only.
The max walk parameter can currently be set via the Settings. The default OTP server behavior is to return an intinerary, even if it exceeds the max walk parameter. So, we're currently returning trips to the user that exceeds their preferred max walk without letting them know this.
We should show a warning to the user when the walk distance of the trip exceeds the walk distance parameter.
Here's an example of how this warning looks in the Leaflet UI:
The text was updated successfully, but these errors were encountered:
Reported by user on the OTP dev list:
https://groups.google.com/d/msg/opentripplanner-users/ZjG49IwIvgo/U9IpGA_ABwAJ
The max walk parameter can currently be set via the Settings. The default OTP server behavior is to return an intinerary, even if it exceeds the max walk parameter. So, we're currently returning trips to the user that exceeds their preferred max walk without letting them know this.
We should show a warning to the user when the walk distance of the trip exceeds the walk distance parameter.
Here's an example of how this warning looks in the Leaflet UI:
The text was updated successfully, but these errors were encountered: