Start way check added

[afischerdev]

This is the answer on the issues #600 and #682.

The idea is to place a definition for excludes highways in the profile.
This is scanned at routing start and an array is created with the index of the lookup entry and the lookup value.
The array is then used to exclude the way from the routing.

The test server is prepared for using this feature.
You have to assign a new global rule in the profile - there is no entry for this feature in the profiles at the moment.

assign   check_start_way          = true   # %check_start_way% | Activate a test for the starting way | boolean | noStartWay=route,ferry;highway,motorway;highway,motorway_link

As you see the comment part of the assign has in this case an array with 4 entries - please note, the web client can not check that at the moment, so you don't see the assigned entry in the option window (I guess, some of the RegEx in Profile.js should be changed).
The fourth part of the array contains the excluded entries.

noStartWay= - a fix constant for this new feature
route,ferry - entry for route=ferry
; - more entries comes here

Here the links for the test server:
issue 600
issee 682

[rtwalz]

Just want to say this feature helped me for a project, I really appreciate it :)

[afischerdev]

@rtwalz
Thank you for the info. It is alway good to know that someone is using it - and it is working as intended.

[rtwalz]

I would love a similar way to specify which ways to exclude for the destination, perhaps a check_end_way rule.

My use case is for walking directions. Many urban areas have poorly connected sidewalks, so I would prefer to not start or end at them, but I still want to consider sidewalks for the route. For example, this sidewalk is not connected to every intersection, so Brouter's route goes all the way around and is longer than necessary.

[afischerdev]

@rtwalz
I understand your intention, but don't you think it is better do connect the sideways to junctions? It is hard to say if this sideway is behind a wall or not.