LoRouter MTB profile: inconsistent barrier handling
Hi. It seems the LoRouter MTB profile (online, offline, web), handles barriers differently than the other cycling or walking profiles. I've found this with two different types of barrier: barrier=gate (alone, no other tags), also barrier=gate, bicycle=yes, foot=yes.
All the profiles except MTB seem to let you right through the gate, even without the extra two tags. But MTB never lets you through, even with the explicit access tags.
I'm not sure what a router should do with a simple barrier=*. (In my region, we have lots of simple barrier=gate, with true access really being determined by the adjacent ways. In other words, it might make most sense to consider all barriers transparent for bikes and walkers.