The documentation of trail_visibility for a very long time featured a picture where there was NO trail visible and called that trail_visibility=good because 25m farther there was a visible trail (for those with basic sense of direction and a map at hand.) This picture recently got removed from the documentation. Reading along her Confused with tracktype usage - #105 by Joan_Apeu I learned, that it is still shown in the article describing the visibility key.
I just could, as others did (did not bother to find out who), just remove it there. I though think the whole section should be removed, after all, It is used on 0.00% of highways. But this is certainly in for a lengthy debate.
The section describes *:visibility=. That’s also not really used on highways: Search results | OpenStreetMap Taginfo I’d say get rid of it, maybe after speaking to the person who added it.
(trailblazed:visibility has its own documentation, and so do the seamark tags)
Thank you for your scrutiny. I understand that as confirming that the addition of the full trail_visibility table in a subsection of the visibility key maybe was a nice try to create one more way to map the same thing for, what features actually, other than trails? And I further understand, that this other way found no uptake in the mapping community after five or six years. So I removed the table. Now to tell that in the other topic…