> Yes, a very substantial one: only understands geometries, > GetFeatureInfo knows about symbolizers (or at least tries to) so a > query on a point symbolizer that is 32px large is going to be much > more likely to work on GetFeatureInfo that GetFeature. To have them > work similarly you have to image a WMS request where all points are > symbolized with a single pixel and all lines are thin. Actually one of the things that I dont like about getFeatureInfo is that hitbox is too small - defined by the symbolizer! I'm more concerned though about server workload and network traffic. > If you are worried that GetFeatureInfo is returning too much > information you'll be happy to know that I'm about to implement > property selection for GetFeatureInfo, pretty much the same way as > GetFeature works That would indeed be good - as would GML option for returned.
-- Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St, Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232 Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
