-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
forward/backward settings #569
Comments
i pushed updated tests to the feature/opposite_direction branch, and updated the testbot profile, but there seems to be a few problems, so i could not make tests pass. there also seems to be some regresssion on other tests, like "Scenario: Routing on a oneway roundabout # features/testbot/basic.feature:237" |
handling maxspeed:backwards seems somewhat akward, because of they way the backward speed defaults to way.speed if you don't set it. now that way.speed and way.backward_speed is set separately it seems like way.direction could be eliminated? we might need to be able to set the mode for each direction, for handling pushing of bikes against oneways. |
would be easier to store (when needed) two plain ways instead of one with backward settings? |
when handling impedance (weight) in lua scripts, this could also be different in the forw/back direction. |
We should have such discussions on the mailing list. The issues get unreadable this way. |
maxspeed:forward and maxspeed:backward currently use a simple 'tonumber' conversion in the lua scripts. Wouldn't it be better to use parseMaxspeed()? |
i think there is a bug regarding the backward direction (backward_speed might be overwritten by accident) not a direct fix / but something more like: |
Emil Tin [email protected] writes:
+1 for that one but maybe we really should take that to the mailing list? |
@emiltin can we close here? |
ability to set speed and other settings differently for the forward/backward direction.
a specific use is pushing bikes against oneways:
#78
references:
724e96f#commitcomment-2460689
The text was updated successfully, but these errors were encountered: