Jody Garnett ha scritto: > Andrea Aime wrote: >> They are separated in the new version of SLD, but you are still >> expected to use SLD 1.1 with a WMS no? SE 1.1 by itself does not >> seem very useful to me. I mean, to do most maps you have to take >> multiple feature type styles and lump them together in the proper >> order. Heck, with feature type style alone we would not be able >> to make the sample NY streets map we provide as a sample. >> > There are two ways to consider it; SLD is the styling for an "entire" > map; all the layers etc... the SE part is what we associate > with each individual layer (ie what we should save to associate with > each named style we publish), the scope is limited to a specific > FeatureType. > > Bigger picture the scope of an SE document is for a FeatureType (and all > its children). The idea is to store SE documents for the different > FeatureTypes in your system and bring them all together into an SLD > document for a specific map. In the uDig catalog we basically use the > SE portion of SLD 1.0 and ignore all the rest as book keeping .... since > we focus on rendering one layer at a time.
And you forget to take care of needs such as road casing and, more in general, composite symbology that styles a single layer by doing so, right? With that approach you cannot have a "highway" style, but only a "thin line", "thick line" ones that you have to apply in the right order on two layers that happen to use the same data... Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
