On 16/08/2016 21:35, Nicolás Alvarez wrote:
Wouldn't that lead to "mapping for the geocoder"? I'm sure that would
be frowned upon as much as "mapping for the renderer".
All tags are 'mapping for the renderer/geocoder/router. Otherwise you
have just black lines, lots of 'You are here' signs
On Tue, Aug 16, 2016 at 09:50:05PM +0200, Hakuch wrote:
> Hey Sarah, do you have documentations that explain how nominatim
> processes the queries? That could be an answer to questions like that one
Not really. You can have a look at the presentation I gave at SOTM
Birmingham[1] but it's a bit
Wouldn't that lead to "mapping for the geocoder"? I'm sure that would
be frowned upon as much as "mapping for the renderer".
--
Nicolás
2016-08-16 16:50 GMT-03:00 Hakuch :
> Hey Sarah, do you have documentations that explain how nominatim
> processes the queries? That could be
Hey Sarah, do you have documentations that explain how nominatim
processes the queries? That could be an answer to questions like that one
On 16.08.2016 21:27, Sarah Hoffmann wrote:
> On Tue, Aug 16, 2016 at 02:29:26PM +0100, Dave F wrote:
>> Hi
>>
>> I've heard a claim from a user who still
On Tue, Aug 16, 2016 at 02:29:26PM +0100, Dave F wrote:
> Hi
>
> I've heard a claim from a user who still wants to use the is_in:*
> tag as well as boundary tags that Nominatim uses is_in as preference
> because "geospacial mathematics is resource intensive".
>
> Is this true?
Not at all.
On 16/08/2016 16:19, Hakuch wrote:
following the wiki, its not deprecated
https://wiki.openstreetmap.org/wiki/Key:is_in
I was surprised when I read that the other day too...
However, I really would love to see a scheme that shows how nominatim
finds it results..
There's the
following the wiki, its not deprecated
https://wiki.openstreetmap.org/wiki/Key:is_in
However, I really would love to see a scheme that shows how nominatim
finds it results..
On 16.08.2016 15:29, Dave F wrote:
> Hi
>
> I've heard a claim from a user who still wants to use the is_in:* tag as
>
Hi
I've heard a claim from a user who still wants to use the is_in:* tag as
well as boundary tags that Nominatim uses is_in as preference because
"geospacial mathematics is resource intensive".
Is this true?
I thought geospacial calculations were fairly light on processing power.
I also
8 matches
Mail list logo