[Tagging] Feature Proposal - RFC - Telecom local networks

François Lacombe fl.infosreseaux at gmail.com
Wed Oct 10 11:41:23 UTC 2018


Le mer. 10 oct. 2018 à 01:09, Graeme Fitzpatrick <graemefitz1 at gmail.com> a
écrit :

> Massive job, thanks Francois! :-)
> Question for you pleasse.

You're welcome

> Following on from the discussion re towers & masts, I've just mapped a
> couple of mobile phone towers.
> What should we call the base station hut / building usually adjacent to
> the base of the tower
> My understanding is they're not a street cabinet as you can walk inside
> them.

That's right it's a building and not a street_cabinet.
Except building=service, I won't add anything else for now.

The proposal only regards local loop fixed landlines, other document will
be needed to deal with mobile networks.
For me, communication:*, telecommunication=* should finally be converted to
telecom=* for physical paths and devices.

Le mer. 10 oct. 2018 à 12:51, Lionel Giard <lionel.giard at gmail.com> a
écrit :

> In this proposal we use "telecom" key, but i would like to know what is
> the limit/definition of this key ? Does it englobe internet provider, tv
> provider and mobile provider (even if the company does only one of them
> which is rarer today) ? Or only some of those ?

telecom=* is proposed as follow :
"It is proposed to use telecom
<https://wiki.openstreetmap.org/wiki/Key:telecom>=* key to map telecom
copper, fibre and coaxial local loops networks."
It doesn't cover services or logical functionalities yet but only static
physical infrastructure of networks (if Virgin uses AT&T network to provide
a service, then operator=AT&T and not operator=Virgin)

> My question come from the wiki page about street_cabinet (
> https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dstreet_cabinet#Street_cabinet_categories
> ) where the values of "street_cabinet" tag can be "telecom" and "cable_tv"
> as two different values. Would it be preferable to merge them into
> "telecom" ? As to me telecom means "telecomunication" which englobe TV,
> internet and mobile.

That may be true, but out of the scope of the proposal.
street_cabinet=cable_tv may sound inconsistent since tv is a service
provided on top of coaxial infrastructure (I didn't have the same point of
view back in 2014). Especially when Internet is also provided over the same
coaxial network.
Then, it's equivalent to map :
man_made=street_cabinet + street_cabinet=cable_tv +
telecom=connection_point + telecom:medium=coax
man_made=street_cabinet + street_cabinet=telecom + telecom=connection_point
+ telecom:medium=coax

I'll try to add such example in the proposal.
Replacing street_cabinet=cable_tv by street_cabinet=telecom +
telecom:medium=coax isn't such a big deal and can be discussed here without
requiring a proper proposal with vote.

All the best

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20181010/2d41121b/attachment-0001.html>

More information about the Tagging mailing list