Allow LABEL POSITION, MINSIZE and MAXSIZE to be Set Dynamically

[DonaldKerr]

Allow LABEL POSITION, MINSIZE and MAXSIZE to be set dynamically e.g. by determining the position from a database record.

I have the following CLASS definition in a map file. In order to set LABEL POSITIONs dynamically, I have to have 9 similar classes to cover the 9 labelling positions ll,cl,ul, etc., as I cannot set the value directly from the database.

---

LABELITEM textstring

CLASS

EXPRESSION (([featurecode] = 10020) And ("[anchorpositiontxt]"="ll")) LABEL

TYPE truetype FONT [font] SIZE [height] MAXSIZE 21 MINSIZE 4 POSITION ll #COLOR 0 0 0 COLOR [oscolor] ANTIALIAS TRUE ANGLE [orientation] FORCE TRUE

END # LABEL

END # CLASS

---

With 30 different classes, each being repeated 9 times, it would be much easier if I could set the POSITION dynamically as with the following desired CLASS definition:

---

LABELITEM textstring

CLASS

EXPRESSION ([featurecode] = 10020) LABEL

TYPE truetype FONT [font] SIZE [height] MAXSIZE 21 MINSIZE 4 POSITION [anchorpositiontxt] #COLOR 0 0 0 COLOR [oscolor] ANTIALIAS TRUE ANGLE [orientation] FORCE TRUE

END # LABEL

END # CLASS

---

Same goes for MINHEIGHT and MAXHEIGHT. If these could be set along the lines of [height]*3 or [height]/3 or even just another database field, it would allow for more dynamic map configuration and less map file hard-coding.

[erigus]

Position attribute binding

[erigus]

Attribute binding for label position would be very useful for me too. Attaching a patch I've used previously.

[sdlime]

Added label position binding to trunk in r11063. The minsize/maxsize stuff doesn't seem as valuable. Maybe in a 6.x release when there's a bit more time.

Steve

[DonaldKerr]

Excellent work, thank you. Granted, minsize/maxsize binding may not be as useful but it would certainly benefit my purposes. If it's relatively easy to do the I'd certainly like to see it sooner rather than later. Thanks for your work again which is greatly appreciated.

Donald