Re: [mkgmap-dev] Feature request: Layer control
Hi, I think you have to change the DrawOrder in your TYP-file. This tells the Garmin-device in which order the polygons should be rendered. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Feature request: Layer control
As I already mentioned, TYP-files are NOT supported by devices from the Garmin marine line-up (GPSMap 421, GPSMap 526, GPSMap 720 ...). All Garmin nautical chartplotters simply ignore the information in the TYP-file. -Ursprüngliche Nachricht- Von: mkgmap-dev-boun...@lists.mkgmap.org.uk [mailto:mkgmap-dev- boun...@lists.mkgmap.org.uk] Im Auftrag von Henning Scholland Gesendet: Donnerstag, 11. Oktober 2012 09:26 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Feature request: Layer control Hi, I think you have to change the DrawOrder in your TYP-file. This tells the Garmin-device in which order the polygons should be rendered. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Feature request: Layer control
I think even if you define the order, it won't really workout well. Also you would need to check if all devices have the same order. At least on the consumer GPS side, Garmin turned the draw order upside down in newer vs older generation gps devices (same holds true for old Mapsource 6.13 vs Basecamp =v3). Maybe there would be a need for proper overlay checking with blacklists which types may not be in the same area as others, and then mkgmap cutting out some polygons. Or mkgmap cutting out smaller polygons from larger ones, similar to how mapnik does it... I cannot imagine this to be easy though (because I cannot even come up with a clean concept on how this should be done). On 11.10.2012 12:28, RheinSkipper wrote: As I already mentioned, TYP-files are NOT supported by devices from the Garmin marine line-up (GPSMap 421, GPSMap 526, GPSMap 720 ...). All Garmin nautical chartplotters simply ignore the information in the TYP-file. -Ursprüngliche Nachricht- Von: mkgmap-dev-boun...@lists.mkgmap.org.uk [mailto:mkgmap-dev- boun...@lists.mkgmap.org.uk] Im Auftrag von Henning Scholland Gesendet: Donnerstag, 11. Oktober 2012 09:26 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Feature request: Layer control Hi, I think you have to change the DrawOrder in your TYP-file. This tells the Garmin-device in which order the polygons should be rendered. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- keep on biking and discovering new trails Felix openmtbmap.org www.velomap.org ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Feature request: Layer control
Cutting out holes will be the best solution off course. In case of the riverbank and fairway multipolygons, fairway has also to be considered as the inner multipolygon of the riverbank. But for the buildings it will be more complicated as there are more tags involved. I really hope you can find a solutions for this problem. The Openseamap project will provide a lot more waterdepth information (crowd sourced and from official sources) in the near future. In my eyes all this is useless until we can render shaded depth areas on a Garmin chartplotter. -Ursprüngliche Nachricht- Von: mkgmap-dev-boun...@lists.mkgmap.org.uk [mailto:mkgmap-dev- boun...@lists.mkgmap.org.uk] Im Auftrag von Felix Hartmann Gesendet: Donnerstag, 11. Oktober 2012 12:46 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Feature request: Layer control I think even if you define the order, it won't really workout well. Also you would need to check if all devices have the same order. At least on the consumer GPS side, Garmin turned the draw order upside down in newer vs older generation gps devices (same holds true for old Mapsource 6.13 vs Basecamp =v3). Maybe there would be a need for proper overlay checking with blacklists which types may not be in the same area as others, and then mkgmap cutting out some polygons. Or mkgmap cutting out smaller polygons from larger ones, similar to how mapnik does it... I cannot imagine this to be easy though (because I cannot even come up with a clean concept on how this should be done). On 11.10.2012 12:28, RheinSkipper wrote: As I already mentioned, TYP-files are NOT supported by devices from the Garmin marine line-up (GPSMap 421, GPSMap 526, GPSMap 720 ...). All Garmin nautical chartplotters simply ignore the information in the TYP- file. -Ursprüngliche Nachricht- Von: mkgmap-dev-boun...@lists.mkgmap.org.uk [mailto:mkgmap-dev- boun...@lists.mkgmap.org.uk] Im Auftrag von Henning Scholland Gesendet: Donnerstag, 11. Oktober 2012 09:26 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Feature request: Layer control Hi, I think you have to change the DrawOrder in your TYP-file. This tells the Garmin-device in which order the polygons should be rendered. Henning ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- keep on biking and discovering new trails Felix openmtbmap.org www.velomap.org ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Feature request: Layer control
On 11/10/2012 11:45, Felix Hartmann wrote: I think even if you define the order, it won't really workout well. Also you would need to check if all devices have the same order. At least on the consumer GPS side, Garmin turned the draw order upside down in newer vs older generation gps devices (same holds true for old Mapsource 6.13 vs Basecamp =v3). Maybe there would be a need for proper overlay checking with blacklists which types may not be in the same area as others, and then mkgmap cutting out some polygons. Or mkgmap cutting out smaller polygons from larger ones, similar to how mapnik does it... I cannot imagine this to be easy though (because I cannot even come up with a clean concept on how this should be done). RheinSkipper I ran a small test with a number of overlapping polygons made OSM files with these objects in different orders. The OSM file with the top polygons listed last worked correctly, implying that the device being used rendered these objects in first-to-last order. If a user's device rendered in reverse order, then that user could simply specify their layer parameters with values high-to-low rather than low-to-high. Our suggested method ought to cause the least implementation work, as it would not require any low-level hacking of mkgmap. ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Feature request: Layer control
Hi, I have a serious problem with making maps for Garmin´s marine devices: Marine devices do not support type files. So it is not possible to control the priority of polygons. I have the following lines in my polygons style file: waterway=riverbank [0x10303 resolution 18] seamark:type=fairway [0x10304 resolution 22] The fairway polygons should be drawn always on top of the riverbank polygons. But sometimes the fairway is drawn below the riverbank and covered by this. We found out that this behavior is depending on the order in which the polygons occur in the osm file. This problem occurs not only with those water depth areas. Buildings are also covered by landuse polygons. It will be necessary to sort those critical polygons out an render them later on top of the rest. If one could specify layers like waterway=riverbank [0x10303 resolution 18 layer 0] seamark:type=fairway [0x10304 resolution 22 layer 1] and that mkgmap scanned the input once for each layer value in ascending order (with default as layer 0), then one could control which polygon is drawn last and on top. Jürgen test.rar Description: Binary data ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
