I am having a problem with a Barricade (barrier=block) on a road that other mapper thinks stops routing

reference barrier here:

It sits on a road (Inman Street) and is not part of the WAY. I noticed the barricade and went to OSM to verify its existance. It was not part of thw WAY (Inman St.) so I broke the way up and made a foot path segment so vehicles could not drive down this street. A fellow mapper changed it (the way it currently is) and said this is all that is needed. I use OSM data and mkgmap to make Garmin maps. The Java code looks at the road, and since the barrier=block is not part of the way, I am still able to route down this road. Should this way be broken up to prevent routing?

Your AI altered my post

The way it is tagged now should prevent routing. You do not need to add a segment of footway in order to prevent routing by motor vehicles.

  1. Please don’t post edit links. Use the normal map links instead.
  2. The barrier node is part of the way (at least it is now).
  3. A node of the way tagged as barrier=* (with access tags as needed) is enough to block routing according to the OSM barrier tagging scheme. The road does not need to be broken up. If the routing software you are using doesn’t recognize that, the fault is with the routing software. (And the example you posted isn’t going to be the only issue.)

What exactly do you mean? There’s no AI changing posts on this forum.

is it about Node History: 5928377007 | OpenStreetMap block?

I dont agree:

This way states highway=residential, speed=25 and no tag indicating the road is not routable. The barrier is a separate node, not attached, or a relation. How would my mkgap software know about this barrier? That is why I alter the way and break it up, so the WAY is not routable.

it is attached to Way: ‪Inman Street‬ (‪1006076351‬) | OpenStreetMap and therefore marked as being barrier on this way

I’m not sure why you say that - the node is part of the way? It looks like standard barrier mapping.

(By the way the advice given earlier was good: please use normal links, not edit links. It’s difficult to follow edit links on a phone, whereas it’s easy to see the tags in normal mode even on a phone).

Also note that all 3 routers featured on osm.org respect the barrier for car routing, sending drivers by a much longer route to avoid it.

From the mkgmap docs:

--link-pois-to-ways

This option may copy some specific attributes of a POI to a small part of the way the POI is located on. This can be used to let barriers block a way or to lower the calculated speed around traffic signals. POIs with the tags highway=* (e.g. highway=traffic_signals) or barrier=* (e.g. barrier=cycle_barrier) are supported. The style developer must add at least one of the access tags (mkgmap:foot, mkgmap:car etc.), mkgmap:road-speed and/or mkgmap:road-class to the POI. The access tags are ignored if they have no effect for the way, else a route restriction is added at the POI so that only allowed vehicles are routed through it. The tags mkgmap:road-speed and/or mkgmap:road-class are applied to a small part of the way around the POI, typically to the next junction or a length of ~25m. The tags are ignored for pedestrian-only ways.

Is anyone using IDeditor? When I select the WAY, there is NO reference to a barrier.

Show me an ID Editor link that shows the barrier is attached to this way

Drag block around you will see it is glued to way as it will also change way geometry (then undo edit without saving)

Also vertex points have grayish not whitish background IIRC.

That is because barrier is tagged on vertex node within way, not on way itself

You don’t need iD to see that connection, it’s enough to use the link mentioned by @Mateusz_Konieczny earlier: Node: 5928377007 | OpenStreetMap, you see on the lower part the way it’s belonging too.