autocomplete - GooglePlacesAutocompleteAdapter (Android Places API) returning results outside of boundary -
it seems sample code google demonstrates google places api android returning results outside of given boundary. (https://github.com/googlesamples/android-play-places/).
searching 'hardware' shows results sydney (the hardcoded boundary), (occasionally) shows results far away other cities (including western australia!). i've implemented googleplacesautocompleteadapter in own code , have found similar results. seems boundary field guideline search; can confirm this?
this may or may not related, know whether results returned places.geodataapi.getautocompletepredictions same results can expected similar call web services places api? few tests seems web services call returns better results (closer location, more relevant, , overall more results). api docs not seem shed light on -- guess perhaps getautocompletepredictions query performed on 'name' of place rather in 'keyword' search per web service api implementation.
thanks help.
as per developer docs, bounds is...
for geographically biasing autocomplete predictions.
this means suggested. results inside preferred, not required.
Comments
Post a Comment