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
Hello.
I'm trying to incorporate search in my map using the Google Provider, however I'm not able to make it work.
My code is very direct:
const searchControl = new GeoSearch.GeoSearchControl({
provider: new GeoSearch.GoogleProvider({
apiKey: 'MY_GOOGLE_API_KEY'}),
position: 'topright',
style: 'bar',
// provider: new GeoSearch.OpenStreetMapProvider(),
});
map.addControl(searchControl);
If I use the OSM provider (commented out in the code above), the search works fine (the results are kind of obsolete for my region, but it works) (Figure 1) . But if I use the Google Provider, nothing appears as a result of the search (Figure 2).
Some more details:
Both the Maps JS API and the Geocoding API are enabled on the Google Console (BTW, for the GridLayer I'm using GoogleMutant which uses the API key and it's working flawless);
The API key is not under any restriction in the Google Console, since I'm only testing this integration for now;
The browser console outputs this:
I don't think it is related to this problem, but I guess it doesn't hurt to mention it.
The text was updated successfully, but these errors were encountered:
Experiencing the same issue, have tried both key and apiKey. Also same issue hitting the provider directly with await provider.search({ query: "the query" });
Hello.
I'm trying to incorporate search in my map using the Google Provider, however I'm not able to make it work.
My code is very direct:
If I use the OSM provider (commented out in the code above), the search works fine (the results are kind of obsolete for my region, but it works) (Figure 1) . But if I use the Google Provider, nothing appears as a result of the search (Figure 2).
Some more details:
I don't think it is related to this problem, but I guess it doesn't hurt to mention it.
The text was updated successfully, but these errors were encountered: