Tag:power=line_section
 power = line_section
|
 |
| Description |
|---|
Arrangement of continuous power line segments to form a section between two substations or tap points. 
|
| Group: power |
| Used on these elements |
    |
| Requires |
| Useful combination |
Status: approved
|
| Tools for this tag |
|
A power line section is defined by 601-02-30 IEC60050 definition. It consists of one or more continuous line segments (i.e., consistently tagged power=line, power=minor_line or power=cable on ways in OSM) that form a connection between substations or tap points.
Each section always has exactly two endpoints.
In practice, a line section is composed of conductors that run continuously along power line segments between substations or tap points.
It's a member of a power=circuit relation only when necessary, under circumstances explained below.
How to map
To keep mapping simple, a power=line_section relation is only required when the section includes two or more segments that need to be grouped to support consistent properties.
Thus, they are expected in power=circuit when the circuit they support has more than two endpoints only.
On the contrary, if the section is composed of a single segment, the concepts of “section” and “segment” are merged.
If the supported circuit has exactly two endpoints, the concepts of "section" and "circuit" are merged.
No relation is necessary and you shouldn't create one. A single power=line way or a single circuit relation are most of the time sufficient.
When necessary, assemble the corresponding power segments (line, minor line or cable) in a relation and give them the line role.
Set appropriate properties like voltage=* or cables=*.
How will we get such information?
Power lines sections are simpler than circuits and can also be deducted from ground survey or aerial imagery. A section is metallic continuation of conductors between two substations or between a substation or a tap point.
Mappers are expected to follow the line segments and stop by substations or tap points.
Just like circuits survey, looking in details at particular points will help, particularly the towers which has got line_management=* or nodes with switch=circuit_breaker.
Public documentation with valid license could help to solve undefined situations. Such knowledge will then be verifiable on ground.
Tagging
Relation
| Key | Value | Comment | Recommendation |
|---|---|---|---|
type |
power |
This is a power relation | Mandatory |
power |
line_section |
This relation represents a section of a power circuit | Mandatory |
voltage |
<Operating voltage> | The voltage at which the section operates, in volts | Recommended |
cables |
<Section's cables> | The amount of cables involved by the section | Recommended |
ref |
<Reference> | The section's reference | Optional |
name |
<Name> | The section's readable name | Optional |
operatoroperator:wikidata |
<Company name> | The company in charge of section operation | Optional |
You should avoid using wires=* and frequency=* on such relations as the first is related to physical construction of supporting segments and the last is related to circuit in which the section is involved.
It's important to reduce redundancy of information and not report those properties on sections. See further explanation in the reviewed proposal.
Members
The relation combines two or more line segments.
A relation with a single line segment is not permitted and you shouldn't create one.
We prefer involving the 
power=line segment directly in a circuit relation.
| Member's role | Member's type | Count | Member | Description |
|---|---|---|---|---|
| line |
|
two or more | Power line segment | A segment of power line involved in the power section |
Examples
To be completed