Hi all, I think the Garmin renderer only uses the information from the RGN file. This contains the geometry of the points, lines and shapes, the type and pointer(s) to the labels. No idea how the renderer decides where to render a highway shield. I also cannot reproduce the problem with the default style. I assume the style used by Joris adds multiple ways for one OSM way, maybe with different labels ? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von osm@pinns <osm@pinns.co.uk> Gesendet: Montag, 12. März 2018 13:12:32 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Limit the number of highway shields in basecamp and gps Hi Henning I think you are right - I have in the past been guilty of forcing labels on certain long distance walking routes by cutting the highway ! I wonder , Gerd, if it is possible to only add a shield if highway's length > a length defined by the user? Nick On 12/03/2018 11:52, Henning Scholland wrote:
Hi Gerd, Maybe it helps for brainstorming to understand how the Garmin-container is working.
So far I understand we take osm-way, shifting each osm-node to closest Garmin-node, this then is written somehow to the map. But how all these information are stored. Is the way-geometry stored once and the linked to routing-data and drawing-data, or are they independent?
Basically I'm thinking, if rendering-ways can be merged while routing-way is splitted more detailed. I think this might improve the rendering of labels. So far I know Garmin-Software later just place the labels per way. So if we have a lot of small ways, there will be too many labels.
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