Change Details

Now that we have a `ext.kartographer.lib.prunecluster` containing the marker cluster plugin, * ** Should we use the marker cluster plugin with `<mapframe>` and `<maplink>` ?** ** should it be configurable or enabled by default? ** should we allow inline plugin configuration? (see below: weight, category, size) * ** How can we configure the plugin to handle all our use cases greacefully?** --- **Examples:** | **without** marker cluster | **with** marker cluster | | --- | --- | | {F4223506} (zoom=4) | {F4223512} (zoom=4) | | {F4223507} (zoom=5) | {F4223510} (zoom=5) | | {F4223515} (zoom=6) | {F4223517} (zoom=6) | --- As https://github.com/SINTEF-9012/PruneCluster#features lists: > The clusters **can be updated in __realtime__**. It's perfect for live situations. > > You **can specify the __weight__ of each marker**. > For example, you may want to add more importance to a marker representing an incident, than a marker representing a tweet. > > You **can specify a __category__ for the markers**. Then a small object representing the number of markers for each category is attached to the clusters. This way, you can create cluster icons adapted to their content. > For example, you may want to add more importance to a marker representing an incident, than a marker representing a tweet. > > The **__size__ of a cluster can be adjusted on the fly** > > The **markers can be __filtered__ easily with no performance cost**.

The nearby feature includes a cluster library that allows the creation of clusters from markers. This library could also be used to cluster user input added from `<mapframe>` and `<maplink>`. The library supports clustering in different cluster groups so it would be possible to have differently styled cluster layouts to transparently distinct between markers from different source that should not be grouped together. Still it's not clear how this functionality should be offered to the authors / readers. So some questions remain: * Should it be configurable in the wikitext or enabled by default? * Should we allow inline plugin configuration? (group, size, color?) * Should it always cluster by group, or just distinguish by source? --- **Examples:** ( taken from the `prunecluster` the currently favored `markercluster` works similar though ) | **without** marker cluster | **with** marker cluster | | --- | --- | | {F4223506} (zoom=4) | {F4223512} (zoom=4) | | {F4223507} (zoom=5) | {F4223510} (zoom=5) | | {F4223515} (zoom=6) | {F4223517} (zoom=6) | --- See https://github.com/Leaflet/Leaflet.markercluster for the plugin currently in use.

Now that we have a `ext.kartographer.lib.prunecluster` containing the marker cluster plugin,The nearby feature includes a cluster library that allows the creation of clusters from markers. This library could also be used to cluster user input added from `<mapframe>` and `<maplink>`. The library supports clustering in different cluster groups so it would be possible to have differently styled cluster layouts to transparently distinct between markers from different source that should not be grouped together. * ** Should we use the marker cluster plugin with `<mapframe>` and `<maplink>` ?**Still it's not clear how this functionality should be offered to the authors / readers. So some questions remain: ** s* Should it be configurablee in the wikitext or enabled by default? ** s* Should we allow inline plugin configuration? (see below: weightgroup, categorysize, sizecolor?) * ** How can we configure the plugin to handle all our use cases greacefully?*** Should it always cluster by group, or just distinguish by source? --- **Examples:** ( taken from the `prunecluster` the currently favored `markercluster` works similar though ) | **without** marker cluster | **with** marker cluster | | --- | --- | | {F4223506} (zoom=4) | {F4223512} (zoom=4) | | {F4223507} (zoom=5) | {F4223510} (zoom=5) | | {F4223515} (zoom=6) | {F4223517} (zoom=6) | --- As https://github.com/SINTEF-9012/PruneCluster#features lists: > The clusters **can be updated in __realtime__**. It's perfect for live situations. > > You **can specify the __weight__ of each marker**. > For example, you may want to add more importance to a marker representing an incident, than a marker representing a tweet. > > You **can specify a __category__ for the markers**. Then a small object representing the number of markers for each category is attached to the clusters. This way, you can create cluster icons adapted to their content. > For example, you may want to add more importance to a marker representing an incident, than a marker representing a tweet. > > The **__size__ of a cluster can be adjusted on the fly** > > The **markers can be __filtered__ easily with no performance cost**See https://github.com/Leaflet/Leaflet.markercluster for the plugin currently in use.