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

Hi Gerd, I tried out my old Oregon 550 and my ZUMO 396 The Oregon 550 behaves almost identical to the Oregon 750t. The boundary layer slows down the POI search by factor 10. Round about 1 sec without and 9 sec with the boundary layer. If I put all transparent layers on the SD Card it's 50 sec. I assume the biggest impact comes fron my contourlines layer with DEM Data for all of Europe (3,7GB size). The Zumo seems to be faster. The boundary layer is no big problem (maybe 1 sec penalty). But when I put my contourlines layer on the Zumo it slows down extremely. The GARMIN Firmware bug seems to affect several devices, if not all. Ciao, Franco

Hi Franco, one of my other ideas was a semi-transparent map where the transparent flag is set but the 0x4b polygon is still added to the map. Made no difference. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Franco Bez <franco.bez@web.de> Gesendet: Samstag, 6. Juni 2020 10:39 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Performance of POI search on the Device Hi Gerd, I tried out my old Oregon 550 and my ZUMO 396 The Oregon 550 behaves almost identical to the Oregon 750t. The boundary layer slows down the POI search by factor 10. Round about 1 sec without and 9 sec with the boundary layer. If I put all transparent layers on the SD Card it's 50 sec. I assume the biggest impact comes fron my contourlines layer with DEM Data for all of Europe (3,7GB size). The Zumo seems to be faster. The boundary layer is no big problem (maybe 1 sec penalty). But when I put my contourlines layer on the Zumo it slows down extremely. The GARMIN Firmware bug seems to affect several devices, if not all. Ciao, Franco _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd, I did a little more testing. Is it possible that the presence of a complete address is the trigger ? I tried building maps with the Places POIS forĀ cities, towns and villages. It didn't help at all, search for POI is still slow. When I put the POIs for the fuell stations, the search is fast. The only difference, safe the type of course, is that the fuell stations usually have a complete postal address attched, while the city centers do not. Here's a sample for the map with the city POIS: |http://files.mkgmap.org.uk/download/482/POI_BAD_dach_boundary_gmapsupp.img||| Ciao, Franco Am 06.06.20 um 14:46 schrieb Gerd Petermann:
Hi Franco,
one of my other ideas was a semi-transparent map where the transparent flag is set but the 0x4b polygon is still added to the map. Made no difference.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Franco Bez <franco.bez@web.de> Gesendet: Samstag, 6. Juni 2020 10:39 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Performance of POI search on the Device
Hi Gerd,
I tried out my old Oregon 550 and my ZUMO 396
The Oregon 550 behaves almost identical to the Oregon 750t. The boundary layer slows down the POI search by factor 10.
Round about 1 sec without and 9 sec with the boundary layer.
If I put all transparent layers on the SD Card it's 50 sec. I assume the biggest impact comes fron my contourlines layer with DEM Data for all of Europe (3,7GB size).
The Zumo seems to be faster. The boundary layer is no big problem (maybe 1 sec penalty). But when I put my contourlines layer on the Zumo it slows down extremely.
The GARMIN Firmware bug seems to affect several devices, if not all.
Ciao,
Franco
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Franco, yes, see my post http://gis.19327.n8.nabble.com/Performance-of-POI-search-on-the-Device-tp596... While looking at this I got lost in the code of the Locator which should help to fill the address data. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Franco Bez <franco.bez@web.de> Gesendet: Mittwoch, 10. Juni 2020 13:57 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Performance of POI search on the Device Hi Gerd, I did a little more testing. Is it possible that the presence of a complete address is the trigger ? I tried building maps with the Places POIS for cities, towns and villages. It didn't help at all, search for POI is still slow. When I put the POIs for the fuell stations, the search is fast. The only difference, safe the type of course, is that the fuell stations usually have a complete postal address attched, while the city centers do not. Here's a sample for the map with the city POIS: |http://files.mkgmap.org.uk/download/482/POI_BAD_dach_boundary_gmapsupp.img||| Ciao, Franco Am 06.06.20 um 14:46 schrieb Gerd Petermann:
Hi Franco,
one of my other ideas was a semi-transparent map where the transparent flag is set but the 0x4b polygon is still added to the map. Made no difference.
Gerd
________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Franco Bez <franco.bez@web.de> Gesendet: Samstag, 6. Juni 2020 10:39 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Performance of POI search on the Device
Hi Gerd,
I tried out my old Oregon 550 and my ZUMO 396
The Oregon 550 behaves almost identical to the Oregon 750t. The boundary layer slows down the POI search by factor 10.
Round about 1 sec without and 9 sec with the boundary layer.
If I put all transparent layers on the SD Card it's 50 sec. I assume the biggest impact comes fron my contourlines layer with DEM Data for all of Europe (3,7GB size).
The Zumo seems to be faster. The boundary layer is no big problem (maybe 1 sec penalty). But when I put my contourlines layer on the Zumo it slows down extremely.
The GARMIN Firmware bug seems to affect several devices, if not all.
Ciao,
Franco
_______________________________________________ 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
participants (2)
-
Franco Bez
-
Gerd Petermann