WMS Coalesce feature option for layers and maps - #12741
Merged
Conversation
stefanocudini
marked this pull request as draft
July 27, 2026 14:38
14 tasks
14 tasks
stefanocudini
force-pushed
the
fix-12624-coalesce-adjacent-wms-layers-into-a-single-getmap-request
branch
3 times, most recently
from
July 28, 2026 12:54
57cf2a0 to
6aacd82
Compare
…urity config (geosolutions-it#12729) Spring 7 (geosolutions-it#12428) added depends-on="entityManager" to the GeoStore token filters and the entityManager bean, but the bean was added only to the db configs. The ldap configs referenced a bean that was never defined, so the ldap profile failed context init at startup. coalesce settings restore loconfig restore tests restore-config coalesce i18n en fr en de . fix tests TOC fix tests TOC fix utils test fix utils test .
stefanocudini
force-pushed
the
fix-12624-coalesce-adjacent-wms-layers-into-a-single-getmap-request
branch
from
July 28, 2026 12:55
6aacd82 to
4804c6d
Compare
…o-a-single-getmap-request
allyoucanmap
marked this pull request as ready for review
July 29, 2026 08:47
allyoucanmap
self-requested a review
July 29, 2026 08:47
This was referenced Aug 3, 2026
allyoucanmap
approved these changes
Aug 7, 2026
allyoucanmap
left a comment
allyoucanmap
left a comment
Contributor
There was a problem hiding this comment.
@stefanocudini I approved and reviewed the code adding some commits, please double check them. If everything is fine we can merge it
Contributor
|
we should squash with the |
Contributor
|
@ElenaGallo please test this enhancement on dev, thanks |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Issues contains the details, add new feature for Map and Layers, Coalesce adjacent WMS layers into a single GetMap request.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
#12662
What is the current behavior?
Each WMS layer is always loaded with a single getMap per layer
What is the new behavior?
Adjacent WMS layers pointing at the same endpoint are currently rendered as separate GetMap requests.
Other useful information
This map conatins more wms layers useful for testing:
https://dev-mapstore.geosolutionsgroup.com/mapstore/#/viewer/67842