Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread Ticker Berkin
Hi I have two examples where a larger polygon is drawn over smaller ones - near start of 'polygons': leisure=nature_reserve {set mkgmap:drawLevel=75} [0x16 resolution 19 continue] military=danger_area {set mkgmap:drawLevel=75} [0x11 resolution 20 continue] ... mkgmap:drawLevel is used

Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread Andrzej Popowski
Hi Karl, > I tried makling a map using the same draworder > Type=0x050,2 > Type=0x051,2 > plus using the option --order-by-decreasing-area This is some kind of trick, not a general solution. There is no guarantee, that GPS will follow the order of objects in img. And I'm sure you can find

Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread 7770
Hi Ticker. Thanks for the explanation. Yes, i have seen how the etrex HCx does overwrite things as they draw... Regards Karl On måndag 2 november 2020 kl. 19:27:39 CET Ticker Berkin wrote: > Hi Karl > > The default draworder is probably device specific. It has been found > that most polygon

Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread Ticker Berkin
Hi Karl The default draworder is probably device specific. It has been found that most polygon have the same priority, with, for some reason, just a few different - I think there is a wiki page on this. Without --order-by-decreasing area, the output order is as good as random, so one wetland

Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread 7770
The default garmin style (no TYP added), does draw the wetland in the forest. Actually it seems to draw it over the forest (no transparency). This occurs even without the --order-by-decreasing-area. Regards Karl On måndag 2 november 2020 kl. 18:26:42 CET 7770 wrote: > Hi. > No worries. It just

Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread 7770
Hi. No worries. It just means that the map maker must be more thorough. I can see that some makers take this into consideration, but others have not. In effect it means that data is processed, but in the end cannot be shown if the TYP is applied at the end. --order-by-decreasing-area, according

Re: [mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread Ticker Berkin
Hi I understand that many users prefer a fixed order of rendering based on the polygon type, and this is part of the definition of mapnik.txt and seems to be the 'Garmin' way of doing things. If there is a consensus that the draworder should be different, then make it so. I'd think that wetland

[mkgmap-dev] mapnik TYP, forest and wetland

2020-11-02 Thread 7770
Hi. In the example mapnik.txt TYP file, the draworder of the polygons for woods/ forest 0x50 and wetland 0x51 are given like this: [_drawOrder] .. Type=0x050,3 .. Type=0x051,2 .. [End] When compiling a map, this means that wetlands in forests are not visible if this TYP is used. I tried

Re: [mkgmap-dev] TYP file. Descriptions and translations

2020-11-02 Thread 7770
Hi. I have now made my way through adding Swedish text for polygons and lines. File attached. The file is based on the example mapnik.txt from mkgmap versions 4587, 4588. Related to the Polish translation of polygon 0x4f, i have updated it to only Zarośla, this after comments here and checking