On Wed, Mar 20, 2013 at 7:59 PM, Martin Davis <mtncl...@gmail.com> wrote: > You're correct, inability to provide access to the underlying points is a > limitation of the current PointStacker implementation. I'm not sure whether > it's possible to solve this within GeoServer using GetFeatureInfo. So > database-side clustering might be a better option.
Just for the sake of the conversation, a couple of observations: - GetFeatureInfo is not aware of rendering transformations at the moment, as such it is returning the original data instead - even assuming GFI applies the rendering transformation and returns the result of the transformation, the results would still be a summary, not a list of the points that were used to form the output point no? Some change would be needed, say for example adding a string field that contains a comma separate list of the feature ids of the features that formed the point (and then the client would have to parse it and make a separate WFS GetFeature request to retrieve the original features with all the attributes) Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
