Hi Henning, I don't think that we should apply a bounding polygon only to the overview map. If you compile tiles for whole Germany and produce a map for Bremen using some of these tiles and an overview map that was created with a proper polygon I would assume that this looks strange when you zoom in/out. I don't understand what you mean with maximizing/minimizing the polygon. Please explain. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Henning Scholland <osm@hscholland.de> Gesendet: Freitag, 12. Januar 2018 12:35:04 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] The 0x4b background polygon in the overview map Hi Gerd, I think this would be best and additionally I would suggest to make the polygon defined by user (as suggested in DEM-poly and precomp-sea thread). As default I would limit overview map to the map tiles. Maybe then we should name the parameter --overview-map-polygon=filename I'm not sure, if the actual rectangle should be maximizing the polygon and the map tile area minimizing it or if Garmin doesn't care at all about it. If no external sea-data is given I would keep map tile area as background polygon. Otherwise it will look strange. Henning On 12.01.2018 19:19, Gerd Petermann wrote:
Hi all,
up to now mkgmap always creates a rectangular 0x4b polygon for the overview map. I wonder if I should change that so that the 0x4b polygons of the sub tiles are used. This seems to be the better way if we start using non-rectangular 0x4b polygons?
Gerd _______________________________________________ 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