[mapserver-dev] rfc49: call for vote

[Steve Lime]

I'm +1 on this. Comments:

- LABELMETHOD: I don't think this is required. In testing I've done and reports
from DM Solutions the new label placement algorithm is plenty fast, fast enough
not to warrant supporting multiple methods.

- PSUEDOITEMs: I prefer this to expression support for things like SIZE. It's just
cleaner. I'll tackle this in a separate RFC. Whether it makes 5.4 is up in the air.

- fractional parameters. I think those can be done now. The changes are pretty
simple and backwards compatible. Moving the params from symbolObj's to
styleObj's can wait until 6.0 I guess.

Steve

>>> "thomas bonfort" <thomas.bonfort at gmail.com> 01/17/09 2:16 AM >>>
Hi devs,

I'd like to get this in for 5.4:
http://mapserver.org/development/rfc/ms-rfc-49.html

wrapping up the comments from the review period, I think there isn't
any issue preventing a vote:

* possible values for LABELMETHOD (the default is to use cog) :
awaiting implementation, very probably postponed to after 5.4 (unless
Steve planned to implement this soon ?)

* labelObj for layer: implementation postponed to after 5.4

* fractional values also for pattern,gap, offset:  a good candidate
for 6.0 (when pattern and gap would be moved to the styleObj?)

* there was concensus for adding parametered scaling, usefull for
thematic mapping (eg size proportional to a feature attribute)
   - by allowing simple expressions, eg SIZE  ( 18 + [poptotal] * ((
43-18)/(5000-30000))  )
   - or by adding pseudoitems at the layer level:

PSEUDOITEM
 'mySize' (mrange([itemname], mininput, maxinput, minoutput,
maxoutput))
 'myText (commify(round([itemname], 2)) + ' ac')
END

LABELITEM 'myText'
CLASS
 STYLE
   COLOR 255 0 0
   SIZE [mySize]
 END
 LABEL
   ...
 END
END

this enhancement will be addressed in a specific rfc.


best regards,

Thomas
_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev