Hi Felix, the labels which are shown in MapSource / Basecamp search are those which are stored in MDR 15. We change them already with the --mdr7-del option but that doesn't help for the names of route relations. mkgmap reads the full labels from the LBL file in each map tile and calculates the string for MDR15. Still, MDR15 is not used with the device, so this only effects the PC programs. Roads have 4 labels, other objects have only 1. With roads, the first label is rendered, other labels are shown when you click on the road. All labels are indexed, and the --housenumber code sometimes adds labels so that addresses can be found.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecar...@gmail.com> Gesendet: Montag, 13. Dezember 2021 12:29 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Building display.jar fails I tried a couple of places that are cut down to 170 characters - and some I can find in Mapsource or Basecamp, Others I cannot. So 170 is definitely too much for the search index. Is there a way to have separate label for search vs the label on tooltip/printed out on the label? For search it clearly should be less (both Mapsurce and Basecamp). In general it would be good to have a separation between name for search and name for the label. I know we have 4 labels, but I haven*t really understood which label is for what and where which label shows up. On Mon, 13 Dec 2021 at 11:46, Gerd Petermann <gpetermann_muenc...@hotmail.com<mailto:gpetermann_muenc...@hotmail.com>> wrote: Hi Felix, okay, I've committed the changes with r4836. It would be good to know if these long strings cause trouble in MapSource. I wouldn't be surprised to find that they cause buffer overflows if Garmin doesn't expect more than N bytes, and that again can cause all kinds of trouble. Will try to reproduce the problem with a modified default style ... Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk<mailto:mkgmap-dev-boun...@lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <extremecar...@gmail.com<mailto:extremecar...@gmail.com>> Gesendet: Montag, 13. Dezember 2021 11:32 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Building display.jar fails it's working fine for me too. But I haven't got around to testing if the length should even be shorter related to search.function. Clearly anything over 170 is not useful. Maybe it should be even shorter, but apart from the value it works well On Mon, 13 Dec 2021 at 10:28, Ticker Berkin <rwb-mkg...@jagit.co.uk<mailto:rwb-mkg...@jagit.co.uk><mailto:rwb-mkg...@jagit.co.uk<mailto:rwb-mkg...@jagit.co.uk>>> wrote: Hi Gerd I don't have any problem with it Ticker On Mon, 2021-12-13 at 09:02 +0000, Gerd Petermann wrote: > Hi all, > > I got no feedback on the patch label_len170.patch. Any comments? > > Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk><mailto:mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Felix Hartman - Openmtbmap.org & VeloMap.org _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev