Search in points nonsensically considers code of photo icons

[Graf Geo]

Hello Menion,

I've always wondered why the search in points sometimes returns results that have nothing to do with the search word or search string.

I just took a closer look and realised that this only happens if an attached photo was used as an icon for the point. If I replace the photo icon with a symbol, the corresponding point is no longer found.

I then exported such a point as a gpx file and looked at it with an editor. And indeed: The photo icon generated by Locus is coded with an exorbitantly inflated cryptic character salad (over 10,000 characters!!!). This even appears twice in the code, once between the tags <sym>...</sym> and again between the tags <locus:icon>...</locus:icon>.

Example:

<sym>image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEAAAABLCAYAAADAroEdAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAACAASURBVHic5Zt5jGXZfdc/v3POXd5S79XaVdU93T09S0+7x54x9owdj23i4CWON0jk ... (further >10000 characters)</sym>

<locus:icon>data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEAAAABLCAYAAADAroEdAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAACAASURBVHic5Zt5jGXZfdc/v3POXd5S79XaVdU93T09S0+7x54x9owdj23i4CWON0jk ... (further >10000 characters)</locus:icon>.

Even if the string of characters is cryptic and only rarely corresponds to a search string, it makes no sense for the search to include this code. If I search for "heu", for example, the point is found because the code contains hEU (see red font).

Is it even necessary to generate such a long code for the photo icons? And can't it be excluded from the search?

Supplement: This happens both in the official Locus version and in the new My Library version.

[Graf Geo]

Even more unwanted search results:

The search in descriptions also finds the addresses/street names that are automatically added to the shaping points (and via points) for planned routes.

I don't know whether this makes sense. These are not consciously entered and so you have no control over what is being searched for... Many planned tracks are found just because the search string is contained in some street name of some shaping point.

The search should be limited to the name of the point/track and (if the option is activated) your own description. Anything else will only lead to unwanted search results.

(Or offer another deactivatable checkbox: "Search also in shaping and via points".)

[Menion]

Thanks for the precise report. Uff, such nasty issue.

I'll keep this issue as "unsolved" for me and look at it next week(s) when working again on the new My Library V2 (because the search is created from scratch so it make sense to fix it there only).

[Menion]

Ahh, got it. Thanks a lot. Will be improved/fixed in the next "My library" version!