The routing currently guide motorcar users onto motorways through ways that should not be used, e.g. here or here.
Doesn't sound like a tagging issue as both ways are tagged with access=emergency and have been modified 3 years ago for that very reason. They also both go over a access=emergency + barrier=gate node. Other routing engines like OSRM or GraphHopper don't use those ways with a car profile.
It's a pity, but we'll support access/barrier restrictions only in 7.3 version (currently under a heavy development, 1.5 month until the planned release).
I'm still getting routes through barriers on version 7.3.5-Google. Example (that's here ). Also, in addition to access and barrier tags, I think highway=track (also in the linked example) should be excluded aswell unless the the user explicitly allows it.
The routing currently guide motorcar users onto motorways through ways that should not be used, e.g. here or here.
Doesn't sound like a tagging issue as both ways are tagged with
access=emergency
and have been modified 3 years ago for that very reason. They also both go over aaccess=emergency
+barrier=gate
node. Other routing engines like OSRM or GraphHopper don't use those ways with a car profile.