Search for POI not ordered by distance

[Clipper11]

Hi,

If have a question to the search order lineup in osmand version 4.3.8
I am in Germany, 73116 Wäschenbeuren and I am searching for 'Wertstoffhof' (recycling station)
If I am doing that, the nearest poi will not shown as first. This is confusing. Can I influence that in the settings, or is this an error?
The nearest is 290 meter, but listed not as first. Screenshot attached

Thanks for your support.
best regards
Marius

[vshcherb]

That's done to prioritize precise name matches which in some situations are more important - #13797

[mariush444]

look at your comments please

can you show how your navi calculates this case in 2 minutes, please?

start point 49.00537 8.40449
end point 52.10229 7.40721
Graphhopper does it in less than 5 seconds.

[vshcherb]

I don't think we should continue routing discussion here it only makes it's offtopic - just for the record this route takes 427 km - 1 300 000 (> 1 000 000 that considered reasonable) - ~3 min calculation S21, and it's not related that OSRM algorithms could do in 1 seconds that A* algorithms are stuck)

[vshcherb]

Nothing wrong with the comments all 2 issues are related to this topic

[mariush444]

so maybe there is other problem.
My calculation take more than 30 minutes and don't finish with any result.
There is info about not loaded maps but there are loaded and "check the necessary maps" doesn't help.

What map do you use? I downloaded full and for second test I downloaded roads only. No positive result.

Maps are from februare 2023

[vshcherb]

Not enough memory you can put it higher in Development Settings but it might crash.

[mariush444]

How much memory does your S21 have?

…

-------- Wiadomość oryginalna -------- Od: ***@***.*** Wysłane: 14 lutego 2023 16:32:59 CET Do: ***@***.*** DW: Mars Yush ***@***.***>, ***@***.*** Temat: Re: [osmandapp/OsmAnd] Search for POI not ordered by distance (Discussion #16344) Not enough memory you can put it higher in Development Settings but it might crash.

-- Reply to this email directly or view it on GitHub: #16344 (reply in thread) You are receiving this because you commented. Message ID: ***@***.***>