Opened 13 years ago
Closed 13 years ago
#430 closed task (fixed)
New sample featuring MapServer Cluster
Reported by: | adube | Owned by: | adube |
---|---|---|---|
Priority: | major | Milestone: | 1.4.0 |
Component: | samples | Version: | trunk |
Keywords: | bis-1.4.0 cluster mapserver | Cc: |
Description
MapServer has the ability to combine multiple features from a point layer into single aggregated features based on their relative position. This is called "Cluster".
It would be nice to have a sample featuring this in GeoPrisma.
See the MapServer documentation : http://mapserver.org/mapfile/cluster.html
Change History (2)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Sample added in r1348, which uses MapServer 6.0.1 and Cluster used for drawing operations only (no query).
Task done.
Note:
See TracTickets
for help on using tickets.
Here's a summary of the current situation for the Cluster in MapServer :
Cluster in MapServer
With MapServer 6.0
Features
Styling
The size of clustered points can be proportional to the "Cluster:FeatureCount" setting it to the SIZE parameter and setting MINSIZE and MAXSIZE, however the WMS GetLegendGraphic only shows the MINSIZE version of the style rendered. Labeling becomes complicated too if you want them dynamic. If you want to use this, set a big minsize and a maxsize equal to your MAXDISTANCE defined in your cluster.
An other way to do so is to manually define styling ranges by manually setting one CLASS object per classification wanted. This is longer to set, but it ensures that the classification is correctly returned in the GetLegendGraphic, you can more easilly manage your LABEL, etc.
TOLERANCE
When querying, the TOLERANCE is used as usual. The size of the feature doesn't matter.
With MapServer 6.1-dev (tested with trunk at revision 13157)
Features
Bugs and issues
Tip and tricks
References