I was using google maps before I realized how expensive it can be if you have a map heavy app…then I rebuilt things to use leafy as it can access mapbox and stadia
Prior to that I was using the basic google maps element from bubble in conjunction with marker mate
I thought marker mate was awesome and only wish I could still use it with leafy but there seems to be an issue with the two plugins on the same page as marker mate utilizes some HTML that doesn’t get rendered when used with leafy
with marker mate I was able to make some really nice custom marker popups.
I don’t think you’ll find something that does everything you need, however leafy can do these
Leafy looks really cool! Unfortunately, route optimization (finding the most efficient path between two locations with multiple stops) is central to my app, and as far as I can tell, Leafy doesn’t do this (but I’d love for @vini_brito to tell me otherwise).
I have my eyes on that other thread since the first post (:
Since there’s a lot of info I postponed diving into it, but I looked into everything with a quick scan and nothing stood out as a potential problem.
And thanks for the mention!
@harrisonalley Who makes the route optimization is not the map element, but an external API that gives the map the data needed to draw the route (:
So yeah, Leafy can display routes and pretty much anything else, but let’s focus on routes, which already can be attained with the current Get Route from Stadia workflow action (:
I can’t tell how much it is optimized in relation to competing providers, but considering the possibility of someone providing a more efficient route, we can look into pretty much any provider out there and pick one that is more efficient than the routes coming from Stadia.
Or maybe Stadia already uses a standard (which is Valhalla) that is undefeated.
If you want to make progress on this, do send me a message (:
When it doesn’t work, I receive the following general error:
Sorry, we have encountered an unexpected error. Please file a bug report (Help -> Report a bug), including error code 1594825761561x527375957105069600 and a step-by-step explanation of how to reproduce this issue.
And the following error when attempting to pan to a location:
You’re probably going to want to execute those steps separately; first reverse geocoding your list of lat/longs, and then mapping the resulting addresses (since I don’t know of a map plugin that can reverse geocode in bulk).
I also don’t know of any reverse geocoding plugins (though they certainly may be out there), but in my app I use the API connector with Google’s geocoding API to reverse geocode.
I decided to go with the BDK plugin, and use the CoordToAddress calculation.
My use case is plotting users trips to a given city on a map, and the behavior of the map when two people visit the same city is pretty shitty - it puts them both at the exact same address so when you drill down they’re at the exact same address of some random building. So I added some random noise to the lat/long before it picks an address