Add OSM node barrier=height_restrictor handling #4872
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Nodes with
barrier=height_restrictor
tags are not handled incar.lua
profile, for example, a barrier node leads to a detour with misleading instructions:http://map.project-osrm.org/?z=17¢er=48.075609%2C11.099442&loc=48.074136%2C11.092565&loc=48.075369%2C11.102929&hl=en&alt=0
PR adds
height_restrictor
tag tobarrier_whitelist
and a check ofmaxheight
tag inprocess_node
function. Also PR addsget_location_tag
method to theosmium::Node
interface.Tasklist
Requirements / Relations
Link any requirements here. Other pull requests this PR is based on?