check for tagvalue containing left/right or up/down when changing direction of a way

[skyper]

Please have josm check for left/right in tags and tag-values when changing the direction of a way and offer to change it like it is done with oneway=*

[stoecker]

This is already implemented. What specifically do you request.

[skyper]

Replying to stoecker:

This is already implemented. What specifically do you request.

Then it does not work:
id: 23024460
footway=right
can change direction silently.
should offer to change to footway=left

also please check for cycleway:right=* and so on

[mjulius]

left/right in keys on ways is checked for and should work. left/right in values is not checked for.

[stoecker]

If I remember correctly, the last time this was requested there existed not one established tagging standard, where left/right in values was used. Is there now something standardized?

[skyper]

No, you are right.
But there are quite a lot of proposals about that and I see even more possibilities like (embankment and cutting).
Any way, that there is nothing yet establish does not mean that no one is using it.

[skyper]

Anyway I think this would be a nice feature to save information and one big plus for JOSM.

[stoecker]

When I say established standard, then I mean either:

• used in real datasets (e.g. provide tagwatch hits)
• documented in MapFeatures

Last time neither of these two existed.

I don't like to support anything when there are no use cases at all.

[mjulius]

Well, according to osmdoc there are 709 ways tagged footway=right and 467 ways tagged footway=left. And, there is a proposal for footway=both|left|right|none.

[skyper]

Replying to mjulius:

Well, according to osmdoc there are 709 ways tagged footway=right and 467 ways tagged footway=left. And, there is a proposal for footway=both|left|right|none.

There is even more right now: (2010-02-23 05:45 tagwatch europe) always left/right

alley			28/27
barrier:bannister	2/4
barrier:fence		2/3
barrier:geländer	3/-
barrier:guardrail	-/2
barrier:handrail	2/-
barrier:hedge		4/8
barrier:leitplanke	10/7
barrier:wall		5/-
bicycle			lane_left (5)
bicycle:footway  	4/-
bus			2/-
bus_stop:side		1/1
cutting			6/10
cycleway		137/228	lane_left/right 37/239	track_left/right 48/46	right_lane 9
direction_hint  	1/11
embankment		20/19
exit  			12/34
foot			21/9
footway 		1219/1661
handrail		5/2
landing_point		1/-
lane:ends		1/1
natural:tree		9/19
natural:trees		3/1
parking			6/11
parking_lane		15/7
parking_lanes		1/2
passing_place		5/4
path			11/16
platform		2/2
save_way		left/right_side 1/2
segregated		4/3
side			85/113
sidewalk		15/27
towpath			15/12
track			25/34
tracks			2/-
turnout			5/-

Maybe not all these tags apply to ways but a lot do.

I am turning this into a defect, because all this information is wrong if a way is reverted.

[skyper]

Please,
this works well with direction info in tags and roles, but not with any tag-values.
like footway/cyclewayembankment..=left/right, direction=up/down

[skyper]

There exist also a tag incline=up/down which I personal do not like but it was accepted.

[stoecker]

Ticket #4664 has been marked as a duplicate of this ticket.

[skyper]

At least incline=up/down was accepted quite some time ago.

Please add this feature. It is almost coded, you only need to check also for values, not only for the tags.

[skyper]

also direction=up/down was accepted.

[skyper]

Ticket #4251 has been marked as a duplicate of this ticket.

[stoecker]

Please do not change priorities which have been change by admins. This is not critical. The above numbers show that these tags are actually not used widely.

[skyper]

Replying to stoecker:

Please do not change priorities which have been change by admins. This is not critical. The above numbers show that these tags are actually not used widely.

There is no editor which supports these values and one arguement against footway=* was that there is no editor supporting it. That is why not many users are using them.

Who is admin ? - I might know it but not erveryone knows.

At least direction=up/down and incline=up/down are on the wiki.

[bastiK]

Who is admin ? - I might know it but not erveryone knows.

Yes, but that's enough because you are the only one bumping tickets by raising the priority. I can imagine it must be frustrating if nothing happens for a long period of time, but there is not much you can do about it. Our developer resources are very limited and there are hundreds of things that need to be improved. This is only one of them and it is by no means a critical bug.

As you pointed out it is a relatively easy programming task, so if you like you can try yourself. Good user feedback is valuable and always welcome, but don't expect us to concentrate on your problems with the software only.

[stoecker]

(In [3190]) fixes #4080

[skyper]

Thanks a lot

I fully accept your arguments.
The problem I often focus that I do not know if I am the only one with that problem or if it effects more. Seems to me that users do not give a comment if a bug is already reported.

I am working offline 80 % of the time. While being offline it is quite hard to contribute to josm.
Last month it was even hard for me to contribute to osm, cause of some nasty bugs in JOSM. I had to manage hundreds of conflicts.
Now it is working quite well and I might have some time to start coding or at least help with documentation.

Cheers

[bastiK]

Would be great, I'm looking forward to it!