Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quest. Trail_visibility for paths #388

Closed
rindlerblabla opened this issue Jul 8, 2017 · 9 comments
Closed

Quest. Trail_visibility for paths #388

rindlerblabla opened this issue Jul 8, 2017 · 9 comments

Comments

@rindlerblabla
Copy link

rindlerblabla commented Jul 8, 2017

See #385.

Suggestion to ask for trail_visibility for highway=path/bridleway and maybe even track(?). My suggestion is like comments in the other thread purposed to exclude paths that are paved. Also to exclude footways since my experience is that they in general have good/excellent visibility.

Ending up in paths with bad visibility is a problem when using routing in e.g. Osmand, why I think not only relations should be included.

See http://wiki.openstreetmap.org/wiki/Key:trail_visibility

@rindlerblabla rindlerblabla changed the title Quest. TrailT Quest. Trail_visibility for paths Jul 8, 2017
@matkoniecz
Copy link
Member

I am confused by OSM wiki page - see https://wiki.openstreetmap.org/wiki/Talk:Key:trail_visibility#highly_confusing_tag

@rindlerblabla
Copy link
Author

Good to figure that out first. About trail_visibility for tracks as I mentioned above, it's better to use tracktype, which according to #38 already is on the list, so exclude that one as well.

@rindlerblabla
Copy link
Author

rindlerblabla commented Aug 4, 2017

Have now read the wiki myself and for me it's pretty obvious that it's ment for tagging paths not routes. The difficulty maybe is to find good images. Will have a look.

@matkoniecz
Copy link
Member

@rindlerblabla Can you answer at https://wiki.openstreetmap.org/wiki/Talk:Key:trail_visibility#highly_confusing_tag or find somebody who would be able to answer?

@rindlerblabla
Copy link
Author

rindlerblabla commented Feb 25, 2018

Didn't know how to answer the wiki but it says "Part of a classification scheme for hiking trails, but can be used for any type of paths." "This key describes attributes regarding trail visibility (not route visibility) and orientation." I understand what you mean with the values in the table that it's confusing though.

@westnordost
Copy link
Member

I'd close this then. It may be reopened if the definitions on the wiki are clearer. Though, currently they are both highly subjective, plus, I am not sure if this quest should be shown for any path, everywhere.

@rindlerblabla
Copy link
Author

And even the photos on the wiki is a bit unclear. Think it's easy to say if the visibility is excellent or if it's bad/horrible but the values in between is just a mess.

@torhovland
Copy link

While I agree this tag is subjective, I still think it is useful information, and as such, would be a useful addition to StreetComplete. An example of varying trail visibility can be seen here.

As for filtering, it seems this tag could be treated similarly as the mtb:scale tag in #1850, i.e. only be shown for ground surfaces or if smoothness is bad or worse.

@rhhsm
Copy link

rhhsm commented Oct 12, 2023

I've been considering for a long time to revive this proposal, but I agree the wiki entry for the key is too confusing. That's why I opened this discussion about it here https://community.openstreetmap.org/t/tag-trail-visibility-proposed-improvements-for-this-descriptive-tag/97865 It was a very lengthy and confusing discussion without clear conclusions, unfortunately, so I postponed suggesting it here.
As for the selection on which ways (paths, footways and maybe bridleways, I think) to ask it, in addition to ways that are part of a hiking relation, it could be asked for ways that are within a national park, nature reserve, etc. It should not be asked for ways that are paved or are broad (tracks, roads) because these can be assumed to have no visibility problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants