Hi, lately I've been quietly working on improving a bit our KML generation story.
The first result of that work can already be found in 2.0.x in terms of defaults configurability: I've added a panel in the WMS service configuration that allows to set defaults for the reflector and the KML generation in terms of: - default reflector mode (refresh, superoverlay, ...) - default superoverlay sub-mode - whether to generate placemarks by default - whether to generate placemarks over raster outputs when the number of vector features exceeds the KMSCORE - setting the KMSCORE See attached screenshot. Now we (Chris and me) want to push a little further ahead in terms of GS/GWC integration. As you may know GWC can cache and generate regionated hierarchies for both vector and raster data. However GeoServer own KML output does not leverage that. What we would like to do is to create yet another sub-mode for the superoverlay generation called "cached" that defers to GWC as much as possible, provided that the current KML request params match what GWC cache, and would fall back on "auto" behavior if the params are not compatible. Raster wise this would be a solid improvement as raster superoverlays are working fine and GWC would give a serious speedup to that use case. Vector wise we still want to introduce the option, though it's not going to be a default since we all know vector super-overlays are not working that well these days. Given this evident difference between raster and vector I plan to provide separate defaults for vectors and raster in the WMS service GUI to allow admins to use superoverlays by default on raster data without have to bring in the vector as well. There is also the catch that GWC cannot do LRU cleaning of tiles at the moment, so for the moment we would not enable the cached mode by default for rasters either to avoid the uncontrolled generation of tiles on disk. But it would be there for all admins to use (and same goes for vectors, super-overlay normally works fine if all you have is small amounts of data) I haven't seen much interest on KML lately on this list so I was unsure whether to talk about this or just go and implement, but here it is, I think it's right to give everybody the possibility to weight in, even if I don't expect much of a reaction (feel free to prove me wrong!! ;-) ) Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers.
<<inline: wms-kml-options.png>>
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
