warn user when over max walk distance #306

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

Comments

Projects
None yet
2 participants
@novalis
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

This comment has been minimized.

Show comment Hide comment
@novalis

novalis Jul 18, 2011

Contributor

{{{
#!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

Contributor

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

This comment has been minimized.

Show comment Hide comment
@novalis

novalis Jul 18, 2011

Contributor

{{{
#!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

Contributor

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

This comment has been minimized.

Show comment Hide comment
@novalis

novalis Jul 18, 2011

Contributor

{{{
#!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

Contributor

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

This comment has been minimized.

Show comment Hide comment
@abyrd

abyrd Jan 27, 2014

Member

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.

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 Jan 27, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment