Proposed features/Telecom local loop

From OpenStreetMap Wiki
Jump to: navigation, search
Telecom local loop
Status: Draft (under way)
Proposed by: ZZ29
Tagging: telecom=[[Tag:telecom=<tt style="background-color:#EEF;white-space:nowrap" dir="ltr">central_office, telecom=connection_point, telecom=outdoor_dslam, telecom:network=local_loop, connection_point=*, telecom:medium=*|central_office, telecom=connection_point, telecom=outdoor_dslam, telecom:network=local_loop, connection_point=*, telecom:medium=*]]</tt>
Applies to: NodeArea
Definition: Introducing new values to depict the telecom local loop, with some keys to map this network in a consistent way.
Drafted on: 2015-02-15
A central office, France.
Two outdoor DSLAM, France.

Proposal

This proposal aims to introduce new values to describe the telecommunication local loop, especially with the telecom=* key. After introducing man_made=street_cabinet last year, there is a need to describe more precisely the different kinds of street cabinet and for which kind of network (optical, copper,...) they are reserved. The central offices are also an important part of the local loop, this is why a tag will also be proposed here. This document will describe a common tagging scheme to specify the telecom local loop.


Rational

Many different kind of infrastructures of the local loop can be seen in the streets. There is today no tag to correctly define a central office, an outdoor DSLAM or a connection point. Moreover, different types of central office and connection points exists, for instance with copper (xDSL services) or fiber (FTTx services). This services cannot be distinguished with our current tags.

Tagging

Central office

A central office is a building, a part of a building or in some countries a street cabinet which connect a subscriber's home with the provider of a line. A lot of switching equipments are located in central offices.

Key Value Description Use
telecom central_office The central office should be mapped as Area for those which are located in a dedicated building. For the others (recent ones in street cabinets, part of building,...), a Node should be used. mandatory
building yes When located in a dedicated building. optional
man_made street_cabinet When the central is a street cabinet. optional
street_cabinet telecom mandatory with man_made=street_cabinet
telecom:medium <medium type> The type of local loop it is used to. See below for possible values. recommended
operator <operator> The name of the company that operates the cabinet. optional
owner <owner> The name of the organization which has the ownership of the building (State or local administritive organisation for example) optional
ref <reference> recommended
List of possible telecom:medium=* values. The tag corresponds to the medium for the final user (local loop side), so central offices which are not for FTTx won't have the fiber tag.
Key Value Comment
telecom:medium copper When the connection is with copper for the final user. Typically for xDSL offers.
telecom:medium fiber When the connection is with fiber for the final user. Typically for FTTH or FTTO offers.
telecom:medium coax When the connection is with coaxial cable for the final user. Typically for FTTB or FTTLa offers.


Outdoor Dslam

Near from central offices, owned by telecommunication operators, these street cabinets are used with copper networks and host dslam.

Key Value Description Use
man_made street_cabinet mandatory
street_cabinet telecom mandatory
telecom outdoor_dslam mandatory
operator <operator> The name of the company that operates the cabinet. recommended
owner <owner> The name of the organization which has the ownership of the building (State or local administritive organisation for example) recommended
ref <reference> recommended