You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: lonvia [Added to the original trac issue at 9.01am, Friday, 10th January 2014]
To clarify, what do you expect as the result, this house http://www.openstreetmap.org/way/28855139?
It can be found in the search results, only it is in the last place. There is something wrong with reordering the results.
Author: Rocksteadyua [Added to the original trac issue at 9.35am, Friday, 10th January 2014]
Replying to [comment:1 lonvia]:
To clarify, what do you expect as the result, this house http://www.openstreetmap.org/way/28855139?
It can be found in the search results, only it is in the last place. There is something wrong with reordering the results.
yes, u right. i receive responce xml in java code, and i believe the correct result on the first place. but it is not
Author: lonvia [Added to the original trac issue at 10.24am, Friday, 10th January 2014]
The order is certainly wrong, 28855139 should come in first place. I suspect that the house number is not taken into account at all when reordering the results but I need to have a closer look at the code to confirm. I've adapted the title of the bug.
Reporter: Rocksteadyua
[Submitted to the original trac issue database at 3.48pm, Wednesday, 8th January 2014]
i tried to find "4 " but received the incorrect result.
browser showed that in the first place at search result is house 16/4
firefos showed that in the first place at search result is house 4 c1
conclusion: it all started with that I was trying to get result through the URL(response XML) and got the wrong result(16/4)
The text was updated successfully, but these errors were encountered: