Proposed features/Street cabinet

From OpenStreetMap Wiki
Jump to: navigation, search
Street cabinet
Status: Approved (active)
Proposed by: Fanfouer
Tagging: man_made=[[Tag:man_made=<tt style="background-color:#EEF;white-space:nowrap" dir="ltr">street_cabinet, street_cabinet=*, operator=*|street_cabinet, street_cabinet=*, operator=*]]</tt>
Applies to: NodeArea
Definition: Introducing a new value of man_made=*, some understandable and reliable keys to map many kind of street cabinet around the world
Rendered as: Unknown
Drafted on: 2014-02-09
RFC start: 2014-04-25
Vote start: 2014-10-30
Vote end: 2014-11-13
Street cabinet friendship.jpg

Proposal

This proposal aims to introduce a new value of man_made=* key and an additional extra key street_cabinet=* to map different kind of street cabinet which can be seen in many cities. Only main values are described here, up to mappers to define custom ones if they don't find any compatible stuff. This document will describe a common tagging scheme without promoting a special infrastructure but some good ways to specify the cabinet usefulness in all cases.

Rationale

Many different kind of street cabinets can be seen on side walks all around the world.
Currently, no key allows mappers to add them correctly in OSM, with a lack of information about pavement accessibility and what is really hosted inside.


A street cabinet hosts many sort of equipment, often technical stuff, where workers can't enter inside.
It's an opposite of buildings where humans can get in.

New approach

To have an expendable and consistent tagging scheme for street cabinets it is proposed to:

Tagging

Tagging example

A street cabinet is commonly a box with vertical hinged doors installed in the street. It contains technical stuff and utilities to run several devices like traffic lights, telephone lines or water meters.
Let's introduce man_made=street_cabinet to map such facilities and assume they merely have a prismatic shape.

Basic tagging

Basically a street cabinet should be tagged as follow:

Key Value Comment Recommendation
man_made street_cabinet The street cabinet should be mapped as a Node. In exceptional cases, such as when cabinet is really big and have a pedestrian accessibility impact, it may be mapped as an Area. mandatory
street_cabinet <cabinet type> The functional type or role of the cabinet or its infrastructure implication. See below for possible values. recommended
width <cabinet width> The effective width of the cabinet optional
length <cabinet length> The effective length of the cabinet optional
height <cabinet height> The effective height of the cabinet optional
direction <cabinet azimuth> The northing azimuth of the "length" side of the cabinet optional
colour <cabinet colour> The colour of the cabinet optional
manufacturer <cabinet manufacturer> The name of the cabinet manufacturer (often visible as a logo) optional
model <cabinet model> The name of the cabinet model (as seen in manufacturer brochure) optional
operator <operator> Name of the company that operates the cabinet or what's hosted inside. optional
ref <reference> Abbreviation / number of the cabinet as publicly visible. ref=* is used by default when no sepecifi key is available (see ref:ERDF:gdo=* as an example) recommended
hinge vertical or horizontal Direction of cabinet's door opening. optional
List of possible street_cabinet=* values
Key Value Comment
street_cabinet power A street cabinet use to host devices for electricity distribution.
street_cabinet gas A street cabinet use to host devices for urban gas distribution.
street_cabinet street_lighting Street lighting switches and cables can pass through some cabinets all along the streets.
street_cabinet traffic_control A street cabinet mainly designed to host traffic lights automation systems but other traffic control systems such as movable barriers. It does have a direct impact on traffic flow.
street_cabinet traffic_monitoring A traffic management device is mainly in charge of vehicle counting. It differs from street_cabinet=traffic_control since it can't impact on traffic directly.
street_cabinet transport_management Transport management cabinets often host automation systems to allow public transportation installed on dedicated paths (metro, tramways...) to work.
street_cabinet water_management All cabinets designed to host water management devices like automation or probes but no water pipes. It includes not only cabinets for drinkable water but utility water or sewerage too.
street_cabinet water All cabinets hosting pipes and valves directly. It includes not only cabinets for drinkable water but utility water or sewerage too.
street_cabinet postal_service A street cabinet designed to host pending letters or other postal stuff before they go on local delivery.
street_cabinet telecom A street cabinet wich is hosting telephone lines amplifiers or connection points.
street_cabinet cable_tv A street cabinet wich is hosting cable CATV lines amplifiers or splitters.



This list of possible values can be completed ad hoc by users who don't find any matching one here.

Accessibility

Streets and more specifically pavements accessibility may be impacted by cabinets installation. Some tags may help to define how this impact can be reduced or avoided. The best example is to compare pavement total width with the cabinet width to know if wheelchairs can pass normally. More information about dimension measuring by looking directly on common keys' page.

Please note street cabinets are only a small accessibility factor of global pavement paths. They are often seen like obstacles and should be mapped as this. Many more information may be available in their direct environment (and firstly on pavement way).

List of possible accessibility keys
Key Value Comment
sound Any kind of sounds emitted by the cabinet A street cabinet can emit sounds which are useful for visually impaired people
heat yes/no A street cabinet can emits heat.
texture Cabinet texture The cabinet surface texture useful for visually impaired people

Values to be replaced

Some existing values, more specific than man_made=street_cabinet should be replaced as below:

Obsolete tag Used for ? New tag(s) to use
power=cable_distribution_cabinet A small cabinet for power local distribution man_made=street_cabinet + street_cabinet=power
utility=cabinet A street cabinet in general man_made=street_cabinet + street_cabinet=* (depending of what utility is concerned)
utility=* Any utility feature describing a cabinet in the street man_made=street_cabinet + street_cabinet=* (depending of what utility is concerned)

Examples

Electricity & gas

Photo Tagging Note
Power distribution cabinet, France
This proposal:

Node or Areaman_made=street_cabinet
street_cabinet=power
hinge=horizontal

Domain specific:
voltage=*
Often in urban places, such cabinet are found on side walks and host switches or joints for electricity distribution.
Gas delivery point, France
This proposal:
Node or Areaman_made=street_cabinet
street_cabinet=gas
hinge=horizontal
operator=GRDF
manufacturer=fiorentini

Domain specific:
A French gas delivery point where pressure is dropped down as for carrying it directly to customers.

[Map]
Private gas delivery point, France
This proposal:

Node or Areaman_made=street_cabinet
street_cabinet=gas
hinge=horizontal
operator=Regaz
manufacturer=fiorentini

Domain specific:
A French gas delivery point where gas is counted to deliver it to a particular customer.
Street lighting cabinet, France
This proposal:

Node or Areaman_made=street_cabinet
street_cabinet=street_lighting
hinge=horizontal
manufacturer=grolleau

Domain specific:
A cabinet hosting switching, accounting and cables of public street lighting system.

Water management

Photo Tagging Note
Sewerage facility controller, France
This proposal:

Node or Areaman_made=street_cabinet
street_cabinet=water_management
operator=CUB
hinge=horizontal
manufacturer=seiffel

Domain specific:
A French sewerage facility controller.

Road facilities

Photo Tagging Note
Traffic lights controller, France
This proposal:
Node or Area
man_made=street_cabinet
street_cabinet=traffic_control
hinge=horizontal
manufacturer=grolleau

Domain specific:
A French traffic lights controller hosting controlling equipments.

[Map]
Traffic lights controller, France
This proposal:
Node or Area
man_made=street_cabinet
street_cabinet=traffic_control
hinge=horizontal

Domain specific:
A French traffic lights controller hosting controlling equipments.
lack of illustration This proposal:
Node or Area
man_made=street_cabinet
street_cabinet=traffic_monitoring
hinge=horizontal

Domain specific:
A French traffic controller used to count vehicles driving on a given road.
Public transport automation cabinet
This proposal:
Node or Area
man_made=street_cabinet
street_cabinet=transport_management
hinge=horizontal

Domain specific:
A French transport controller to manage tramways switching devices in the street

Cable TV

Photo Tagging Note
Lack of illustration This proposal:

Node or Areaman_made=street_cabinet
street_cabinet=cable_tv
operator=Virgin

Domain specific:
An UK CATV green cabinet owned by Virgin Media
French cable TV splitters cabinet
This proposal:
Node or Areaman_made=street_cabinet
street_cabinet=cable_tv
operator=Numericable

Domain specific:
A French cable TV spliting cabinet in street of some major cities

Telecoms and postal services

Photo Tagging Note
Telephone street cabinets, UK
This proposal:
Node or Area
man_made=street_cabinet
street_cabinet=telecom
hinge=horizontal
operator=Openreach

Domain specific:
Two telephone street cabinets in GB streets. First one is designed to hold DSLAM for VDSL connection and we can see on background an old copper primary connection point (PCP).
Telephone street cabinet, France
This proposal:
Node or Area
man_made=street_cabinet
street_cabinet=telecom
height=1.91
width=0.44
length=1.87
hinge=horizontal
operator=Orange
manufacturer=prefatel
model=ASRP15T

Domain specific:
A French street cabinet for copper lines connections. That's the current installed model in all cities.
Telephone street cabinets, France
This proposal (newest one):
Node or Area
man_made=street_cabinet
street_cabinet=telecom
height=1.64
width=0.35
length=1.64
hinge=horizontal
operator=Orange
manufacturer=ideaoptical
model=iBER-C-1635-outdoor

Domain specific:
Two telephone street cabinets in French streets. First one is designed to hold optical connection point and second POTS copper lines connections (legacy iron model)

[Map]
Postal street relay, France
This proposal:
Nodeman_made=street_cabinet
street_cabinet=postal_service
hinge=horizontal
operator=La Poste

Domain specific:
A small French brown street cabinet currently used by national postal services to relay letters and parcels prior to their local distribution.

[Map]

Features/Pages affected

If approved, this proposal would impact:

  • tags:
    • man_made=street_cabinet: Create this page and explain its usage.
    • street_cabinet=*: Create this page (related to THIS proposal) and explain its usage.
    • manufacturer=*: Create this page (attribute) and explain its usage : required? How to differenciate with operator=* ?.
    • model=*: Create this page and explain its usage: should be optional.
    • hinge=*: Create this page and explain its usage: should be optional (very specific to cabinets built over the ground, may not be accurate for elevated cabinets on masts or on towers, or within underground wells).
  • other optional complementary tags:
    • length=* and width=*. Not very clear (a width is a length but width is sometimes understood as the longest horizontal dimension in other tags). Consider drawing polygons instead (will also work when cabinets are not rectangular, some of them are tower-like, with a circular footprint on the ground, or fixed over a thin mast or along building wallsn, or on top other urban equipement such as bus stop or below bridges or within wells or within "niches" or small rooms inside building walls).

All that tags must be disused before they get actually documented on this wiki or more widely used :

  • utility
  • cabinet

Please explain the term "street" which is too restrictive (cabinets may be within buildings, or on top of roofs, or built on mountain pikes far from any "street"). Consider using a more appropriate term like "technical_cabinet" (but consider also monitoring stations which are very often, but not always, within cabinets too, along streets/roads or railways or rivers, or coastlines or in airports, or along power lines in some related facilities)

Comments

Comments are welcome on the Talk page :)

Voting

Please use {{vote|yes}} or {{vote|no}} and give your reasons to oppose. Use ~~~~ to sign with your user name & date.

  • I approve this proposal I approve this proposal. Spitzbart (talk) 19:45, 30 March 2015 (UTC)
  • I approve this proposal I approve this proposal. JitenshaNiko (talk) 21:00, 14 November 2014 (UTC)
  • I approve this proposal I approve this proposal. Jseigneuret (talk) 13:39, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Escada (talk) 13:29, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal.--Dieterdreist (talk) 13:30, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Yod4z (talk) 13:43, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Zecke (talk) 13:46, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. /al 13:49, 30 October 2014 (UTC) -- But I'd suggest to allow rectangular mapping instead of giving width, depth, direction or whatever. (N.B.: width x depth x height! length and width mean the same [the longer side of the base rectangle][lenght even means the longest side of a quader and makes no sense at all])
  • I approve this proposal I approve this proposal. Sdoerr (talk) 13:50, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. BZH (talk) 13:56, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. PhQ (talk) 16:19, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Fanfouer (talk) 16:06, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. JB (talk) 16:16, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Glassman (talk) 17:10, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Syrus (talk) 17:32, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Sommerluk (talk) 18:49, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. TheDutchMan13 (talk) 13:10, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Yannig (talk) 20:12, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. --Floscher (talk) 20:18, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Hedaja (talk) 21:13, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. AlaskaDave (talk) 23:05, 30 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Javbw (talk) 05:32, 31 October 2014 (UTC)
  • I approve this proposal I approve this proposal. Zoubiddaaa (talk) 13:37, 31 October 2014 (UTC)
  • I approve this proposal I approve this proposal. --Rfuegen (talk) 23:15, 31 October 2014 (UTC)
  • I approve this proposal I approve this proposal. --nyampire (talk) 08:07, 1 November 2014 (UTC)
  • I approve this proposal I approve this proposal. Polarbear w (talk) 21:35, 2 November 2014 (UTC)
  • I approve this proposal I approve this proposal. Warin61a (talk) 22:00, 3 November 2014 (UTC)
  • I approve this proposal I approve this proposal. --Pyrog (talk) 18:52, 13 November 2014 (UTC)
  • I oppose this proposal I oppose this proposal. conflicts with Tag:man_made=monitoring_station (approved and active) in too many domains - missing rationale for desambiguating uses. Also badly named (not all cabinets are in "streets", some may be nearly invisible, below the ground within wells or in other underground facilities, within buildings or walls, on top of roofs, on high masts, on mountain pikes...). I'll change my vote later only after clarifications made — Verdy_p (talk) 20:42, 13 November 2014 (UTC)
Thank you User icon 2.svg Verdy_p (on osm, edits, contrib, heatmap). Please note that Open Street Map doesn't only concern streets any more. Discussion on Talk will go on after this simple proposal to make street_cabinet=* values more exhaustive and add examples. I agree with you on the strict side of things, nevertheless, man_made=street_cabinet is a good generic option to start mapping. Instead of waiting any clarification from Above, you can try yourself your own proposal on this wiki. Fanfouer (talk) 23:33, 13 November 2014 (UTC)
I don't want to reform completely this proposal for another one, but the current vote is much too large when there are several issues to consider with other existing tags, some of them being still very used and very active, and approved since long. I want clarification to make a more clear distinction between the architectural form (a cabinet, other forms are possible but "man_made=*" is appropriate), its location (street, or elsewhere, "man_made=*" is not appropriate for that), and its function(s) (man_made=* is definitely not the correct tag for indicating that, there are other tags for example in "trafic:*=*", or "railway:*=*", etc.). Even if this vote is passes this evening, nothing will be solved about the conflicts with other approved values "man_made=*" for the proposed main tag. Nothing is solved but we are adding here a new difficulty or ambiguity! Even the name of the tag is a problem with "street_cabinet", when it should be "technical_cabinet", and all other proposed subtags areassuming a rectangular form and laying vertically on the ground !!! In mly opinion the vote was initiated too prematuremly without first lmooking for usages and seeing how each practice could be migrated, and nothing was searched about preserving compatibilities including for future evolutions. This proposal, even if it passes, is still unusable in its existing form. The vote will just initiate some principles to be refined — Verdy_p (talk) 23:54, 13 November 2014 (UTC)
It was discussed to use this for permanent garbage disposal cabinets found in Japan, using the value =waste, so it isn't merely technical. Javbw (talk) 00:31, 15 November 2014 (UTC)
  • I approve this proposal I approve this proposal. User:Liotier -- I would have either not created the cable_tv value and included it in telecom, or I would make telecom finer grained (copper, fiber, cable etc.)... But that may be a personnal bias - good job anyway !



27 pros and 1 cons : this proposal is approved on November 14 2014. Thank you for your numerous feedbacks !

Now solve the problems above. And alert all those users affected by this proposal only approveds by some 27 people without alerting the hundreds using another older approved proposal (much more active than this one). Unfortunately this page was announced very late only with the starting vote on October 30 and not followed before the end the last day.
The supposed "RFC" procedure did not occur. This alpha proposal is only experimental for now (we'll need more time to experiment it and report problems), and will soon need to be revisited. Things are not terminated by this vote and we'll need to review how to separate the three separate concepts that this proposal mixes: architectual form (cabinet: too limited), location (street: too limited), function/usage (conflicting with other tags). — Verdy_p (talk) 19:16, 14 November 2014 (UTC)