Proposal:Relation:system
Jump to navigation
Jump to search
| System Relation | |
|---|---|
| Proposal status: | Draft (under way) |
| Proposed by: | Panther37 |
| Tagging: | type=system |
| Applies to: | 
|
| Definition: | The system relation is used to make multiple things work as one system. |
| Statistics: |
|
| Draft started: | 2012-04-23 |
Relations of type system are used to represent complex arrays of things as one system.
Simple points are mapped in OSM. If you have two things they are mapped seperately. However, this model only works for seperate things. If one thing has multiple parts, we put them together in a relation. For all of the multiple parts to function as one, they are a system.
Tags
| Key | Value | Explanation |
|---|---|---|
| type | system | indicates this Relation represents a system |
| system | highway | aeroway | railway | etc. | indicates what is included in the system. If all nodes are the same, node tag should be added too (example: highway:traffic_signals) |
Members
| Way or Node | Role | Recurrence? | Explanation |
|---|---|---|---|
|
none | No uses yet |
Usage
The intended use of systems is this:
- Tags complex traffic signals as one signal
- Could be used instead of Relations/Proposed/Site
Examples
None
Tagging
- It is suggested to apply all tags which describe the system to the parts, and not to the system for better compatibility.
See also
- See highway=traffic_signals for some discussions on how to improved area handling in OSM.
