[UX] Ranking of search results with street numbers

[Echolon]

Describe the bug

Hi, my screenshot will help you with a simple example what I would like suggest to improve.

When I search for a specific street, in this example just 'Mönckebergstr. 31' (in Hamburg, Germany), as seen, the app suggest several close locations, but also unrelated stuff. Moreover, the app suggest the target, but ranks it to the 8th place of the list. In between are locations which might interest me, but I don't expext them to be previous to the actual target I typed into the search bar.

Even more, sometimes I have to scroll the list to choose such a specific street/target. Some users might think the app couldn't find the target.

To Reproduce Steps to reproduce the behavior:

1. Search for a specific street with a street number.
2. Watch the search results.
3. The app likely does not rank the acutal street to the very top results. (No error)

Expected behavior Search result with street numbers should have a higher ranking. Don't show unrelated results before.

Screenshots See above.

Versions:

• Transportr Version: 2.0.6
• Device: HTC One M7
• Android Version: Xenon HD, Android 7.1.2

Eventually realted: Let specify street number on search #559

[grote]

IMHO we just take the sorting from the API and don't mess with it ourselves.

[Echolon]

Hi,

yes, was wondering if that is the case. Maybe a simple ranking algorithm would improve the situation. People might think it's the apps fault, but it's actually Deutsche Bahn or so.

[grote]

Feel free to propose "a simple ranking algorithm" that performs better than all providers in all regions and never makes the order worse.

[Echolon]

Yes sure, didn't meant that the work actually is easy.

[ialokim]

The specific case mentioned in #596 is probably easier to implement, putting an identical name of a station first in the list.