Proposal:Directional node

Relation:direction
Proposal status:	Rejected (inactive)
Proposed by:	Andrewpmk; Zverik
Tagging:	type=direction
Applies to:
Definition:	Direction for point features
Statistics:
Rendered as:	rotated icon
Draft started:	2009-08-27
RFC start:	2011-08-09
Vote start:	2011-08-26
Vote end:	2011-09-11

A relation that groups a point feature (e.g. a road sign or a 3d painting) with a node or a way, to which this feature is facing (e.g. a highway segment or an observation point). This is a generic proposal, it does not address the tagging of specific types of objects (e.g. stop signs). For stating the direction of unrelated point features, Proposed features/direction should be used.

Tags

The only required tag on relation is type=direction.

Members

The relation must have two, and only two members: the directional node and the related node/way.

Member	Role	Recurrence	Description
	from	one	A node or way in the direction the object is facing. if a point feature is at the end of that way and is faced in that direction (one-sided road signs, for example). if a point feature is faced in the direction of this node and is related to it.
	<blank>	one	The node whose direction is being described.

Examples

A traffic sign

Here 'from' member is a way, leading to a highway=stop (which is placed not as recommended on the wiki page, just for example). Since the node is in the direction relation, it affects only vehicles coming from the specified direction.

A painting

A 3D painting is best viewed from a single point, usually marked. So in a way, a painting has a direction.

traffic mirror

A traffic mirror is viewed from 2 directions. It is represented by a node. highway=traffic_mirror

Discussion

Please use the Talk page.

Voting

Please add {{Vote|yes/no}} [your comment] --~~~~

• I approve this proposal. --Zverik 07:41, 26 August 2011 (BST)
• I oppose this proposal. Given Proposed features/direction I think this proposal needs more discussion and justification of its need. -- Rjw62 08:24, 26 August 2011 (BST)
• I approve this proposal. --Dieterdreist 10:30, 26 August 2011 (BST)
• I oppose this proposal. Like other direction proposals, we don't need such things in OSM since our basic element, the node, contains coordinates. If a node is not enough, draw a line. If a line is not enough, draw a tringle or a rectangle, etc. Don't use ugly tagging schema when your issue can be solved by simple drawing's. --Pieren 11:59, 26 August 2011 (BST)

This is the proposal to draw a line to mark a direction. --Zverik 12:20, 26 August 2011 (BST)

erg.. no, it's about creating a relation, nothing about drawing. --Pieren 10:03, 2 September 2011 (BST)

erg.. yes it's not a physical thing and yes the relation describes a line to detrmine the direction.

• I approve this proposal. But I'd add a "to" role to show the direction toward which the node is facing. --Surly 11:11, 27 August 2011 (BST)
• I oppose this proposal. Adjuva 02:11, 28 August 2011 (BST)
• I approve this proposal. - although I dislike relations (they tend to get messy and novice users don't understand them) I can't figure a better way to achieve this (position:left would be an idea, but is probably even more messy). --BorisC 09:16, 2 September 2011 (BST)
• I approve this proposal. --Lulu-Ann 14:40, 2 September 2011 (BST)
• I approve this proposal. --Computerfreaked 03:37, 4 September 2011 (BST)
• I oppose this proposal.--R-michael 07:33, 8 September 2011 (BST)

See also

• Relation:enforcement and Relation:restriction — those use the same scheme
• Proposed features/direction — a proposal for stating node direction in degrees
• Proposed features/One way restrictions — suggestion to change API in order to make all ways bidirectional