
12 Mar
2018
12 Mar
'18
11:52 a.m.
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