[mkgmap-dev] Basecamp crashes on search if searching for many 2+ word phrases

Wed Jun 2 10:48:22 BST 2021

Okay -no removing --split-name-index does not change anything. Still
crashes. I will try to produce a minimalist map that still crashes tonight
then upload the style and options used.

On Wed, 2 Jun 2021 at 12:20, Felix Hartmann <extremecarver at gmail.com> wrote:

> 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.
>
> On Wed, 2 Jun 2021 at 12:07, Gerd Petermann <
> gpetermann_muenchen at hotmail.com> wrote:
>
>> Hi Felix,
>>
>> 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?
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
>> Felix Hartmann <extremecarver at gmail.com>
>> Gesendet: Mittwoch, 2. Juni 2021 10:16
>> An: Thomas Morgenstern; Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] Basecamp crashes on search if searching for
>> many 2+ word phrases
>>
>> https://www.openstreetmap.org/node/3268115540
>> shop=hardware  | shop=trade  [0x2e01 resolution 24]
>> does not crash - it has a full address field. Maybe if we have address
>> for a POI it does not crash?
>>
>> 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.
>>
>> On Wed, 2 Jun 2021 at 11:08, Felix Hartmann <extremecarver at gmail.com
>> <mailto:extremecarver at gmail.com>> wrote:
>> 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).
>> --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.
>>
>>
>> On Wed, 2 Jun 2021 at 10:49, Felix Hartmann <extremecarver at gmail.com
>> <mailto:extremecarver at gmail.com>> wrote:
>> 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?
>>
>> 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?
>>
>> Lets take Verbier Village - it is not a ciy POI
>> https://www.openstreetmap.org/node/8307159228
>>
>> 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]
>> for that one.
>>
>> Cold de Jaman
>> https://www.openstreetmap.org/node/1437437792
>> I have the rule:
>> 0x1c01 resolution 24 continue]
>> [0x11607 resolution 20-21 continue]
>> [0x1151f resolution 22-22 continue
>>  [0x1151f resolution 23-24]]
>>
>> However the first one in my map obviously is 0x1c01 - an old type.
>>
>>
>> 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.
>>
>>
>> On Wed, 2 Jun 2021 at 10:25, Thomas Morgenstern <webmaster at img2ms.de
>> <mailto:webmaster at img2ms.de>> wrote:
>> 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.
>> mfg
>>
>> Am 02.06.2021 um 09:07 schrieb Felix Hartmann:
>> 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.
>>
>> On Wed, 2 Jun 2021 at 08:35, Thomas Morgenstern <webmaster at img2ms.de
>> <mailto:webmaster at img2ms.de>> wrote:
>> Kann ich nicht bestätigen, alle hier genannten Suchen sind erfolgreich
>> ohne Abstutz. BC Ver 4.7.0 und eigene OSM map
>> mfg
>>
>> Am 01.06.2021 um 22:32 schrieb Felix Hartmann:
>> 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.
>>
>> I tested it on my maps, and on other mkgmap created maps and the crashes
>> are more or less happening on all maps.
>>
>>
>> For Switzerland some places causing crashes:
>> Verbier Village
>> Saas Fee
>> Col de Jaman
>> Pic chaussy
>> Pic chosy
>>
>>
>> Also
>> 2) the search must be the first from BC execution
>> 3) if a good search already has been executed (single word), then the
>> crash rarely occurs
>>
>>
>> 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.
>> --
>> Felix Hartman - Openmtbmap.org & VeloMap.org
>>
>>
>>
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>
>> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>>
>>
>> --
>> Felix Hartman - Openmtbmap.org & VeloMap.org
>>
>>
>>
>>
>> --
>> Felix Hartman - Openmtbmap.org & VeloMap.org
>>
>>
>>
>> --
>> Felix Hartman - Openmtbmap.org & VeloMap.org
>>
>>
>>
>> --
>> Felix Hartman - Openmtbmap.org & VeloMap.org
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>
>
> --
> Felix Hartman - Openmtbmap.org & VeloMap.org
>
>

-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210602/a22eeb5f/attachment.html>