<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:690835193;
mso-list-type:hybrid;
mso-list-template-ids:-1252497680 536870913 536870915 536870917 536870913 536870915 536870917 536870913 536870915 536870917;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1016732904;
mso-list-template-ids:730206798;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=en-NL link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>Yes, this has been happening for a very long time (longer than my memory lane).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>My “facts”:<o:p></o:p></span></p><ul style='margin-top:0cm' type=disc><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>Not possible to reproduce;<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>Sometimes it will take hours before the crash occurs. So, I don’t agree: “</span>if a good search already has been executed (single word), then the crash rarely occurs<span lang=EN-GB>”.</span><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>Long, long ago I have tested by uninstall all mkgmaps, which left over City Navigator 2007 (yes; 2007). And still: the error did occur. But harder to reproduce;<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>But also: I have the impression (no fact) that more Maps increases the chance of crashing;<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>I have never seen GPS crash on search (Vista HCx, Etrex 30, GPSMAP 62/66)<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>Find Addresses (Ctrl+Alt+A) will never crash (so: work-around);<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>I have also seen strange addresses found, which do not match my search criteria.<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo3'><span lang=EN-GB style='mso-fareast-language:EN-US'>And – lol – I could reproduce a BaseCamp search which will take 10 minutes to respond. Oeps, or was this a GPS search? Is this a search where BaseCamp will crash (impatience, no retry, no error handling) and GPS will try for 10 minutes and succeed???<o:p></o:p></span></li></ul><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>My work-around:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>Do not use BaseCamp for any Search. Not ever! I use my smartphone + OsmAnd or Google search on second PC monitor.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>I will only test a new version of BaseCamp and until now, it’s always not oké. Still not oké.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>In BaseCamp I can only find an object, if I know where it is….<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>A BaseCamp crash is 99% harmless, but at 1% I lose information (in which case always (...) relevant information, so bad for my mood).<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>But I might have to apologize to Garmin.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>I have always considered BaseCamp to be extreme bad software, but perhaps Garmin is not to blame???<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>If (but only “if”) you are gone investigate and mkgmap might be the cause, I could try “memory lane”.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>I have posted several times on Garmin Vendor forum about searching and not finding or finding the wrong answers or crashing. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>I even might have found a way to reproduce ?????<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>But these posting are all in Dutch language, so therefore: “If and only if”.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>Sorry, too many “???”. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>But I assumed I had managed to suppress my - bad - memories<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'>Eric (AnkEric)<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> <b>On Behalf Of </b>Felix Hartmann<br><b>Sent:</b> woensdag 2 juni 2021 11:20<br><b>To:</b> Development list for mkgmap <mkgmap-dev@lists.mkgmap.org.uk><br><b>Subject:</b> Re: [mkgmap-dev] Basecamp crashes on search if searching for many 2+ word phrases<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Basecamp just closes 0-3 seconds after entering that term into the search bar. No warning, no error notice, nothing. Seems to have been happening a long time already. Okay this evening I will try to produce a map as small as possible that still crashes. I do not have much time now anymore - but will try if removing --split-name-index changes something. I kinda feel it has something to do with split-name-index.<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, 2 Jun 2021 at 12:07, Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com">gpetermann_muenchen@hotmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'><p class=MsoNormal>Hi Felix,<br><br>I couldn't reproduce the crash so far. Please provide a small map and exact instructions how to reproduce. What happens when BC crashes? Do you have some kind of report?<br><br>Gerd<br><br>________________________________________<br>Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>> im Auftrag von Felix Hartmann <<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a>><br>Gesendet: Mittwoch, 2. Juni 2021 10:16<br>An: Thomas Morgenstern; Development list for mkgmap<br>Betreff: Re: [mkgmap-dev] Basecamp crashes on search if searching for many 2+ word phrases<br><br><a href="https://www.openstreetmap.org/node/3268115540" target="_blank">https://www.openstreetmap.org/node/3268115540</a><br>shop=hardware | shop=trade [0x2e01 resolution 24]<br>does not crash - it has a full address field. Maybe if we have address for a POI it does not crash?<br><br>I have to look but I think so far only entries without an address cause a crash. Also it does not crash if being nearby and only searching for one of the words of the entry thereby finding it.<br><br>On Wed, 2 Jun 2021 at 11:08, Felix Hartmann <<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a><mailto:<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a>>> wrote:<br>I just thought about it - could it be related to multi word street search? Maybe what works for multi word street search is not possible for old type POI search? So it is the multi word stuff that got introduced for roads that causes the crashes in Basecamp (not sure about what happens on devices - will check that out later).<br>--add-pois-to-areas --pois-to-areas-placement=entrance=main;entrance=yes;building=entrance;barrier=entrance --link-pois-to-ways --location-autofill=bounds,is_in,nearest and of coure --index are the most relevant to this thread options I am using.<br><br><br>On Wed, 2 Jun 2021 at 10:49, Felix Hartmann <<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a><mailto:<a href="mailto:extremecarver@gmail.com" target="_blank">extremecarver@gmail.com</a>>> wrote:<br>Even though Gerd also speaks German, I think its better to continue in English. I am quite sure that this is the same bug then. Your map does not crash because it find another POI first. I also sometimes have two POI for the same thing - one for finding it via a category POI search, the other for the symbol in the map. I do wonder if you have two POI the order in the style matters? If you change the order they are created - does it crash?<br><br>Could it be that only 0x1234 POI are affected, but the newer 0x12345 types not? As soon as it finds 0x12345 it does not crash?<br><br>Lets take Verbier Village - it is not a ciy POI<br><a href="https://www.openstreetmap.org/node/8307159228" target="_blank">https://www.openstreetmap.org/node/8307159228</a><br><br>I use: highway=bus_stop | amenity=bus_stop | highway=busstop | amenity=busstop | railway=bus_stop {set name='bus_stop ${name}' | 'bus_stop' } [0x2f17 resolution 24]<br>for that one.<br><br>Cold de Jaman<br><a href="https://www.openstreetmap.org/node/1437437792" target="_blank">https://www.openstreetmap.org/node/1437437792</a><br>I have the rule:<br>0x1c01 resolution 24 continue]<br>[0x11607 resolution 20-21 continue]<br>[0x1151f resolution 22-22 continue<br> [0x1151f resolution 23-24]]<br><br>However the first one in my map obviously is 0x1c01 - an old type.<br><br><br>The other ones are a bit bad examples I noticed - because there exists several entries in osm data that could be found with identical name. However I have found no actual city only poi where it crashes - Saas Fee also has other POI named the same. So maybe they cause a crash.<br><br><br>On Wed, 2 Jun 2021 at 10:25, Thomas Morgenstern <<a href="mailto:webmaster@img2ms.de" target="_blank">webmaster@img2ms.de</a><mailto:<a href="mailto:webmaster@img2ms.de" target="_blank">webmaster@img2ms.de</a>>> wrote:<br>Kann sein, dass es am Style liegt. Ich nutze meinen eigenen Style, der z.B einen zusätzlichen POI für Städte einfügt. ich fand vor geraumer Zeit, dass Städte in der MDR nicht eingebbar sind, wenn der String Leerzeichen enthält. Dazu hatte ich auch in der mailinglist gepostet. Hr.Petermann sagte damals, das die MDR für Städte aber nicht anpassbar sei. deshalb hat bei mir jede Stadt noch einen zusätzlichen POI einer anderen Kategorie.<br>mfg<br><br>Am 02.06.2021 um 09:07 schrieb Felix Hartmann:<br>Very strange - I also tested this on "Frezeitkarte" Schweiz and it crashed too. It usually does not crash if you before had a non crash search.<br><br>On Wed, 2 Jun 2021 at 08:35, Thomas Morgenstern <<a href="mailto:webmaster@img2ms.de" target="_blank">webmaster@img2ms.de</a><mailto:<a href="mailto:webmaster@img2ms.de" target="_blank">webmaster@img2ms.de</a>>> wrote:<br>Kann ich nicht bestätigen, alle hier genannten Suchen sind erfolgreich ohne Abstutz. BC Ver 4.7.0 und eigene OSM map<br>mfg<br><br>Am 01.06.2021 um 22:32 schrieb Felix Hartmann:<br>A user of my maps just told me that there are some crashes in the Basecamp search. There is a clear pattern - only search phrases of minimum 2 words with a space between cause crashes.<br><br>I tested it on my maps, and on other mkgmap created maps and the crashes are more or less happening on all maps.<br><br><br>For Switzerland some places causing crashes:<br>Verbier Village<br>Saas Fee<br>Col de Jaman<br>Pic chaussy<br>Pic chosy<br><br><br>Also<br>2) the search must be the first from BC execution<br>3) if a good search already has been executed (single word), then the crash rarely occurs<br><br><br>Not happening with Garmin's own maps. The more entries (POIs) of the name exist - the more likely? Seems to happen more often in the French part of Switzerland compared to the Garmin part. But as many words like Saas Fee do not contain any special characters - I do not think it is related to any codepage problem.<br>--<br>Felix Hartman - Openmtbmap.org & VeloMap.org<br><br><br><br><br>_______________________________________________<br>mkgmap-dev mailing list<br><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br><a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br><br><br><br>--<br>Felix Hartman - Openmtbmap.org & VeloMap.org<br><br><br><br><br>--<br>Felix Hartman - Openmtbmap.org & VeloMap.org<br><br><br><br>--<br>Felix Hartman - Openmtbmap.org & VeloMap.org<br><br><br><br>--<br>Felix Hartman - Openmtbmap.org & VeloMap.org<br><br>_______________________________________________<br>mkgmap-dev mailing list<br><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br><a href="https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><div><div><div><div><div><p class=MsoNormal>Felix Hartman - Openmtbmap.org & VeloMap.org<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></div></div></body></html>