Fix wrong one-way identification in the bike profile
* upgrade to api version 4 * set bike pushing speed to 4km/h and add mode change penalty * set cycleways for two-way and one-way roads according correctly * add changelog * adjust tests according to change of the walking speed * adjust tests according to new behaviour of opposite, track and lane in one-ways * refactor the cycleway identification * comment to understand weird counterintuitive testcase * adjust sliproad test because walking speed is now slower
This commit is contained in:
committed by
GitHub
parent
873e766d2e
commit
bdb116afe5
@@ -141,5 +141,12 @@ Feature: Bike - Oneway streets
|
||||
| highway | oneway | cycleway:left | cycleway:right | forw | backw |
|
||||
| primary | yes | | | cycling | pushing bike |
|
||||
| primary | yes | | track | cycling | pushing bike |
|
||||
| primary | yes | track | | cycling | cycling |
|
||||
| primary | yes | track | track | cycling | cycling |
|
||||
| primary | yes | track | | cycling | pushing bike |
|
||||
| primary | yes | track | track | cycling | pushing bike |
|
||||
|
||||
Scenario: Bike - Left/right cycleways on any oneways
|
||||
Then routability should be
|
||||
| foot | oneway | cycleway:left | cycleway:right | forw | backw |
|
||||
| no | yes | track | | cycling | |
|
||||
| yes | yes | track | | cycling | pushing bike |
|
||||
| yes | -1 | track | | pushing bike | cycling |
|
||||
Reference in New Issue
Block a user