Switch on rendering of access tag by default

[joostschouppe]

🚀 feature request

Switch on rendering of access tag by default

The Belgian OpenStreetMap chapter processes more than one complaint per month from people who say a path on their property should not be used by the general public. They generally want us to delete them. But if the path is observable, we explain that it's better to keep it on the map, and (hopefully) correctly map it as private. However, many apps don't show that info clearly on the map. As a community, we're trying to talk to app-makers to take this info in account. Osmand does a great job at showing the info, BUT the feature to show this info is a little bit hidden. The suggestion is to switch this on by default.

So the suggestion is: on new installs, activate the rendering of accesibility by default.

This is of particular interest to hikers and bikers, so perhaps the default could be associated to just those profiles.
However, for cars, the information is becoming more and more relevant too, as more details are getting mapped. The number of driveways worldwide has doubled in the last year or so - and a lot of them are private. Access roads in general can provide useful shortcuts. Users might be annoyed when they are not used by the routing, showing them as private on the map might make it easier to understand routing choices. The same layer also contains toll road info, which is also always nice to know.
For 4WD vehicles the info is also of particular interest.

[vshcherb]

I tend to disagree cause it needs to come with explanation. It's 1 story if you enable something and starts to see new dashes / strange lines and completely another if app uses it by default without proper introduction.
If you want to share within specific group it's better to create profile: OpenStreetMap Belgium and share it within group with proper communication.

I would definitely agree that we need to render more icons that could explain but different types of dashes are not very explanatory .

[joostschouppe]

I understand your point. Though red dots on top of a path are pretty self-explanatory IMHO. To realize blue means destination and purple is with a fee, yeah that does take a little more time.

(note that it is exactly the difficulty of communicating to data users, in this case hikers and bikers, that is the difficult part. Hence why we are talking to different map developers to make it more obvious when a path isn't for general use. Different solutions are possible, like showing them only at high zoom, overlaying access icons, not showing them at all,...)

[vshcherb]

To do:
Icons needs to be clickable (POI)

[vshcherb]

• Add propagateToNodes for all sections OsmAnd-tools#692 (comment) needs to be implemented for good rendering

[dmpr0]

Review - 2

• Unable to find No access icons

[johnpercy]

Toll roads seem to be permanently on for me except for low zoom in this commit.
I think UniRS will also need the same treatment as Touring to get access and tolls to work again

[xmd5a2]

@johnpercy I've checked UniRS and it already works as expected

[xmd5a2]

@dmpr0 see #10983 (comment)

[ivanPyrohivskyi]

New access icons will be available in the new December 2023 maps.
For test need regenerate map.

[dmpr0]

Review

• Disable red circles by default, only "Stop" icons should be visible - red circles are fine with more details option on

---

Screenshot

• Context menu doesn't provide any relevant information - is it possible to fix ?
• Next task: support conditional tags?

[vshcherb]

Detection border points to place stop icons:

1. Most complex and correct part that stop icons shouldn't be placed on the OSM node but not in the middle between OSM Way segments. For example "T"-intersection and "I" is a private road, we shouldn't place stop icon on intersection as it confusing.
2. Correct detection border point (as OSM node): it's a point that has intersection of "private" and "non-private roads". To get it working correctly all roads need to be analyzed which is very significant performance implication.

[vshcherb]

This looks definitely incorrect, so it's a question whether we are ready to release this feature.

[xmd5a2]

All commits were reverted