[MapServer-msautotest]WMS GetFeatureInfo on a raster (in tomk_workshop.map) returned different results depending on the format (GML or HTML)

[nsavard@…]

WMS GetFeatureInfo on a raster (tomk_workshop.map) returned R=61, G=85 and B=23
as result of the request when the format is HTML.  When the format is GML no
result is found.  There is only a bounding box of -1, -1, -1, -1.

I opened the raster and vector layers in OpenEV.  If I checked at x=141 and y=91
location the pixel value is R=55, G=64 and B=14.  Also the lat/long coordinates
are more like -81E 26N than the ones returned in the response (-78.323040,
35.282000).

What should we expect as the result when we query at x=141 and y=91 location
with a radius of 10 on a raster layer?


Tests:
# Generate WMS GetFeatureInfo HTML format on raster data
# RUN_PARMS: wms_get_feature_info_raster.html [MAPSERV]
QUERY_STRING="map=[MAPFILE]&version=1.1.1&service=WMS&request=GetFeatureInfo&srs=EPSG:4326&bbox=-180,-90,180,90&format=image/png&layers=land_shallow_topo_2048,rivers&styles=,&transparent=true&width=500&height=300&query_layers=land_shallow_topo_2048&info_format=text/html&x=141&y=91&radius=10"
> [RESULT]
#
# Generate WMS GetFeatureInfo GML format on raster data
# RUN_PARMS: wms_get_feature_info_raster.gml [MAPSERV]
QUERY_STRING="map=[MAPFILE]&version=1.1.1&service=WMS&request=GetFeatureInfo&srs=EPSG:4326&bbox=-180,-90,180,90&format=image/png&layers=land_shallow_topo_2048,rivers&styles=,&transparent=true&width=500&height=300&query_layers=land_shallow_topo_2048&info_format=application/vnd.ogc.gml&x=141&y=91&radius=10"
> [RESULT]
#

[nsavard@…]

Do you have some development on this one Tom?

[tomkralidis]

The GML output problem is due to an ommision of metadata in the mapfile.

In the LAYER/METADATA object, for GML output, one must declare:

"gml_include_items" "all"

...to expose the RGB values.

For the radius issue, I would expect that MapServer would return pixel values
for a radius (units pixels).  When I change the radius in the GetFeatureInfo
URL, the response is still the same.  In mapwms.c around line 2371, this is
basically transferred to tolerance units.  So I'm not sure why this isn't
working.  Any comments from the MapServer developers?

[warmerdam]

I have reviewed now and these two tests now produce one feature in the response so it appears this issue has been resolved since it was first filed.