You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sure this is a Leaflet.MarkerCluster code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
I've searched through the issues to make sure it's not yet reported
I'm plotting a map with lots of markers. For most of the time, the markers will be shown as clusters - so very few markers will actually be shown.
I think this offers a performance opportunity. If MarkerCluster took a function to generate the icon markers, then it would just call that function when a parent cluster got expanded. If clusters don't get expanded then the icon marker doesn't actually get created, which optimises performance and memory.
Note: the MarkerCluster would still need to know the coords of each icon, so I guess the developer would provide a coord/function pair for each icon.
The text was updated successfully, but these errors were encountered:
It's actually that code snippet that prompted the idea.
But, the function in the snippet provides the cluster icons (shaded circle with a number in the middle), not the icons themselves. So, we'll almost always have the cluster icons, it's the individual markers themselves that I'm hoping to defer.
I'm plotting a map with lots of markers. For most of the time, the markers will be shown as clusters - so very few markers will actually be shown.
I think this offers a performance opportunity. If MarkerCluster took a function to generate the icon markers, then it would just call that function when a parent cluster got expanded. If clusters don't get expanded then the icon marker doesn't actually get created, which optimises performance and memory.
Note: the MarkerCluster would still need to know the coords of each icon, so I guess the developer would provide a coord/function pair for each icon.
The text was updated successfully, but these errors were encountered: