MapExtender style overwriting? Can't load any style +16 days ago

[scmuses]

believe that’s all information we’ve seen. You could reference the Google’s Address location service and the result of the search (Bloc Almo 3, Șoseaua Mihai Bravu, Bucharest, Romania) which may help them find the issue faster: https://www.google.com/maps
Hope this helps.

I got this answer from bubble:

The problem here is being caused by the fact that the search box is returning exact geographic places (longitude / latitude) while the plugin appears to be using street addresses. This makes sense because the plugin appears to provide driving directions.

Bubble’s search box can be thought of as an extension of Google’s Places APIs (different from the Maps Javascript API). The search box in particular uses the Google Places API to validate exact geographic locations down to the exact latitude and longitude instead of the nearest street address. It’s important to use this when using the “geographic place” data type within your app because only validated geographic locations can be used for these types of data. Using regular text may not provide the desired effect.

It makes sense here to work with the plugin’s developer to determine if the Places API can be used to retrieve more exact geographic data (or simply data more in line with the Places API). This way, the plugin will return the same location as the search box. Again, the built-in search box only returns validated geographic locations / places as provided directly from Google’s APIs.

[Dumitru]

Hello @scmuses

Thanks for getting back with the information from Bubble. We’ll need check this out if it’s feasible to push for update.
At the moment, the solution is to use the plugin as it was set in our demo. With a simple input element formatted as text.
Demo: https://zeroqode-demo-12.bubbleapps.io/map_extender

Thanks for understanding.

[scmuses]

Thanks for getting back with the information from Bubble. We’ll need check this out if it’s feasible to push for update.
At the moment, the solution is to use the plugin as it was set in our demo. With a simple input element formatted as text.

Thank you for the answer but it’s not a possible option to use the input element. We need to use a search box because we permit to use to search their address and give similar options while typing. Basically, its a map with from - to addresses and with input element won’t work as we need.

We got an additional answer from bubble:
“An option would be the plugin’s developer to allow using exact geographic coordinates when calculating routes. Or possibly using the Google Places API.”

[Dumitru]

Hello @scmuses

Thanks for providing additional notes.

I’m afraid Bubble’s provided information is no feasible for us, since we’ll basically implement the same set of features which are available already in Bubble framework. Meaning we’ll re-create same search box which will use Google Places API in order to get the address.
The plugin is used to retrieve the street address in order to provide driving directions, that is why we use an input and not a search address box.
Using the exact geographical coordinates to calculate the routes will change the existing algorithm of the plugin, which works as intended at the moment.
You can use Bubble search box option by accepting that you may not always be able to get the address you want because that is how Google processes your input and gives you the address which is more consistent due to their API.
Or you can use a simple text field where you can enter the address manually, and get the desired result.

Thanks for understanding.

Regards,
Dumitru.

[scmuses]

Oh wow @Dumitru what bad news… I can’t use the plugin like that…

If there was a way as said @c6648481 to give to users option to add the address manually (drawing in the map) using the bubble option “map center address” exposed state of the map element we could try to find another way to fix this.

We have tried either to add another map without targeting it to Mapextender but it seems it never loads…
If this feature is available under Mapextender exposed state (map center address) we can build a fix for this ourselves or just the Mapextender not killing other non-targeted maps.

Thanks.

[scmuses]

Hello again @Dumitru, have checked your answer when you said this was Bubble issue about how they process directions.

I have been doing many tests and it seems this issue only occurs with this plugin. Been doing tests with one Google Maps (free plugin by AliFarhat) and the directions action is very different:

So I’m very sure this is not a Bubble issue as they said it’s an issue with the plugin.
As you can see in the same directions (left map zeroqode plugin) vs (right map free plugin).

How this is possible?

[Dumitru]

Hello @scmuses

As it was mentioned before, the fact that the search box is returning exact geographic places (longitude / latitude) while Map Extender plugin is using street addresses because the plugin provides driving directions that is way the return state differs.
The algorithm for getting the position for the marker to render accordingly using street addresses provided by the API.
The geocoder will attempt to find the closest addressable location within a certain tolerance and provide a street address that is readable for the user.