Skip to content

feat(wms): set default maxscaledenominator - #141

Merged
kad-korpem merged 4 commits into
masterfrom
set-default-maxscaledenominator
Oct 29, 2026
Merged

kad-korpem merged 4 commits into
masterfrom
set-default-maxscaledenominator

Conversation

@kad-korpem

Copy link
Copy Markdown
Collaborator

Description

A degenerate request (very large bounding box combined with very small width/height) can cause high CPU usage in Mapserver. Setting a (high) default for the max scale denominator provides a workaround for this issue, since it forces Mapserver not to try rendering features beyond a certain zoom. For specific use cases, it is still possible to set a higher max scale denominator explicitly in a WMS CR.

Type of change

  • Improvement of existing feature
  • Configuration change
  • Breaking change

Checklist:

  • I've double-checked the code in this PR myself
  • I've left the code better than before (boy scout rule)
  • The code is readable, comments are added that explain hard or non-obvious parts.
  • I've expanded/improved the (unit) tests, when applicable
  • I've run (unit) tests that prove my solution works
  • There's no sensitive information like credentials in my PR

kad-marchal
kad-marchal previously approved these changes Oct 29, 2026

@kad-marchal kad-marchal left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests are still red, but changes lgtm

@kad-korpem
kad-korpem merged commit 28759b6 into master Oct 29, 2026
3 checks passed
@kad-korpem
kad-korpem deleted the set-default-maxscaledenominator branch October 29, 2026 15:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants