OpenTransitTools-BonePile / trimet-mod-pelias

TriMet MOD Pelias ... related to https://github.com/conveyal/trimet-mod-otp
1 stars 0 forks source link

result sorting #6

Closed fpurcell closed 5 years ago

fpurcell commented 6 years ago

result sorting

fpurcell commented 6 years ago

Here, the search service weights multiple (fallback) records with the same weight, but the sorting is not clear why a point farther away appears higher in the response:

PELIAS QUERY: https://ws-st.trimet.org/pelias/v1/search?text=888%20SE%20Main%20St

image

fpurcell commented 6 years ago

NOTE: weighting 'interpolated' hits higher than 'fallback' hits is perfectly reasonable, despite the distance. So the following result is preferred.

PELIAS QUERY: https://ws-st.trimet.org/pelias/v1/search?text=822%20Main%20St

image

fpurcell commented 6 years ago

https://ws-st.trimet.org/pelias/v1/search?text=1800%20SE%20MLK%20Blvd

A handful of random addresses that basically match '1800 SE .* Blvd' come back via search with the same confidence value, but the sorting based on distance didn't happen.

image

fpurcell commented 6 years ago

https://ws-st.trimet.org/pelias/v1/autocomplete?text=Fred%20Meyer%20HOP doesn't even try on distances, I've found.

fpurcell commented 6 years ago

Still Funky (when filtering on stops layer):
https://ws-st.trimet.org/pelias/v1/search?text=834%20SE%20Lambert&sources=transit&layers=stops

fpurcell commented 5 years ago

going to close for now, since in practical use sorting, feels pretty good --- will reopen if need be from future user feedback