Hi All, With the introduction of the fontShrinkSizeMin vendor option the process of determining the labelling of the feature in case both fontShrinkSizeMin and maxDisplacement options are defined has as follows: First the fontShrinkSizeMin algorith is applied trying to shrink and place the label and if this does not succeed then maxDisplacement iterations take place using the initially defined font size of the label. I would like opinions whether do you consider this to be a good attitude. On the one hand it seems rational that when shrinking is enabled on a label we first check that trying to place the label and if no success then go for the solution of maxDisplacement. (still we must make it explicit in the user docs since there is no reference now)
Alternatives would be to: 1. 'interleave" the two processes (that is for each shrink size to apply all possible displacements) 2. 'interleave" the two processes in the reverse order of what is mentioned above ( that is for each displacement step check all shrink sizes) 3 apply first maxDisplacement and after fontShrinkSizeMin (I am not so positive to that I must admit) IMHO there is no perfect choice since depending on the situation somebody may have different requirements during rendering (i.e. (a) I may want to place labels as near as possible to their anchor points witihin polygons but not with reduced size, or (b) I have a long polygon I want just to place its label somewhere labels so check with displacement first but if font size is too big then resort to shrinking after)
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
