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.
Leliestraat, Hattem, Berghuizen, Zwolle, 8051EH, Gelderland, Nederland
Leliestraat, Rouveen, Staphorst, 7954, Overijssel, Nederland
Leliestraat, Zwolle, Schelle, 8012, Overijssel, Nederland
Leliestraat, Zwolle, Schelle, 8013, Overijssel, Nederland
Because Hattem is a city besides Zwolle, it is in the same region. So that's why Hattem is also included in this results. Now this is no problem, but because Zwolle is a city in itself, Zwolle should be higher in the order then Hattem.
So I suggest to put in the sorting algoritm, a relevance options. Maybe on the client side instead of the database side, because tsearch doesn't support that currently.
The text was updated successfully, but these errors were encountered:
Author: twain [Added to the original trac issue at 10.31am, Tuesday, 30th March 2010]
Replying to [ticket:2845 michiel[at]ict4schools.nl]:
So I suggest to put in the sorting algoritm, a relevance options. Maybe on the client side instead of the database side, because tsearch doesn't support that currently.
Reporter: michiel[at]ict4schools.nl
[Submitted to the original trac issue database at 10.27pm, Monday, 29th March 2010]
The order of the results are not ordered correctly by relevance.
Searching for example on:
Leliestraat 31, Zwolle (http://nominatim.openstreetmap.org/search?q=Leliestraat+31%2C+Zwolle&viewbox=-225%2C82.34%2C225%2C-74.45)
Gives the following results:
Because Hattem is a city besides Zwolle, it is in the same region. So that's why Hattem is also included in this results. Now this is no problem, but because Zwolle is a city in itself, Zwolle should be higher in the order then Hattem.
So I suggest to put in the sorting algoritm, a relevance options. Maybe on the client side instead of the database side, because tsearch doesn't support that currently.
The text was updated successfully, but these errors were encountered: