<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Am 28.02.2021 um 15:15 schrieb Bert -Araali- Van Opstal:<br>
</p>
<blockquote type="cite"
cite="mid:b8464b87-42bb-2f1b-06ea-8e15663b0f83@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
I didn't program it nor a specialist but as seen from the aboce,
Nominatim will search for the value you eneter in the search box
in:
<p>the main name key and in the operator key, only when the
amenity is a restaurant or fuel.<br>
In all other cases (except amenity=no) it will look for the
value only in the name key.<br>
There is no specific way as far as I can see to look for the
value post_office in the amenity key.</p>
<p>If you enter post_office as a search value, it comes up with
all POI's where post_office is contained in the name or where
mappers have contained it in another key, like I am seeing lots
of results where addr:housename contains Post office or variant
of that value. Done this way to map for a specific data
consumer, Nominatim ?<br>
The Africans, as usually, solved it by putting the name Post
Office in the name key which is also not good practice. But that
is what users do, being creative if the proposed or approved
tagging doesn't give a feasible solution, for data processing,
for rendering or for mapping purposes, that's the mess you get.<br>
</p>
<p>But please, correct me if I am wrong.<br>
</p>
</blockquote>
<p>No, I think you're near the truth. <span class="VIiyi" lang="en"><span
class="JLqJ4b ChMk0b" data-language-for-alternatives="en"
data-language-to-translate-into="de" data-phrase-index="0"><span>The
problem here: nominatim neglects a lot of different data
(e.g. stop area relations and much more) - mho: The search
is more broken than it really works well. It works for me
not like a search should do in 21st century.....<br>
</span></span></span></p>
</body>
</html>