WMS GetFeatureInfo request is malformed about udig-platform

[fgdrf]

WMS spec for version 1.3.0 states that CRS is an mandatory parameter for GetFeatureInfo Requests

[nmtoken]

Yes indeed, A GetFeatureInfo request is effectively the GetMap request (except the the request type is GetFeatureInfo) plus image (pixel) coordinates in the GetMap image for the point clicked on in the map, plus the layers to be queried, plus the information format. The issue is that the request is automatically generated by udig, so I can't add the CRS parameter manually

[nprigour]

Hi @nmtoken ,

Can you explain the way (precisely steps) you issue the above mentioned request from within the udig application. I couldn't find a way to generate it. When I add a layer I can see only possibilities to select between a general wms request (usually targeting raster layers) and a wfs request targeting feature layers.
In the wms request the CRS is sent (checked against geoserver). On the other hand wfs request have a completely different format from the one you specify above.

[nmtoken]

Hi @nprigour, yes agree that the WMS GetMap operation does send the CRS otherwise I wouldn't get a map to click on, and to reiterate I am talking about WMS and not WFS.

Sorry haven't got UDIG on this PC but as per my screenshot, if you see the info option in the palette window on the right hand side, I'm using that info tool to do the on map selection, and it is making the malformed GetFeatureInfo request.

[nprigour]

OK @nmtoken that makes things more clear,

I tried to perform the steps as mentioned above using a geoserver 2.13 wms service . Indeed it seems that the request sent does not include CRS info. However information about the feature clicked is correctly returned to the info view. Of course it is possible that geoserver is less restrictive regarding the actual information needed during a getFeatureInfo request. Is it possible to provide some more information regarding the type of wms server you communicate with and if there is a way to access it for testing?

[mprins]

ESPG:4326 has lat/long axis ordering, however some versions of mapserver have this inverted, see https://mapserver.org/ogc/wms_server.html#wms-1-3-0-support
Looking at the capabilities document can be helpful

[nmtoken]

@mprins MapServer is working correctly because the GetMap operation is generating the correct map, the issue is with the GetFeatureInfo operation. MapServer version used here is 7.2.0 so https://mapserver.org/ogc/wms_server.html#wms-1-3-0-support is not an issue

[nmtoken]

@nprigour I'm using MapServer. The issue is with UDIG not following the WMS standard, not with the server. GeoServer has an option Strict CITE compliance do you have that enabled in your test service? When I do a GetFeatureInfo request on GeoServer with Strict CITE compliance set I don't get a result if I omit the CRS.

[fgdrf]

fixed with milestone 2.1.0