Open aavmurphy opened 2 years ago
@aavmurphy Thank you for opening this issue. 🙏 Please check out these other resources that might be applicable:
google-maps
tagThis is an automated message, feel free to ignore.
Thanks for capturing these. There are definitely some tradeoffs that were made and I think this library was an early attempt to provide the flexibility that was lacking in previous versions.
One of the questions going forward will be additional forms of rendering. The previous marker clustering implementation used google.maps.OverlayView
and had significant challenges around a11y that were blockers for many customers. The rendering of the clusters had also fallen into the trap of a leaky abstraction. Should we provide renderers that use WebGLOverlayView for instance, or OverlayView where the renderer returns a HTMLElement?
Another question is the input data. It's difficult to support all of the edge cases around visibility, setMap, etc as captured in #267. Should we allow something like geojson?
As to speed, markers are definitely the bottleneck on both ends however there is ongoing work that may improve this on the rendering side.
Already available at unpkg.
<script src="https://unpkg.com/@googlemaps/markerclusterer/dist/index.min.js"></script>
Anyone can submit a pr to have support in CDNJS. https://github.com/cdnjs/packages
An update, checking if I can upgrade to the current (2.5.3) version from legacy clusterer https://github.com/mahnunchik/markerclustererplus
The points I made above are still valid
minPoints
and radius
that quite worked(Note : I was using Advanced Markers when testing, the legacy clusterer doesn't support them)
[Sorry for multiple points in the same issue] Migrating from (depreciated) https://github.com/mahnunchik/markerclustererplus to v2.0.4 1) More documentation in README please, with examples of calling each cluster algorithm & each render algorithm,