Hi Joris,

again, what would be the result? Remember that a POI is more than just the icon 
on the map. Besides the name I may have an address, a phone number and so on. 
If we replace them by a single POI, what would be the content of those fields?
Thinking of it the code should probably be changed to compare those fields as 
well and to prefer the one that has more information.

Gerd

________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag von Joris 
Bo <[email protected]>
Gesendet: Donnerstag, 18. Juni 2020 12:26
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Nearby poi feature

Hi Gerd,

I tried to unclutter the bunge of symbols by just hiding a couple of them 
allowing other poi's and lables to come through and be displayed in stead of 
'pushed away' by a clutter of the same symbols. That works perfect for bins, 
benches, parkings , silo's etc. because they rarely have names.

So its not directly related to the "doctors office". My eye fell on them as an 
example because I expected them to be filtered out.
It's no big deal, just would be nice. It is because the manual really gave me 
the idea that it works that way that I spent time on it.

Kind regards

Joris


-----Oorspronkelijk bericht-----
Van: mkgmap-dev <[email protected]> Namens Gerd Petermann
Verzonden: donderdag 18 juni 2020 12:08
Aan: Development list for mkgmap <[email protected]>
Onderwerp: Re: [mkgmap-dev] Nearby poi feature

Hi  Joris,

The current code always groups the POI by type AND name.
What result would you expect for the different doctors?

Gerd

________________________________________
Von: mkgmap-dev <[email protected]> im Auftrag von Joris 
Bo <[email protected]>
Gesendet: Donnerstag, 18. Juni 2020 11:46
An: Development list for mkgmap
Betreff: [mkgmap-dev] Nearby poi feature

Hello,

I'm struggling with the nearby poi rules. As far as I understand from the 
manual there are 3 options
named: triggered if the type code and the name is the same
unnamed: triggered if the type code is the same and the name is empty no 
specification: triggered if the type code is the same regardless of the name 
being the same

But if I use 0x3002:10   on a docters clinic with 9 doctors all having 
different names, obvious closer together then 10 meters nothing happens
When adding multiple rules for the same typ-code I get a SEVERE error message 
(which is correct and proofs the correct nearby - config-rules - file is in 
use) When hiding trees next to the doctors (just to be sure the correct code is 
triggered) the unnamed trees are hidden as expected When rendering the doctors 
as typ-code trees, again nothing happens. So it's not in the the typ-code used 
and I can only assume that I just can't hide poi's when the name is different?

Maybe somebody could help explain what can be expected

If interested in the test area:
https://www.openstreetmap.org/#map=19/49.75947/6.64167
https://www.openstreetmap.org/#map=19/49.75841/6.64698


Kind regards,

Joris

_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
[email protected]
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Reply via email to