<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML - vooraf opgemaakt Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTML-voorafopgemaaktChar
{mso-style-name:"HTML - vooraf opgemaakt Char";
mso-style-priority:99;
mso-style-link:"HTML - vooraf opgemaakt";
font-family:Consolas;
mso-fareast-language:NL-BE;}
span.E-mailStijl19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NL-BE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hey,<br>
<br>
I’m new at OSM so I don’t know if this is an usfull contribution but the BIPT-antennes or updated in de WMS /WFS of the flemish governement at Mercator WMS /WFS at the layer ‘Zendantennes’<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Wms :
<a href="https://www.mercator.vlaanderen.be/raadpleegdienstenmercatorpubliek/ows?SERVICE=WMS">
https://www.mercator.vlaanderen.be/raadpleegdienstenmercatorpubliek/ows?SERVICE=WMS</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">wfs :
<a href="https://www.mercator.vlaanderen.be/raadpleegdienstenmercatorpubliek/ows?SERVICE=WFS">
https://www.mercator.vlaanderen.be/raadpleegdienstenmercatorpubliek/ows?SERVICE=WFS</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">download –zip-shape :
</span><a href="https://www.mercator.vlaanderen.be/raadpleegdienstenmercatorpubliek/us/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=us_zndant_pnt&maxFeatures=40000&outputFormat=SHAPE-ZIP">https://www.mercator.vlaanderen.be/raadpleegdienstenmercatorpubliek/us/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=us_zndant_pnt&maxFeatures=40000&outputFormat=SHAPE-ZIP</a><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
metadata :<o:p></o:p></span></p>
<p class="MsoNormal"><a href="https://www.mercator.vlaanderen.be/zoekdienstenmercatorpubliek/apps/tabsearch/index.html?uuid=00b8c6b6-437d-4d35-9b39-7ad300f11b94&hl=dut">https://www.mercator.vlaanderen.be/zoekdienstenmercatorpubliek/apps/tabsearch/index.html?uuid=00b8c6b6-437d-4d35-9b39-7ad300f11b94&hl=dut</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gert<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Van:</span></b><span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Lionel Giard [mailto:lionel.giard@gmail.com]
<br>
<b>Verzonden:</b> dinsdag 10 maart 2020 11:51<br>
<b>Aan:</b> Vucodil; OpenStreetMap Belgium<br>
<b>Onderwerp:</b> Re: [OSM-talk-be] BIPT antennas<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><b>@ Vucodil :</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">One solution could be to map everything as telecom=antenna if they don't match a mast/tower (already mapped), and put a "fixme=check if a mast or tower is present". Note that on a rooftop, you generally don't have a mast (it is a small
support structure that we can just consider being "telecom=antenna" and maybe in the future, we could use a "antenna:support=*" tag ;-) ).
<b>[1]</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">For mast and tower, use the obvious existing one, or map it if it is visible (some of them can be easily seen on imagery), and use the man_made=mast or tower tag like usual and change it later on if needed (if a future proposal is done
for it). :-p <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">For man_made=antenna, i don't think it is better than telecom=antenna (neither one or the other was ever approved formally). The telecom key was created to refine the telecom tagging following the same idea that was used for the power infrastructure
(with the power key). I'm completely in favor of redesigning the telecom infrastructure tagging like the french community started to push (especially focused on cable and fiber infrastructure at the moment), as they seem quite experienced with infrastructure
tagging as they were involve in power tagging... :-p <o:p></o:p></p>
<div>
<p class="MsoNormal">So using telecom=antenna seems more logical in order to already start using a "proper" tag instead of a general tag like man_made=antenna (that we could regret later on). And it can always be changed if/when someone do a proper proposal
and approval process later on (as that would be the only difference, as the subkey will probably be identical).
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">antenna:use seems functionally equivalent to the <a href="https://wiki.openstreetmap.org/wiki/Key:communication:mobile%20phone?uselang=fr">
subtag communication:*=yes/no</a> (like communication:mobile_phone=yes/no). I don't see an improvement as the communication:*=yes/no is already used for all mast/tower<b> (including power=tower !
</b>As they can have antenna on them (i don't know if that's the case in Belgium)<b>)</b>, so we should maybe use it for antenna too. ^_^ One example that i did map like that for an antenna (on top of a watertower here) was <a href="https://www.openstreetmap.org/node/5968512028">https://www.openstreetmap.org/node/5968512028</a> . <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>[1]</b> I work at one of our telecom company and i can see their structure data (pylons, mast, ...) and it is very detailed but unfortunately it is closed data. :D But antenna on rooftop have a structure type : "self-supported roof structure".
;-) <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We should push BIPT to open more infrastructure data. :-D <i>
*dreaming* </i><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Le lun. 9 mars 2020 à 22:18, Vucodil via Talk-be <<a href="mailto:talk-be@openstreetmap.org">talk-be@openstreetmap.org</a>> a écrit :<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Hello everyone,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Already thanks for all the feedback! I answer some of your questions in the following topics:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Continuous update (@Midgard and @<a href="http://rodeo.be" target="_blank">rodeo.be</a> )</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">It was in the back of my head but I didn't want to plan it yet. I will probably work on that but not soon.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Note that the list of BIPT antennas is
</span><span lang="EN" style="font-family:"Arial","sans-serif"">updated monthly. Is there server for scheduled scripts within OSM BE ?</span><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN" style="font-family:"Arial","sans-serif"">Workflow (@Midgard)</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN" style="font-family:"Arial","sans-serif"">The distance triggering manual review has been changed to 25m.</span><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><br>
</span><span lang="EN" style="font-family:"Arial","sans-serif"">> 3) And even then, just dumping elements in OSM without manual review is not considered best<br>
> practice, but since it's only nodes, things are relatively simple and I won't object. I would<br>
> just like to see that they're not placed too close to any other existing node, but that can be<br>
> checked automatically.</span><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN" style="font-family:"Arial","sans-serif"">Like one meter? Is there JOSM tool for that?</span><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN" style="font-family:"Arial","sans-serif"">BIPT (@Thibault Rommel)</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">I agree. I updated the proposal<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Latitude and longitude as tag (@s8evq and @Midgard)</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">That's a mistake. I only wanted to explain that I use the longitude and latitude provided in the dataset. It has been updated.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Open data Portal (@<a href="http://rodeo.be" target="_blank">rodeo.be</a>)</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Good idea. I will inform BIPT of the positive feedback of the OSM BE community and I will kindly push them to do so.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Precision of the localisation</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Looking alone at 9000 nodes for manual review is quite some work. Would it be acceptable to have a FIXME tag stating that the localization could be a few meters offset? Or is it considered
to pollute the OSM db to do so?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Tagging (@Lionel</span></b><b><span lang="EN" style="font-family:"Arial","sans-serif"">, @Karel Adams, @midgard)</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">If I had found the discussion from 2018 before, I would have maybe not prepared the import :-D.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial","sans-serif"">What to map?</span></i><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">The BITP dataset include a list of sites used in our mobile phone network. Each site can include multiple supports for antennas. And each support can include multiple directional antennas.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">There is no info on the support in the dataset. That's why I focused on mapping the antennas (or the group of antennas). Are they enough visible in our landscape?
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">I think so. On rooftop in cities, those groups of antennas are often visible. Their white color is often even more visible than the support itself.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">On other structures like tower, @lionel already mentioned that the antennas could be tagged with telecom=antenna
<a href="https://lists.openstreetmap.org/pipermail/tagging/2018-October/040276.html" target="_blank">
https://lists.openstreetmap.org/pipermail/tagging/2018-October/040276.html</a>.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">I can understand that there is no proper way to tag the antennas and the group of antennas without specifying the support but it seems a bit limiting.
<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial","sans-serif"">How to map it?</span></i><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">@Lionel, you didn't comment on the man_made=antenna tag (Status:
<span style="color:#222222;background:white">in use</span>) which was also mentioned in the discussion of 2018.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">There is also this proposal from nov 2018 where the man_made=antenna + antenna:application=mobile_phone is suggested (<a href="https://wiki.openstreetmap.org/wiki/Proposed_features/antenna:use" target="_blank">https://wiki.openstreetmap.org/wiki/Proposed_features/antenna:use</a>)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">In any case, I don't have enough experiences on tagging and I will follow what comes out of this discussion.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Best regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Vucodil<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">March 9, 2020 11:39:20 AM CET Lionel Giard <<a href="mailto:lionel.giard@gmail.com" target="_blank">lionel.giard@gmail.com</a>> wrote:<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Cool news that they gave the authorization to use it ! And it is always great to have some interest on the telecom side. :D I'll give what i know and some opinion on the tagging. ^_^<o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">For the tags to use, there was a (rather long) discussion in October 2018 on Tagging mailing list (<a href="https://lists.openstreetmap.org/pipermail/tagging/2018-October/thread.html" target="_blank">https://lists.openstreetmap.org/pipermail/tagging/2018-October/thread.html</a>)
and one output was that the current scheme is probably not good (but nothing was decided) ! :p <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">I had done some manual cleaning on the mast/tower tags 2 years ago i think - i looked at mapillary footage especially for mast/tower along motorways where it is often easy to spot them or did
some survey (and we are not many to map these structure so it was quite easy :p ). And the current tagging scheme should be (following the wiki and what was clarified in the discussion) :<o:p></o:p></span></p>
</div>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">EITHER : <o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">- man_made=mast / tower
</span></b><span style="font-family:"Arial","sans-serif"">(really subjective, as we don't have real difference but mainly: a tower is generally freestanding and often larger diameter/width (think about (often) concrete telecom tower), while a mast generally
have often some guy wires and/or have a small diameter/width (think about metallic mast).<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">- tower:type=communication</span></b><span style="font-family:"Arial","sans-serif""><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">- tower:construction=freestanding / lattice / guyed_lattice / guyed_tube</span></b><span style="font-family:"Arial","sans-serif""> (<a href="https://wiki.openstreetmap.org/wiki/Key:tower:construction?uselang=en-US" target="_blank">https://wiki.openstreetmap.org/wiki/Key:tower:construction?uselang=en-US</a>)<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">- communication:mobile_phone=yes</span></b><span style="font-family:"Arial","sans-serif""> (if GSM, which should be the case for all thse one).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- <b>height=*
</b>(if known)<o:p></o:p></span></p>
</div>
</blockquote>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">OR<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- <b>telecom=antenna</b> (there is no real other tag for antenna alone, and this one is using the telecom=* key as some people want to clarify things).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">- communication:mobile_phone=yes</span></b><span style="font-family:"Arial","sans-serif""> (if GSM, which should be the case for all thse one). <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- <b>height=*</b> (if known).<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">=> Those two are two different things : the first one is a structure that support some antennas (typical GSM mast support multiple antennas), and the second is a standalone antenna (on a rooftop
for example). <b><u>The BIPT only give antennas, so we must first determine if it is standalone or on a mast or tower.</u></b><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">There is no approved tagging of multiple antennas on 1 mast or tower (you mention the "Radio antennas mapping proposal" but it seems really complicated and easy to break with the relations...).
Maybe we should just create <u>a custom belgian tag </u>(similar to how the french are tagging their own infrastructure) for the antenna present like : <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- ref:BE:BIPT=21292<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- ref:BE:Proximus=10DLT_01 (or ref:BE:PXS if we want an abbreviation ?! I did use that in the past on street cabinet but i could change it)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- ref:BE:Orange=1-32264-W1<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- ref:BE:Telenet=_BW4629P<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Following what is in the technical data and their ID (i took one example having the three operators ;-) ). It would keep the different operator information like it is done on street_cabinet
for exemple. It would also be easier to maintain and more difficult to break, because if we put 3 nodes next to each other (1 for each antenna), it would be easily broken by anyone editing the area (especially in ID editor). <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Note that, the operator tag is difficult to assess for the mast or tower structure as it could be any one of the multiple antenna operator or even someone else (and they don't give this information
publicly). So i would not use the operator tag except on individual antenna or mast/tower that would only have 1 antenna. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">We could also use a subtag like antenna=1/2/3/... if we want to give the number of antenna on a same support (mast or tower) ? <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Note that there was some discussion of a "potential" proposal in the discussion to change the tagging of "telecom mast and tower" into something looking more like the "power" scheme. Something
like that :<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- telecom=tower (similar to power=tower grouping everything into one tag) <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- structure=guyed_mast, tubes_mast, lattice, tubular/tubes, ...<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- tower:type=communication<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">- communication:mobile_phone=yes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">=> This proposal is mainly re-using the common tags used for power scheme : structure=* instead of tower:construction (François Lacombe - a french mappers involved a lot in telecom scheme -
was proposing that); and telecom=tower instead of man_made=tower or mast (i was proposing that). It would simplify the tagging as we would tag everything easily and refine only in the structure tag. But that was never formally proposed and approved AFAIK. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">I don't know if you want to go into the rabbit holes of trying to adapt a new tagging scheme for this ahah. <b>Anyway we can use the current scheme as it would be easier now. ;-) </b><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Kind Regards,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Lionel<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Le lun. 9 mars 2020 à 00:36, Midgard <<a href="mailto:midgard%2Btalkbe@janmaes.com" target="_blank">midgard+talkbe@janmaes.com</a>> a écrit :<o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Replying inline to s8evq and Karel:<br>
<br>
Quoting s8evq (2020-03-08 20:20:34)<br>
> What is the point of adding longitude=* and latitude=* to the nodes?<br>
<br>
I had overlooked them, but these tags definitely have to be dropped.<br>
<br>
> How precise are the locations of the antennas in the BIPT dataset? Do we know what the quality of this data is before importing?<br>
<br>
The ten or so that I checked were pretty close, within 5 metres. One was either very recent, or<br>
20 metres off. (BIPT has location 51.151194,3.235139 but there's no structure visible there on<br>
the most recent imagery.)<br>
<br>
In any case, we would get higher quality with a manual review instead of fully relying on the<br>
source: we can correct errors when the structure is visible on imagery.<br>
<br>
> Perhaps my questions sound a bit tough, but I appreciate the effort you put into this.<br>
<br>
Such is an import discussion. Original Poster has my appreciation too :)<br>
<br>
> On Sun, 8 Mar 2020 17:46:38 +0000, Karel Adams <<a href="mailto:fa348739@skynet.be" target="_blank">fa348739@skynet.be</a>> wrote:<br>
> > didn't we<br>
> > have a rule to map only those features visible in the scenery? The BIPT<br>
> > antennae (sic!) are usually attached to existing structures, such as<br>
> > church spires or GSM masts or so? Of course we map those highly visible<br>
> > carrying structures, but to map the individual antennae seems to me like<br>
> > overdoing things.<br>
<br>
Looking at the source data, it's going to be one node for one mast, which typically has several<br>
directional antennas mounted on it. A node per antenna is not something I'd like to see either.<br>
<br>
Off-topic: when referring to the electrical part, "antennas" is actually the most common form. By the way,<br>
could you maybe start trying to behave more constructive and socially acceptable? I believe you can<br>
do it with some effort.<br>
<br>
Kind regards,<br>
Midgard<br>
<br>
_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><o:p></o:p></span></p>
</blockquote>
</div>
<pre>_______________________________________________<br>Talk-be mailing list<br><a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><o:p></o:p></pre>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Talk-be mailing list<br>
<a href="mailto:Talk-be@openstreetmap.org" target="_blank">Talk-be@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-be" target="_blank">https://lists.openstreetmap.org/listinfo/talk-be</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>