<div dir="ltr">I think your new mapping is correct, as it reflects reality - which is what most matters. You could improve it by curving the cycle path/sidewalk up to the crossing and aligning the kerb nodes to the aerial photo, but that's nitpicking.<div><br></div><div>That said, there's still a problem in that at least one routing engine (OSRM in bicycle mode) still sees kerbs as impassable to bicycles: <a href="https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=55.0123%2C-1.4837%3B55.0130%2C-1.4810">https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=55.0123%2C-1.4837%3B55.0130%2C-1.4810</a> but that's something the routing engine devs should fix (if you feel like contacting them); compare <a href="https://github.com/fossgis-routing-server/cbf-routing-profiles/blob/master/foot.lua#L35">https://github.com/fossgis-routing-server/cbf-routing-profiles/blob/master/foot.lua#L35</a> <a href="https://github.com/fossgis-routing-server/cbf-routing-profiles/blob/master/bike.lua#L40">https://github.com/fossgis-routing-server/cbf-routing-profiles/blob/master/bike.lua#L40</a> </div><div><br></div><div>Even a non-lowered kerb is an obstacle to cycling, but not an insurmountable one, at least to able-bodied cyclists who can raise their bike over the kerb, so it should perhaps have a penalty in routing but not enough to make a 2km detour preferable. That said, the same goes for cars - other than the lowest bodied sports cars, pretty much all motor vehicles are capable of taking a kerb at low speed.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 18, 2019 at 12:35 PM James Derrick <<a href="mailto:lists@jamesderrick.org">lists@jamesderrick.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
After investigating two reports of OSRM routing failures around North <br>
Tyneside, the common factor I can see is barrier=kerb tags added to <br>
highway=crossing nodes intersecting highway=tertiary and <br>
highway=cycleway/ footway ways.<br>
<br>
Here are links to the two map note reports:<br>
<br>
<a href="https://www.openstreetmap.org/note/2030228" rel="noreferrer" target="_blank">https://www.openstreetmap.org/note/2030228</a><br>
<a href="https://www.openstreetmap.org/note/2030238" rel="noreferrer" target="_blank">https://www.openstreetmap.org/note/2030238</a><br>
<br>
To investigate the report, I entered the postcodes given into the <br>
default routing engine on the OSM map and found VERY odd routes going <br>
10x the direct distance, and avoiding very obvious direct paths:<br>
<a href="https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=55.0659%2C-1.4624%3B55.0511%2C-1.4530#map=14/55.0590/-1.4747&layers=N" rel="noreferrer" target="_blank">https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=55.0659%2C-1.4624%3B55.0511%2C-1.4530#map=14/55.0590/-1.4747&layers=N</a><br>
<br>
Personally, I'd not noticed the OSM main map had added several routing <br>
engines as I use separate tools, so have no idea how often the routing <br>
engines update their database extracts but expect the issue to be <br>
visible for a few days.<br>
<br>
<br>
After two examples of bad routing, I checked the paths between the <br>
geolocated points given and found one common factor - barrier=kerb on a <br>
road / footway highway=crossing node.<br>
<br>
<a href="https://www.openstreetmap.org/node/4341572135" rel="noreferrer" target="_blank">https://www.openstreetmap.org/node/4341572135</a><br>
<br>
My hunch is the router isn't familiar with barrier=kerb, so is assuming <br>
BOTH ways are blocked and using an alternate path.<br>
<br>
<br>
It is debatable how a routing engine should interpret highway=kerb tag, <br>
however my own thought is the kerb is not on the highway=secondary - it <br>
is on the highway=footway.<br>
<br>
If anywhere, there should be two nodes on the footway separate from the <br>
secondary to give information to wheelchair accessibility routers.<br>
<br>
<br>
As an experiment, I've removed the barrier=kerb from a highway-crossing <br>
and added two nodes on the cycleway, with the additional explicit tags of:<br>
<br>
barrier=kerb<br>
bicycle=yes<br>
foot=yes<br>
wheelchair=limited<br>
kerb=lowered<br>
tactile_paving=yes<br>
horse=yes (ISTR UK law says cycle = horse!)<br>
<br>
This is rather cumbersome compared with one barrier=kerb tag on the <br>
node, but logic suggests this is more consistent with reality and <br>
current routers.<br>
<br>
<br>
Has any one used the barrier=kerb tag, or is familiar with the inner <br>
workings of OSRM or similar engines please?<br>
<br>
Thanks,<br>
<br>
<br>
James<br>
-- <br>
James Derrick<br>
<a href="mailto:lists@jamesderrick.org" target="_blank">lists@jamesderrick.org</a>, Cramlington, England<br>
I wouldn't be a volunteer if you paid me...<br>
<a href="https://www.openstreetmap.org/user/James%20Derrick" rel="noreferrer" target="_blank">https://www.openstreetmap.org/user/James%20Derrick</a><br>
<br>
<br>
_______________________________________________<br>
Talk-GB mailing list<br>
<a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-gb" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>
</blockquote></div>