Markers cluster #2436
Open
Markers cluster #2436
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There's a request for showing the Oskari infobox (https://oskari.org/api/requests#/2.12.0/ui/infobox/request/infobox.showinfoboxrequest.md) and pointing it to a specific marker. We should test if it works with clustering, but other than that this looks good to me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable clustering for markers. Changed mapmodule generator cluster style to return style instead of function to use same cache and style than others (WFS). WFS uses wrapClusterStyleFunction.
Not sure if cluestered markers are wanted everywhere so made it configurable. Maybe we should add prop + plugin modifier for backend.
One problem might be that nearest address markers can be very close.