Reuses MarkerClusterGroup

[derekmiranda]

MarkerClusterGroup seems to extend LayerGroup so should be fine using
backend-determined clusters while this plugin handles stacked pins. Not sure if this is a regression since @jmensch1 had changed it from MarkerClusterGroup to LayerGroup.

Also, pins at same lat/lng don't seem to automatically spiderfy even though spiderfyOnMaxZoom is enabled by default. Users will have to click on a fully zoomed-in stacked cluster to spread them.

Fixes #{issue number here}

• Up to date with dev branch
• Branch name follows guidelines
• All PR Status checks are successful
• Peer reviewed and approved

Any questions? See the getting started guide

[jmensch1]

Hey @derekmiranda, thanks for the help!

I don't think this is necessarily a regression, since I wasn't thinking of the stacked pins problem when I took out the MarkerClusterGroup originally. If it solves that problem, them I'm all for it.

However, I did notice a different bug that we had before with the MarkerClusterGroup. When you're zoomed all the way in and click on a cluster with stacked pins, they do the spiderify thing. And then if you click on one of the pins, the popup appears for a moment and then disappears. If you click on the cluster again, and then click on the same pin again, it stays open.

I'm not sure if there's a way to fix that. Maybe it should be a new ticket.

[adamkendis]

Thanks for working on this! Agree with what Jake said - no issues with reusing MarkerClusterGroup if it accomplishes what we need. Unfortunately, it did reintroduce the bug in #461 . I reopened the bug ticket in case you wanted to take a look at it.

[adamkendis]

Even with the autoclustering after clicking a pin, this is better than stacked pins. Going to merge this and we can tackle the clustering in another PR.

[derekmiranda]

Hey guys, thanks for reviewing! I'll take a look at the reopened issue