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
On Fri, 18 Feb 2022, 9:31 pm Gunnar Eketrapp, ***@***.***> wrote:
Hi!
I switched from geocoder to geocoder2 since geocoder didn't work anymore.
One of my previous tests that geocoded a point in the Indian Ocean now
started to fail.
This worked better with geocoder then geocoder2 :-)
I can remove that test but I am just curious about if in general geocoder2
is worse than geocoder when it comes to such areas?
For this test below geocoder2 gives ...
formattedAddress: 6HH73GX2+X2
placeId: GhIJmZmZmZmZ8T8RAAAAAADARkA
... which to me is a bit cryptic.
// From coordinates
String? address = await geo.getAddress(LatLng(1.10, 45.50));
expect(address, 'Indian Ocean');
—
Reply to this email directly, view it on GitHub
<#4>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASWKAX333FPANNYI7DTCGD3U3ZULZANCNFSM5OYK3VAQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Hi!
I switched from geocoder to geocoder2 since geocoder didn't work anymore.
One of my previous tests that geocoded a point in the Indian Ocean now started to fail.
This worked better with geocoder then geocoder2 :-)
I can remove that test but I am just curious about if in general geocoder2 is worse than geocoder when it comes to such areas?
For this test below geocoder2 gives ...
formattedAddress: 6HH73GX2+X2
placeId: GhIJmZmZmZmZ8T8RAAAAAADARkA
... which to me is a bit cryptic.
The text was updated successfully, but these errors were encountered: