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
Using Mapbox as the lookup API I'm getting some ommited results
e.g -> "geometry"=>{"type"=>"Point", "coordinates"=>[X, Y], "interpolated"=>true, "omitted"=>true}
I want to accept these results as valid instead of ignoring and using the next one in the array.
Actual behavior
Geocoder actually ignores ommited: true results instead of using them
I'm not sure I understand this issue. Some of the results returned by Geocoder have omitted: true and some don't. Are you saying Geocoder should be handling these results differently?
@alexreisner if the first result is ommited is ignored, the second one is used.
I'd like a way to override this behaviour. To use the first value even if it's ommited
Expected behavior
Using Mapbox as the lookup API I'm getting some ommited results
e.g ->
"geometry"=>{"type"=>"Point", "coordinates"=>[X, Y], "interpolated"=>true, "omitted"=>true}
I want to accept these results as valid instead of ignoring and using the next one in the array.
Actual behavior
Geocoder actually ignores
ommited: true
results instead of using themSteps to reproduce
Geocoder.search("Rua Egas Moniz 8, 1900-218, Lisboa")
Environment info
1.8.3
8.0.1
mapbox
The text was updated successfully, but these errors were encountered: