Talk:Proposed features/One way restrictions
If you wish to use an XML parser, don't use tag:l, since that would be an “l” element in the “tag” namespace, not a “tag” element with some special information. Better propose a “side” attribute as in “side="left"” or something like that. --ChristopherCreutzig 18:47, 30 August 2008 (UTC)
I strongly support the proposal to establish a general rule for handling the side dependent features of ways. I think the name 'One way restrictions' is somewhat misleading, as the rule would apply also to features which are not restrictions. I favor the use of a simple colon separated direction specifier (forward/backward or right/left) in the tag name, like for example:
k="maxspeed:left" or k="maxspeed:backward" k="maxspeed:right" or k="maxspeed:forward"
This way there is no need to modify the API to accomodate for side dependent information. And the editor will always have to take care of reversing direction specifiers when a way is reversed, so I see no disadvantage in keeping the specification compatible with existing API infrastructure --Kaitu 09:47, 28 December 2008 (UTC).
What about tagging like maxspeed:opposite=*? And tagging for the direction of the road would be voluntary as when there exists a tagging for opposite direction the maxspeed=* without direction would mean the direction of the road. But I see a little shortage here of the words meaning 'opposite direction' as some of them might confusingly mean 'reverse' and thinking of a car reversing at a speed of 90 km/h is quite amusing :)
So, can a native english speaker propose a good word for indicating opposite direction of a road?
|In the direction of the road||Opposite direction of the road|
|onward onwards forward forwards ahead along forth||rearward rearwards backward backwards back astern about around|
--Joosep-Georg 09:18, 10 May 2010 (UTC)