Opened 19 years ago
Last modified 13 years ago
#1340 assigned enhancement
minfeaturesize support at layer or class level
Reported by: | Owned by: | sdlime | |
---|---|---|---|
Priority: | high | Milestone: | 6.0 release |
Component: | MapServer CGI | Version: | 4.5 |
Severity: | minor | Keywords: | |
Cc: | woodbri@…, mapserver@…, dmorissette, aboudreault |
Description (last modified by )
I would like to be able to set a MINFEATURESIZE at the LAYER or CLASS level and have it act to filter out small features. It would be acceptable to implement the test on the features extents for performance and simplity of implemetation. This is needed for example with a water polygon layer so as you zoom out and the polygons reduce to 1 or 2 or N pixels, you can filter them from drawing. Otherwise you see a cloud of pixels the make it look like there is a lot of water when there is not. This will allow us to make more professional looking maps.
Change History (7)
comment:1 by , 19 years ago
Cc: | added |
---|
comment:3 by , 19 years ago
Milestone: | → 4.6 release |
---|
comment:4 by , 19 years ago
Milestone: | 4.6 release → FUTURE |
---|
Sorry, forgot about the feature freeze for 4.6. Marking as FUTURE. I would try then to add immediately to the 4.7 development version in a month or so and then backport to 4.6 once tested, and assuming the implementation is trivial (which it should be). Steve
comment:5 by , 15 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Milestone: | FUTURE → 6.0 release |
Let's try to get this in 6.0
comment:6 by , 13 years ago
I have added the support of minfeaturesize in the LAYER and CLASS scope in r10982. I think there is only the following case that might not work: when the layer has a different unit than the map. I will produce a test case tomorrow to test it.
comment:7 by , 13 years ago
I improved the last commit to reflect the proper behavior in r10998. Stephen, it would be nice if you could take a few minutes to test it.
Note:
See TracTickets
for help on using tickets.