<div dir="ltr"><div><div><div><font face="Arial">Hi guys,<br><br></font></div><font face="Arial">Current implementation of QGIS mapserver generates only one <gml:featureMember> element for all features of particular layer. For example, response from GeoServer ( <a href="http://demo.opengeo.org/geoserver/wms?LAYERS=topp%3Atasmania_water_bodies&QUERY_LAYERS=topp%3Atasmania_water_bodies&STYLES=&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&BBOX=141.5115%2C-43.933%2C150.8015%2C-39.288&FEATURE_COUNT=10&HEIGHT=256&WIDTH=512&FORMAT=application/xml&INFO_FORMAT=application/vnd.ogc.gml&SRS=EPSG%3A4326&X=292&Y=145">http://demo.opengeo.org/geoserver/wms?LAYERS=topp%3Atasmania_water_bodies&QUERY_LAYERS=topp%3Atasmania_water_bodies&STYLES=&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&BBOX=141.5115%2C-43.933%2C150.8015%2C-39.288&FEATURE_COUNT=10&HEIGHT=256&WIDTH=512&FORMAT=application/xml&INFO_FORMAT=application/vnd.ogc.gml&SRS=EPSG%3A4326&X=292&Y=145</a> ) produces </font><br>
<font face="Arial"> <gml:featureMember> element for every feature. Also parsing response from QGIS mapserver with OpenLayers (OpenLayers.Format.GML.read method) results in max. 1 feature per layer, even if XML document clearly contains more features.<br>
</font></div><font face="Arial"><br>For me, it seems like bug, but I'm no expert on WMS standard, so maybe there was some good reason to do it this way.<br><br></font><br><font face="Arial">Thanks<br>
      <br>
      </font></div><font face="Arial">Marcel Dancak<br></font></div>