This article or section may contain out-of-date information: This proposal has been obsoleted by the following relation types: For street like relations see relation:associatedStreet and relation:street. For streams and rivers see relation:waterway. For generic collections of linear features see relation:multilinestring
The direct successor of the proposal is Relations/Proposed/Collected_Ways_Simple
Also remember that Relations should not be used as "categories"
If you know about the current state of affairs, please help keep everyone informed by updating this information. (Discussion)
|Definition:||A Relation to represent all the ways making up a street with a common name, the ways of a complete waterway or railway and possibly others.|
This is a proposal for a set of tags and members making a Relation to represent all the ways making up a street with a common name, the ways of a complete waterway or railway and possibly others.
This could be determined by looking at names of ways, especially if they are connected, but this is a more convenient mechanism. It might be used where a street is broken up into multiple ways by bridges, changes of status (residential, unclassified etc), and so on, or where a a street pattern is not contiguous - lots of branching or discontinuous sections.
Note that numbering of roads is placed under Routes. See there for reasoning.
The collecting of ways into streets also overlaps with linking of carriageways of a dual carriageway (divided highway).
Though we can't do it yet, it should eventually be possible to drop any common tags on each of the constituent ways and have them on the relation instead, with constituent ways having preference if they deviate from the relation (e.g. a relation with 10 ways, relation has highway=residential name=Dover St, but one of the 10 ways has highway=pedestrian).
|collection||street/river/stream/rail||if type is tagged with collection|
|any tag||any value||All tags on the relation (besides type) are automatically inherited to the members, but tags on the members override those on the relation. Thus, the relation could have highway=residential, but some of its members could be tagged as highway=living_street. They could also have different names, etc.|
|Way or Relation||Role||Recurrence?||Discussion|
|member||one or more||All the related ways that constitute this way. alternatively: street/river/stream/railway|
|axis||zero or one||Line in the middle of the street, specially if the street/rail consists of more than one carriage way/track (highway/railway = axis)|
|address||zero or more||See Karlsruhe_Schema|
|associated / others...||zero or more||everything related to the way|
Members might also be other relations (e.g. dual carriageways).
Using Collected Ways wherever Ways can be used
Since we will often have the need to split ways into smaller parts and/or to group small parts into one, it is assumed that in the long run, a "collected way" relation may take the place of an ordinary way everywhere. This means that everywhere one would normally expect a way, there could be a "collected way" relation instead.
This applies recursively, i.e. we will very likely allow a "collected way" relation to be built from not only normal ways, but also other "collected way" relations. This is important especially with respect to the planned upper limit for the number of members in a relation; it will become impossible to combine *all* ways that make up a transnational motorway into one relation.
Clients (editors, rendereres) are encouraged to accept "collected way" relations in lieu of a plain way wherever possible.
this version of collected way (from 2009 and earlier)
I'm not happy with the current version wich I find too complicate, I'd rather like this very simple old one : Relations/Proposed/Collected Ways Simple