<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/03/2014 17:15, François Lacombe
wrote:<br>
</div>
<blockquote
cite="mid:CAG0ygLd-NDyXJX5g_fvRxnMMKafz6Kp9UkFETxudK+U=AMZ5ig@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">2014-03-04 16:35 GMT+01:00 Jean-Marc
Liotier <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jm@liotier.org" target="_blank">jm@liotier.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
Along railways, motorways, high-voltage lines, riverbeds,
roads, sewers, tunnels... Pretty much every type of
right-of-way is used and the telecom link is part of it.
Rarely does the telecommunications link exist on its own,
except as directly buried cables that exist in rural
locations.</blockquote>
<div><br>
</div>
<div>I don't agree. "Except in rural location" may concern
some important distance.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Yes, those rural cables buried directly are long ones and therefore
represent a significant share of the network's total length.
Opposite case: sewer-borne cables - short, numerous and urban.<br>
<br>
<blockquote
cite="mid:CAG0ygLd-NDyXJX5g_fvRxnMMKafz6Kp9UkFETxudK+U=AMZ5ig@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
</div>
Come on Jean-Marc, @AlertePelleteuz on Twitter wouldn't
report so many optical fibre outage with an efficient and
reliable French DICT system.</div>
</div>
</div>
</blockquote>
<br>
Indeed there is room for improvement - we are working on it.<br>
<br>
<blockquote
cite="mid:CAG0ygLd-NDyXJX5g_fvRxnMMKafz6Kp9UkFETxudK+U=AMZ5ig@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>As a data producer I can't know what user would be
finally interested in.<br>
</div>
<div>I see things in my environment and looking for the best
way to legally, responsibly and technically add it to the
map.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
If you take a major drinking water pipeline such as Aqueduc de
l'Avre or the TRAPIL fuel pipeline network, even though they are
buried they are associated with a surface trail so clearly visible
that one may almost consider setting landuse=pipeline on top of
them. They are an important part of how one may describe their
location, even though their main feature is underground.<br>
<br>
In the case of telecommunications infrastructure, I believe that the
issue is visibility. I am convinced that mapping features that are
not visible directly or indirectly is not going to produce data that
Openstreetmap contributors can maintain - and that it should
therefore not be present.<br>
<br>
That leaves many telecommunications features that are excellent
Openstreetmap fodder: hosting centers, central offices, street
cabinets - we had those discussions before. But visible cables or
cable-bearing infrastructure are going to be a very rare exception
to the norm of invisibility - better take that into account early to
set limited goals and expectations... Unlike your effort on the
electrical network which is turning out very nicely !<br>
<br>
Well... Back on topic...<br>
<br>
Let's take inspiration from
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dpipeline">https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dpipeline</a> and
propose:<br>
<br>
man_made=pipeline<br>
type=telecom<br>
location=underground<br>
operator=*<br>
<br>
The German man_made=pipeline page already proposes type=telecom<br>
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/DE:Tag:man_made%3Dpipeline">https://wiki.openstreetmap.org/wiki/DE:Tag:man_made%3Dpipeline</a><br>
<br>
And on the basis of
<a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:pipeline%3Dmarker">https://wiki.openstreetmap.org/wiki/Tag:pipeline%3Dmarker</a> you would
have:<br>
<br>
pipeline=marker<br>
type=telecom<br>
operator=*<br>
ref=*<br>
<br>
The key here is to set the hypothesis that you are going to map not
cables but cable paths, which may contain more than one cable - in
my view, that justifies using the pipeline tagging scheme.<br>
<br>
</body>
</html>