Hi Gerd,
thanks for updating mkgmap.
I think the idea behind background is to provide an arbitrary shape for
trimming tile area. CGPSmapper doesn't execute trim on mp files, so the
meaning of background is lost.
--
Best regards,
Andrzej
___
Hi Gerd
Thanks for your reply
Yes, I noticed that level 2-4 is allowed as well.
Just going back to an earlier problem,
using the default levels
levels = 0:24, 1:22, 2:20, 3:18
overview-levels = 4:17, 5:16, 6:15, 7:14, 8:12
a) I'm still a bit unclear about what happens if a resolution
a)
Hi Nick,
a)
natural=wood [0x50 level 2-4 ]
is allowed.
b)
a level larger than specified in levels gives an error message. For your
example I'd expect
Error in style: Error: Level number too large, max=5
Not sure if that makes sense. For your example I would have expected that
area_city=* [0x03
Hi Andrzej,
thanks, committed with r4466. I wonder why Background=Y is needed. In most
mkgmap sources a polygon with type 0x4b is a synomym for background.
Gerd
Von: mkgmap-dev im Auftrag von Andrzej
Popowski
Gesendet: Freitag, 13. März 2020 12:35
Version mkgmap-r4466 was committed by gerd on Fri, 13 Mar 2020
backgroundMP.patch by Andrzej Popowski
Improve polish reader compatibility with cGPSmapper reg. background polygon(s)
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4466
___
Hi Gerd,
yes, when I compile my map, I get only object 4b at layer 0. I use
simple definition of background:
[POLYGON]
Type=0x4b
Background=Y
Data0=...
[END]
This works for cGPSmapper, but not for mkgmap. I could add EndLevel=5 to
all my sources, but it was easier to recompile mkgmap, to
Hi Andrzej,
please describe the problem that is solved with this patch. Does it mean that
the background polygon is not added to all levels without the patch?
Gerd
Von: mkgmap-dev im Auftrag von Andrzej
Popowski
Gesendet: Donnerstag, 12. März 2020
