<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 29/11/18 22:21, Sergio Manzi wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1b6665c3-e64b-937a-1756-5f6b3fb77799@smz.it">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p><b>At the end of the day... I think this proposal has same
serious issues: the use of an antenna system can be decided
only if you have internal knowledge of what it is actually
used for, not just looking at the antenna. Also, either we
define a very broad range of usage cases or a very fine list
of them (in the hundreds, I guess...). </b>I'll probably vote
against...<b><br>
</b></p>
</blockquote>
<br>
Don't give up! <b><br>
</b>Still thinking about this. Perhaps 'use' is the wrong term?
Could 'system' be better? After all TV is a 'system'? <br>
It is all about the words and there meaning. <br>
<br>
Mappers come to associate a particular antenna with TV so they map
it as a TV antenna, not realising that the antenna frequency and
polarization are specific to their area of the world. That is
fine... it may not be as precise as an 'expert' would map it as but
it is a start. Better than just mapping it as an antenna, has just a
little more detail. The use/system is what most mappers appear to be
tagging. <br>
<b><br>
</b>
<blockquote type="cite"
cite="mid:1b6665c3-e64b-937a-1756-5f6b3fb77799@smz.it">
<p><b> </b></p>
<p>On a broader account, do we really want OSM to become a
"database of the world", with all its details<i>, </i>even fine
technical details which IMHO are more fit to the blueprints of
an infrastructure?</p>
</blockquote>
<br>
Unfortunately mappers will map things as they see them. And some
will want to add more and more detail. <br>
Keeping that detail in some order is what I am on about here. At
present it is all going into antenna:type, system, polarization,
configuration ... everything .. <br>
I'd prefer some more organisation than simply lumping it all
together under one tag. <br>
<br>
<p><br>
</p>
</body>
</html>