Barrier / gate is not rendered

[brunetton]

Hi, I'm using Organic Maps for a while and I'm SOOO HAPYYY to have found a real open source fork of MapsWithMe 🤩

But yesterday I came across something missing on the map: a barrier that is not rendered:

not rendered

https://www.openstreetmap.org/node/288354527

barrier=swing_gate
bicycle=yes
foot=yes
horse=yes
motor_vehicle=designated

(but rendered on OSM standard):

but this one is correctly rendered

https://www.openstreetmap.org/node/8327476375

barrier=lift_gate
bicycle=yes
foot=yes
horse=yes

[biodranik]

@brunetton what is the value for users to know about the barrier, if it is passable by bicycle, foot, and horse? If they see it on the map, they may decide that it's not passable.

[brunetton]

@brunetton what is the value for users to know about the barrier, if it is passable by bicycle, foot, and horse? If they see it on the map, they may decide that it's not passable.

IMHO any barrier should be rendered. I don't know if there is a compromise choice that would make everybody happy:

• render only barriers with horse=no would make bikes users and walkers feel like they can't pass (while they would probably be able to pass)
• render only barriers with bike=no would make walkers feel like they can't pass (while they would probably be able to pass)

In my case I was looking for a place to go by car, and as the barrier wasn't present on the map I decided to go there by car. But I was surprised to see this barrier that I wasn't able to pass by car (even if it's tagged with motor_vehicle=designated; because when the gate is opened a car can actually pass the gate).

This reminds me a need that I often feel: the need to see the "raw" tags of an object, to have more details. Maybe this would be hidden by default but could be displayed with a little button to push. There are many cases where the tags may be very useful; and quite human readable I suppose. What do you think of this ? (probably off-topic; this would need another issue for a proposal)

[biodranik]

Storing raw tags can be useful, but also can make maps bigger and slower for search and rendering. Probably designated styles for cyclists, hikers, raiders, and drivers can help to draw it only when necessary.

Or we can think about some special rendering.

The one unpassable by car, located on the road, should definitely be rendered. @vng can you please check why barrier=swing_gate is not in the data? They are needed for our routing algorithms. Only tags with motor_vehicle=yes should be passable by car.

[brunetton]

Storing raw tags can be useful, but also can make maps bigger and slower for search and rendering.

Indeed ! I didn't thought that the data used by the map is not the whole OSM data. Make sense of course. Maybe we could imagine a kind of "whitelist" for objects types that could be stored with all tags ... but ... sounds weird.

Probably designated styles for cyclists, hikers, raiders, and drivers can help to draw it only when necessary.

I don't think this could be easy to remember what color is okay for what type of people (cyclists, hikers etc). But maybe this information could be added on the "details" panel of those objects ? (I mean: the surface that comes from the bottom of the screen and display additional information about currently selected object; like gps coords, phone, website etc). Would it be difficult to add dedicated informations for barriers to make it human readable ?

Or we can think about some special rendering.

The one unpassable by car, located on the road, should definitely be rendered. @vng can you please check why barrier=swing_gate is not in the data? They are needed for our routing algorithms. Only tags with motor_vehicle=yes should be passable by car.

I've no idea whether motor_vehicle=yes, associated with barrier=* means:

• motor vehicles can pass through the barrier when it's opened
  • and sometimes there's a chain that can only be opened by some authorized people
• motor vehicles can pass through the barrier any time: the barrier is not blocking for cars

The wiki doesn't precise this as far as I see. Do you know for sure the exact meanings of those tags combinations ?

Thanks !

[meinrad-0]

Hi! Today I learned that barrier=gate has only a very small dot in OM. I think this is very easily overlooked. It might be better to replace the icon with something bigger. This specific case applies to a barrier that has no further specifications concerning who/what can pass. I guess this is often the case. In my specific case the gate was locked so nobody could pass.

The case: https://www.openstreetmap.org/node/3419406372

[pastk]

The wiki doesn't precise this as far as I see. Do you know for sure the exact meanings of those tags combinations ?

Having read the wiki I can second that the whole access thing is quite complicated, access=yes could be overriden by vehicle= or motorcar= etc. My overall impression is it requires the mapper be very knowledgeable and accurate. And this probably mean there are a lot of tagging mistakes.

Taking it into consideration I think its important to render ANY barrier on the map regardless of its "access" tags. If there is a physical structure - then show its there. If the barrier is rendered doesn't mean its closed (or open), but at least it allows the user to prepare in advance - e.g. if in doubt then ask local people, call a friend who've been there etc. before going there by car.

As for the routing I think the gate should be considered passable e.g. by car only if no of access=, vehicle=, motor_vehicle=, motorcar= etc. tags contradicts it. Another good options is to display gates with uncertain status on the route with a special icon similar to e.g. "unpaved road" or "ferry crossing" icon.

[rmtsrc]

I also recently had this issue while hiking. I was walking along a coastal footpath shown in Organic Maps, but came across a big metal barrier with a no entry sign preventing access and noted that I should add it to Open Street Map later, as there was nowhere else to go (being along side a cliff face and next to the sea) I had to walk back and find another footpath.

However, when I looked on Open Street Map a gate had already been placed there and was tagged with access: no, barrier: gate 4 years ago. It also showed the open part of the footpath (which I was on) as a red dashed line, while the footpath on the other side of the barrier was marked with a gray dashed line with access: no on the footpaths tags:

Looking back in Organic Maps it shows the gate as a tiny dot (which I didn't spot while hiking) and the footpath is marked as open on both sides of the barrier:

I think it would be a good idea to show gates on in Organic Maps with the same or similar icon to Open Street Map and also indicate inaccessible footpaths, to help notify future hikers of inaccessible footpaths.

[Misalf-git]

I can see several barrier types around my place but what I don't see is barrier=cycle_barrier cycle_barrier=double Or maybe any cycle_barrier.

Edit: Also, I think in Germany (NRW) it's not allowed to drive on highway=track by car if there is any kind of barrier. I could be wrong, though.

[RedAuburn]

fixed by https://github.com/organicmaps/organicmaps/pull/5018