|man_made = utility_pole|
|A single pole supporting elevation of any of various and unspecified public utilities, such as power transmission, lighting or telephony.|
|Group: Man made|
|Used on these elements|
|Tools for this tag|
A single pole supporting elevation of any of various and unspecified public utilities, such as power transmission, lighting or telephony.
How to map
On every pole found on ground or on aerial imagery, place a node at the exact location of each pole.
Tagging is really simple. Add man_made=utility_pole, sometimes in replacement of communication=pole or telephone=pole.
Also add corresponding main purpose with utility=*, often utility=telecom. Always use a single value for this key, see below.
|man_made||utility_pole||It's a pole supporting utility networks||mandatory (except for power poles)|
|utility||<main utility>||The purpose for which the pole was design or installed||recommended|
|material||<pole material>||The material composing the pole||recommended|
|height||<height>||Pole's height in meters as measured or read on ground||recommended|
|operator||<operator>||Name of the company that operates the pole||optional|
|manufacturer||<Manufacturing company>||Name of company that produced the pole||optional|
|ref||<reference>||Abbreviation / number of the pole as seen on ground.||optional|
|line_attachment||<line attachment>||Attachment mean for lines connected to that pole||optional|
|line_management||<line management>||Particular topology situations around the pole||optional|
Find the appropriate utility
See appropriates values for utility=* to state to which activity the pole is mainly designed for.
A given pole is almost always operated by a single operator=*, not several. This given operator can make offers to support other utility lines without changing its own responsibility for maintenance or operations or the pole nature.
Answers to such questions are convenient to get the right value of utility=*:
- Who operates the pole? If the operator is a telecom operator, then utility=telecom and so on...
- If the operator operates several utilities and rolls out them at the same time, which one is most impacting pole structure? A power line is heavier than a telephone line for instance, then utility=power (and power=pole).
As utility=* is used with a single and the most representative value for each given pole, solutions should exist to link a single pole to numerous different activities and features.
Here is a list extracted from a topic of Talk page to link many activities to poles
- High voltage electricity: pole member of a power=line way
- Lower voltage electricity: pole member of a power=minor_line way
- Coaxial cable carrying TV; telephone & internet: pole member of a way with tags remaining to be defined (telecom=line eventually) + telecom:medium=coaxial
- Metal wire bundles for telephone & T1 internet (called POTS by telephone workers) : pole member of a way with tags remaining to be defined (telecom=line eventually) + telecom:medium=copper
- Fiber optic cables carrying TV; telephone & internet: pole member of a way with tags remaining to be defined (telecom=line eventually) + telecom:medium=fibre
- Electrical transformers: transformer=* on the pole (and eventually substation=*, see Proposed_features/Substation_nodes_extension)
- CATV or telephone equipment cabinets: street_cabinet=* on the pole
- Street lights highway=street_lamp on the pole
- A fire emergency pull box with a corresponding red light above : not aware of an eventual emergency=* value to add on the pole
- Wires used for local sound system used by local authorities, but that would be an additional way
- Surveillance camera/CCTV: Should find a way to let man_made=utility_pole and man_made=surveillance to coexists on the same feature. However surveillance isn't a proper utility.
As some of those points don't refer to any utility at all (but a street furniture, emergency response equipment and so on), there is no point to give the entire list of what is supported by a given pole with utility=*.
Some tagging values for telecom poles was used previously. You can replace it manually with caution
- A proposal to make this value reviewed
- French data model for utility networks (PCRS). Page 71, AffleurantPCRS base class definition which any utility pole inherits. Attribute reseau is equivalent to utility=* and is defined with a multiplicity of 0..1.
- proposed type=node relation can be used to map things attached to a pole