Yes, I wanted to ask for the same :) Also, Mapbox looks pretty cool and they use OSM data. The free tier at Mapbox is much more generous than at Google Maps and doesn't require a credit card. Maybe Mapbox could somehow contribute to the development.

I support this idea. It is the big plus of a competitor. FacetWP should have that too.

Our goal isn't to add features for the sake of adding them.

We've stuck with GMaps because its Places API (which our Proximity facet relies on) was light years ahead of competitors.

If it turns out that Mapbox's places search is now on-par with GMaps, then yes we'll definitely consider supporting it too 👍

My basic idea was also rather to extend the map add-on by the OSM / Mapbox functionality. In my opinion, the GMaps Places API is still the undefeated market leader.

But if I understand it correctly, the GMaps Places API is not needed for the Map Add-on, because "only" the geo-coordinates are passed and displayed.

As no payment data has to be stored for the OSM / Mapbox variant, I find it worth an idea. In addition, Google does not exactly make it easy to generate an API key (create billing account, deposit the credit card, etc.).

Support for MapBox, both the maps and more specifically the MapBox Places API would be good.

Benefits are:

• More reasonably pricing
• Privacy Friendly (Google Places API tracks personal data such as IP address, and even more, if user is logged in with a Google Account. It puts off certain users)

@Matt Your goal should be to support your customers in Europe as well. The GMaps plugin is NOT GDPR compliant, hence not usable.

Do you want to keep your European customers? Then meet their needs.

This would be very very nice to implement Openstreetmap