David Winslow ha scritto: > Hi all, > > I've been doing some work on automated regionating for KML output in a > community module. I'd like to move that code into the main KML map > producer. I've written up a GSIP at > http://geoserver.org/display/GEOS/GSIP+20+-+Automated+Regionating+in+KML+MapProducer > > Of course, comments/questions/general feedback are welcome. It would be > nice to be able to vote on this at next week's IRC meeting.
KML support is getting so big that it is really starting to ask for its own module (hello Justin ;) ) As for merging stuff directly inside the KMLVectorTransformer, I'm having some reservations. I understand it's the easiest way to get that done, but at the same time this would add to a class that's already 1200loc. I'm wondering if it would be possible to split up some more code in pluggable separate classes, so that you would use one for standard KML, another for regionated KML, and so on. To give you another idea, some time ago Jason Pickering asked the KML to be split along the values of one or more attributes, building a classification tree that could be seen from GE as a tree control, stuff like roads with childs as "major roads", "local roads", and so on. I believe having some pluggability in how the generated KML is organised (besides the regionating strategy, but more on the lines of flat, regionalted, classified) would be good from a maitentance and understandability point of view. I'm not asking this to be done this way, just that you consider this as an alternative and see if it could lead to a cleaner (and more extensible) implementation without expanding too much the scope of your work. Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
