
Cool! Franco My godfeeling was telling me that this contourline overlay does do something. Did not yet find time to investigate it more properly. I also always have an Europe transparent contourline overlay map on my SSD (in case of...) Probably the lines and numbers are searched without being indexed or because it are numbers, they fill up the first whatever 2.000.000 entries in the index as being sorted on top... Joris -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> Namens franco_bez Verzonden: maandag 1 juni 2020 09:08 Aan: mkgmap-dev@lists.mkgmap.org.uk Onderwerp: Re: [mkgmap-dev] Performance of POI search on the Device Joris Bo wrote
Same for me. Even indexes of maps not 'enabed' are searched and if covering the same area even displays duplicate results. Where I first copied big maps to my Oregon just because there was space enough on the 32GB SSD, now I build smaller maps and rename them if not used that (holi)day(s)
Kind Regards Joris
Hi Joris, I remember having had POIs in the search list that came from disabled maps. That's why I renamed the pre-installed GARMIN maps instead of just diasbaling them. ------------- I made a few tests just now. If I enable all my routable maps for all of Europe (some 7 GiB total) the POI search still is incredibly fast, roundabout 1 second. But if I have one of my non-routable, transparent overlay maps (contourlines for instance) on the SD Card the search speed is going down significantly. I will try if this is triggerd by the "route" option and let you know. Ciao, Franco -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev