Handle no_entry and no_exit turn restrictions

[daniel-j-h]

Currently we only handle (fromWayId, viaNodeId, toWayId) turn restrictions and work for handling way-vias is in progress #2681.

What we don't consider at all is no_entry and no_exit which can have multiple from and to ways, respectively - see spec: http://wiki.openstreetmap.org/wiki/Relation:restriction#Members

What we should do is

• detect no_entry and no_exit turn restrictions
• insert multiple (from, via, to) turn restrictions for all from and for all to ways
• add cucumber tests for no_entry and no_exit (might require updating support code)
• update taginfo.json
• update changelog

[MoKob]

@daniel-j-h I just checked taginfo, it seems like there are 5 tags using no_entry, none for no_exit. I guess we can skip on supporting these?

[daniel-j-h]

You need to check for relation=no_entry/no_exit

• https://taginfo.openstreetmap.org/tags/restriction=no_entry 419
• https://taginfo.openstreetmap.org/tags/restriction=no_exit 170

given that these transform to multiple simple turn restrictions I would love to have them in.

[daniel-j-h]

@MoKob with your turn restriction work merged into master what's your assessment here? What specifically needs to be done and can we simply add multiple "simple" turn restrictions for these tags?

[MoKob]

@daniel-j-h yes, we would need to translate the single restriction into multiple ones to allow this.
It requires:

• translating a restriction into multiple node restrictions

  • adjust this to not handle single from/via/to but multiple
  • output multiple node-restrictions for all n*m combinations

• hand off multiple restrictions here