Opened 2 months ago

Last modified 8 weeks ago

#21602 new enhancement

Role verification problem

Reported by: Filip009 Owned by: team
Priority: normal Milestone:
Component: Internal preset Version:
Keywords: recreation route member role route_marker Cc:

Description (last modified by skyper)

Please add to Bicycle route preset a route_marker node.

In Slovakia we use it, and is not good when JOSM reports problems with this.

You can check if in this node added to relation is used tag bicycle=yes, this is bigger problem.

Attachments (1)

role_verification_problem.jpg (20.9 KB) - added by Filip009 2 months ago.

Download all attachments as: .zip

Change History (5)

Changed 2 months ago by Filip009

comment:1 Changed 2 months ago by skyper

Component: Core validatorInternal preset
Description: modified (diff)
Keywords: recreation route member role route_marker added

Despite validator producing this warning the code is in defaultpresets.

Well, documentation of information=route_marker and information=trail_blaze is very little without own wiki pages for the tag.
Has this usage been discussed somewhere?
Can we get it documented first?
Do you have an example and which role do you use? I do not think it is smart to add it without role.

comment:2 Changed 2 months ago by skyper

Owner: changed from team to Filip009
Status: newneedinfo

comment:3 Changed 2 months ago by Filip009

We have discussed it in Slovak OSM community, but whole thread is in Slovak. We have discussed if these guideposts can be tagged as is shown on the picture. And we have make conclusion, that we will tag it like it is shown in the last picture from which I have edited the osm wiki page for slovak cycleroutes.

I mostly use it without role, but when I add a role "guidepost" to it, it is saying me the same error.

comment:4 Changed 8 weeks ago by skyper

Owner: changed from Filip009 to team
Status: needinfonew

Yes, the warning combines roles, type of object and tags on the object. :)
Maybe, an external preset can be used to overwrite the rules but I have not tried this, yet.

I like to have this discussed on a wider audience and appropriate channel. I have no problem with the tagging of these objects but route relations and their members + roles is another story. Personally, I'd prefer a new role marker for all recreation route relations with a proper proposal. One thing to keep in mind is the members count as relations with too many members get hard to handle and are a burden on performance.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to Filip009
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.