Please dont commit a bunch of styling changes right now. As I've said in several email messages, I'm currently going through parts of it and fixing it up. Most of it is in the rendering classes, but the styling objects are missing parts of the spec (as I mentioned earlier about LinePlacement being converted to PointPlacement in the StyleFactory because there's no LinePlacement in the style object).
There's no point in having a bunch of merge conflicts. I should be finished by early next week, or I can commit what I have now. Here's my notes. There's two changes that might be contraversial: a) grouping is turned off by default now (I've already warned people about this) b) default behavior for a missing <LabelPlacement> item is PointPlacment. dave -------------------------------- I've put up a page explaining how to use the Geotools labeling system: http://docs.codehaus.org/display/GEOSDOC/LabelingOptions -------------------------------------------------------- I've made the changes so that the SLD style factory is no longer making label placement decisions. This was already voted on. Martin - if you're going to be doing j2d/GO-1 renderer stuff, you should be aware of this change. -------------------------------------------------------- I've made the default behavior for not including a <LabelPlacement> tag ("PointPlacement" or "LinePlacement") to be PointPlacement. The old implementation was inconsistent about this. If you want LinePlacement, just put: <LabelPlacement> <LinePlacement> </LinePlacement> </LabelPlacement> In your SLD. -------------------------------------------------------- I've modified the code so you get more consistent behavior for PointPlacement and LinePlacement options. The only thing I havent done is handle LinePlacement for a polygon - it should probably pull the outer ring and then label the line. If anyone actually cares about this you should submit a jira. -------------------------------------------------------- Grouping of labels is only really useful for roads - and causes no end of problems for most other types of data. This should have never been the default behavior (although it was the *only* behavior for a long time). I've changed the default behavior to be "do NOT group". In LabelCacheDefault.java: public boolean DEFAULT_GROUP=false; //what to do if there's no grouping option You can change the behavior in your SLD document: <VendorOption name="group">yes</VendorOption> I've already warned people about this. -------------------------------------------------------- I also modified the "spaceAround" option so that you can allow overlapping label with a negative value. <VendorOption name="spaceAround"> ... </VendorOption> ---------------------------------------------------------- This mail sent through IMP: https://webmail.limegroup.com/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
