[mkgmap-dev] mkgmap:area2poi placement
From lig fietser ligfietser at hotmail.com on Wed Apr 6 14:57:28 BST 2022
Yes, I've tried to quote it but this does not exclude the poi, it still will be rendered somehow. I've decided to use a workaround, I now make those "unwanted" pois only visible at the lower zoom levels (16-18). This way it is not so obvious that they are way out of the national park boundaries and they will still be searchable in the index. ________________________________ Van: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> namens Ticker Berkin <rwb-mkgmap at jagit.co.uk> Verzonden: woensdag 6 april 2022 06:43 Aan: Development list for mkgmap <mkgmap-dev at lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] mkgmap:area2poi placement Hi The * needs to be quoted in the param list: boundary=* & ... & is_in(boundary, '*', ... Ticker On Wed, 2022-04-06 at 13:02 +0000, lig fietser wrote: > I also want to use it for all boundaries but this line is not > working: > boundary=* & mkgmap:area2poi=true & is_in(boundary,*,in_or_on)=false > {delete boundar _______________________________________________ mkgmap-dev mailing list mkgmap-dev at lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20220406/edd256a2/attachment-0001.html>
- Previous message: [mkgmap-dev] mkgmap:area2poi placement
- Next message: [mkgmap-dev] some findings about NT format
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list