Talk:Key:priority road
Jump to navigation
Jump to search
what priority_road=end denotes?
It is placed at the last node of priority road? Or one need to split the last few meters of the road and place the tag here? Should it be applied on both ends? What if the road is just one way, should we split it to three parts?
- We've used it on the applicable last way of the road. The idea is that this is a tag on the way(s). At least the priority_road=designated tag on the road/way should not extend beyond the "end of priority road" sign. If the end sign is used in the country, it's logical that there was at least one intersection between that sign, and the last "start of priority road" sign (although I do know a place where even that isn't true, because the intersection was lately removed). Usually there are other reasons, too, to split the way at that intersection. But maybe my view is a bit biased, because we had already tagged so many other attributes like changes in lane count, overtaking restrictions and roadside parking restrictions, which usually necessitate splitting roads quite often. I'd also state that the split should be after the last "non-end" intersection; any traffic that "enters" the way at the first/last node of that way, is bound to pass the sign because there are no intersections before the end priority road sign. And yes, if it's not dual carriage road and it was drawn as just one way, both ends probably need to be split, so into three parts as you say, and with priority_road:forward=end at one end and priority_road:backward=end at the other end. Alv (talk) 10:59, 6 February 2014 (UTC)
- Thanks for detailed explanation of some issues with this value, however I still do not understand why this should exist. Is not it sufficient that the higway just does not have priority_road=* when it is not priory road anymore. Could you maybe give some examples how this is used? --Jakubt (talk) 00:52, 10 February 2014 (UTC)
- I know this is an old topic, but I share User:Jakubt's confusion. Surely, the last road segment which is tagged as a priority road could be automatically inferred to be the end of the priority road. So why is the special value necessary? --Tordanik 20:58, 18 September 2019 (UTC)
- Completeness, error checking (including errors/omissions in traffic signs) and bound to traffic signs. So not "necessary" for most uses, but includes information that the traffic necessarily passes an end sign. Alv (talk) 04:04, 19 September 2019 (UTC)
- maybe this should rather be priority_road limit? Any start is also an end? As it stands it is rather a value for a node than a way, could be a traffic sign value. A node is incompatible with the current usage on elements —-Dieterdreist (talk) 13:02, 16 August 2022 (UTC)
- Completeness, error checking (including errors/omissions in traffic signs) and bound to traffic signs. So not "necessary" for most uses, but includes information that the traffic necessarily passes an end sign. Alv (talk) 04:04, 19 September 2019 (UTC)
- I know this is an old topic, but I share User:Jakubt's confusion. Surely, the last road segment which is tagged as a priority road could be automatically inferred to be the end of the priority road. So why is the special value necessary? --Tordanik 20:58, 18 September 2019 (UTC)
- Thanks for detailed explanation of some issues with this value, however I still do not understand why this should exist. Is not it sufficient that the higway just does not have priority_road=* when it is not priory road anymore. Could you maybe give some examples how this is used? --Jakubt (talk) 00:52, 10 February 2014 (UTC)