Leaflet.LayerGroup.Collision
Leaflet.LayerGroup.Collision copied to clipboard
MazeMap
Leaflet plugin for uncluttering L.Markers using basic collision detection.
I installed the latest version via npm and required via Browserify: `require('leaflet.layergroup.collision')` I got the following error: `Uncaught ReferenceError: rbush is not defined` I could workaround by changing the require...
I got this on my console when opening the demo page ``` Uncaught ReferenceError: L is not defined https://mazemap.github.io/Leaflet.LayerGroup.Collision/demo/demo.html:49 ```
Hi; I just installed Rbush latest version ( 2.0.1 ) as a dependency, and it's not working out of the box. Adding support for 2.x or bundling with the old...
It seems that the GeoJSON version of this addon can't find the extended properties on itself. Simply calling `L.geoJSON.collision(...)` throws ``` Uncaught (in promise) TypeError: Cannot read property 'push' of...
How do we safely remove the plugin in the map after we use it? I tried removing it through: map.removeLayer(collisionLayer);, the labels are remove, but the rendering is messedup such...
It would be desirable to make `L.Tooltip`s from Leaflet 1.0.x and LayerGroup.Collision compatible - read collision boxes from labels, not assuming they are marker icons.
On touch devices the collision detection doesn't work while zooming until you lift up your fingers. Therefore it would be nice to switch to onZoom as a trigger instead of...
Would be great to have smooth transitions (fade in / fade out). Maybe adding a CSS class to colliding/hidden elements or using a callback on collision could be alternative solutions...
Chrome complains about loading insecure elements. Seems there are "http" urls hard coded in the page. Can easily work around, but with Googles push to the encrypted internet might be...
This plugin has been a great solution to all of my point collision issues thus far (without using markerclusters or similar copycat plugins), however, recently I've been incorporating features into...
