<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<link href="chrome://translator/skin/popup.css" type="text/css"
rel="stylesheet">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-11-07 16:26, Sander Deryckere
wrote :<br>
</div>
<blockquote
cite="mid:CABUOUO-qSftUr+E+yNpdt4VE7UxHBpiGJ6r+XEBvFcGkU-dzEg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>On 2014-11-07 13:42, Jakka wrote :<br>
<blockquote cite="mid:545CBE1C.3030203@gmail.com"
type="cite">Marc Gemis schreef op 7/11/2014 om 12:02:
<br>
<blockquote type="cite">There is a new tool on osm.orf
<br>
<br>
At the right you will now find a questionmark. You
can activate it by
<br>
clicking on it. Then click somewhere on the map. You
will get a list of
<br>
all nearby objects with links to the osm details of
those objects
<br>
<br>
groeten/regards
<br>
<br>
</blockquote>
Fijne tool. <br>
Bij proberen zag ik ook 'missing' objecten. <br>
zoals [missing
"nl.geocoder.search_osm_nominatim.admin_levels.level7"
translation] Kortrijk <br>
Idee: <br>
Die 'missing' objecten weglaten wanneer je niet
ingelogd bent. <br>
Heeft een cleaner zicht voor bezoekers. <br>
Jakka <br>
<br>
Google translated:<br>
<blockquote type="cite">Fine tool <br>
When trying I saw 'missing' objects <br>
like [missing
"nl.geocoder.search_osm_nominatim.admin_levels.level7"
translation] Kortrijk <br>
Idea:.. Woman Holding 'missing' objects omit when
you are not logged in. Woman Has a cleaner sight for
visitors. <br>
Jakka</blockquote>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</blockquote>
OK. But just btw, who is Woman? ;-)<br>
<br>
It's another nice feature indeed. Little by little, the OSM map is
getting as and more attractive than Google.<br>
What is a pity is that out of a tennis court, a mini-golf and a
kayak boarding place, this map shows only the tennis.<br>
I made a RENDER suggestion to solve this globally and the general
opinion was against it.<br>
Some call getting mini-golf and kayak visible "tagging for the
renderer" and I call it "tagging for the tourist".<br>
<br>
<blockquote
cite="mid:CABUOUO-qSftUr+E+yNpdt4VE7UxHBpiGJ6r+XEBvFcGkU-dzEg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Dat zijn onze "arrondissementen". Die termen worden
jammer genoeg uit het Engels vertaald, en zijn ook niet
afhankelijk van het land.<br>
<br>
</div>
Zo is bij ons admin_level=9 een deelgemeente, maar het
wordt als "dorp" weergegeven (en "dorp Kortrijk" ziet er
nogal raar uit). Voor admin_level=7 is er dus blijkbaar
geen vertaling (of zelfs geen Engels origineel), en het
zou moeilijk zijn om te vertalen, omdat de term in
Nederland waarschijnlijk anders is.<br>
<br>
</div>
Nu ja, op de Belgische mailing list zal je niemand bereiken
die iets aan die functionaliteit kan veranderen, daarvoor
moet je hogerop, en het waarschijnlijk zelf implementeren.<br>
<br>
Google translated:<br>
<blockquote type="cite">These are our "districts". Those
terms are unfortunately translated from English, and are
not dependent on the country. <br>
Thus in our admin_level = 9th district, but it is
displayed as "village" (and "village Kortrijk" sees kinda
weird out). For admin_level = 7, there is apparently no
translation (or even no English original), and it would be
difficult to translate, because the term in the
Netherlands is probably different. <br>
Well, on the Belgian mailing list you will reach anyone
who could change something about the functionality you
have to probably implement. higher, and the self</blockquote>
</div>
</div>
</div>
</blockquote>
When I made some corrections to Brussels, I had pinpointed "village
Brussels" which is the former municipality.<br>
In fact, I have a theory that boundaries should be much more simply
defined by nesting subareas (UK = England + Wales + Scotland), which
would make the set of borderlines easily automatically computable,
but still continued to be tagged in the boundary relations as a
cache. In that framework, admin_level=X would be totally
superfluous because the nesting determines which boundary relation
is higher or lower in the tree and it could be replaced with sort of
admin_level=municipality, admin_level:fr=commune,
admin_level:nl=gemeente, admin_level:ge=gemeinde,
admin_level:ru=город. This would put two relations of the tree at
the same level when in-between levels are missing, such as between
Belgium and Brussels capital.<br>
But I know it's time lost presenting that to the Tagging list. The
wiki is disparaging subareas in the first place.<br>
<br>
Another nice change is that such names are now written on the sides
of the borderlines. One no longer heads to the wrong direction ;-)
But, because of what we just wrote, when you see Liège next to a
border, you cannot know if it's the (old) town, the municipality,
the arrondissement or the province.<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<div style="top: auto; max-width: 400px; max-height: 354px; bottom:
0px; left: auto; right: 0px; display: none;"
class="translator-theme-original" id="translator-popup">
<div id="translator-popup-toolbar">
<div id="translator-popup-title">
<div id="translator-popup-source-languages-wrapper">
<ul id="translator-popup-source-languages">
<li id="translator-popup-source-language-auto" code="auto">Dutch
- detected</li>
<li code="en">English</li>
<li code="fr">French</li>
<li code="ru">Russian</li>
</ul>
<div id="translator-popup-source-languages-scroller"></div>
</div>
<div id="translator-popup-languages-direction"></div>
<div id="translator-popup-target-languages-wrapper">
<ul id="translator-popup-target-languages">
<li code="en">English</li>
<li code="fr">French</li>
<li code="ru">Russian</li>
</ul>
<div id="translator-popup-target-languages-scroller"></div>
</div>
</div>
<div class="translator-popup-toolbar-spring"></div>
<a title="Copy translated text to clipboard"
href="javascript:void(0);" id="translator-popup-button-copy"></a></div>
<div style="max-height: 304px; opacity: 1;"
class="translator-message-type-normal"
id="translator-popup-message"></div>
<div style="display: none;" id="translator-popup-notice"></div>
<textarea style="display: none;" id="translator-popup-textarea"></textarea></div>
<div style="bottom: 0px; left: auto; right: 0px; top: auto; display:
none;" title="Translating..." class="translator-theme-original"
id="translator-popup-loading"></div>
</body>
</html>