Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warn user when over max walk distance #306

Closed
novalis opened this issue Jul 18, 2011 · 4 comments
Closed

warn user when over max walk distance #306

novalis opened this issue Jul 18, 2011 · 4 comments

Comments

@novalis
Copy link
Contributor

novalis commented Jul 18, 2011

[from whuber]

There should be an alert saying why it is being suggesting that you walk further than the stipulated max walking distance. For instance: "No trips were found that met your criteria. Consider the following other options" or something like that.

@novalis
Copy link
Contributor Author

novalis commented Jul 18, 2011

{{{
#!html

}}}
This ticket has been referenced in ticket #353:

''...h constant edge weights (per mode). This can be implemented in conjunction with #306 and #359.

This also suggests that all components of weight (e.g. turn costs)...''

--andrewbyrd

@novalis
Copy link
Contributor Author

novalis commented Jul 18, 2011

{{{
#!html

}}}
This ticket has been referenced in ticket #353:

''...d (temporarily) to a hard limit, pending a more elegant fix to be combined with #306 and #359.''

--andrewbyrd

@novalis
Copy link
Contributor Author

novalis commented Jul 18, 2011

{{{
#!html

}}}
This ticket has been referenced in ticket #371:

''... limit in AStar. They should be handled more intelligently, in conjunction with #306 and #359.''

--andrewbyrd

@abyrd
Copy link
Member

abyrd commented Jan 27, 2014

Itinerary objects now have a public boolean walkLimitExceeded field, so it's just up to clients to interpret this field and warn the user. Closing.

@abyrd abyrd closed this as completed Jan 27, 2014
kalon33 pushed a commit to kalon33/OpenTripPlanner that referenced this issue Oct 13, 2019
…egex

Make travis regex matching ready for next decade
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants