[mkgmap-dev] Performance of POI search on the Device

Mon Jun 1 07:58:25 BST 2020

For holidays I create a special map which covers the area I want to cylce. I remove all other maps and also all tracks that I have for my home area.
My planned track is divided into chunks of 50km (was 100km, still experimenting with the size) and the parts have very simple names like part-1, part-2, part-3 ... part-70. I think smaller parts are loaded much faster and - more important for me - the height profile is easier to use. In the morning I change the track color of those parts which I already cycled and check the height profile of the comming parts.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Joris Bo <jorisbo at hotmail.com>
Gesendet: Montag, 1. Juni 2020 08:33
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Performance of POI search on the Device

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

-----Oorspronkelijk bericht-----
Van: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> Namens Gerd Petermann
Verzonden: maandag 1 juni 2020 08:21
Aan: mkgmap-dev at lists.mkgmap.org.uk
Onderwerp: Re: [mkgmap-dev] Performance of POI search on the Device

Hi Franco,

I had the same problem with my Oregon and found out that the existence of a 2nd map triggered this. For a test I renamed the 2nd map to *.img_ and was very surprised that this solved the search problem. In my case, the 2nd map was the cycling layer TK-Europe-Bicycling from Thomas Kukuk, but I have no idea why it causes the problems. I assume there is a firmware bug in the Oregon.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von franco_bez <franco.bez at web.de>
Gesendet: Montag, 1. Juni 2020 07:16
An: mkgmap-dev at lists.mkgmap.org.uk
Betreff: [mkgmap-dev] Performance of POI search on the Device

Hi all,

searching for POIs on my Oregon often is very frustrating. It virtually takes forever.
Yesterday I noticed that some POI types are reasonably fast, while others are 10 times slower.

I assume that this is some sort of index Problem.

For example
using my DACH map, built with mkgmap-r4506, map size 2.7GiB on my Oregon 750t
- searching for Gas Stations takes some 5 seconds
- searching for Bank/ATM takes some 50 seconds
- searching for Any-/All Poi types also takes some 50 seconds for the first Elements to appear in the list.

If I can trust my memory, in the past, maybe some 2 years ago, searching for Gas Stations was just as slow as any other POI type.

What can I do to get the POI search fast for any POI type in the map ?
I tried --make-poi-index but this didn't make any noticeable difference.

Ciao,
 Franco

--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev