Hi, the current GetFeatureInfo implementation already mimicks WFS GetFeature in a number of ways, including the ability to set a filter and output in GML2/GML3.
One bit that is missing is support for the PROPERTYNAME parameter, that is, the ability to select what attributes should be returned to the client as a request property. The interest is mostly related to network performance, especially when using an output like GML, where the geometry is included in the result too (and it can be large), but it's also easy to think about situations where the client just wants a single attribute out of of a potentially long list. So I would like to add support for &PROPERTYNAME=att1,att2,... , just like it is working today in WFS GetFeature, to GetFeatureInfo, both in trunk and in the stable series. Opinions? Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 339 8844549 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
