Problem with WMSGetFeatureInfo request when map cross the 180 dateline

Phil Scadden added a comment - 08/Mar/12 2:40 PM This behaviour also affects geoserver 2.1.0

Phil Scadden added a comment - 08/Mar/12 2:42 PM I raised this on the openlayers list least the problem was with OL and and format of the URL. ahocevar comments as follows: ________________________________________________________________________________________ The bbox that OpenLayers uses for the GetFeatureInfo request should be the same as for the GetMap request. In the example above, the llbbox is 150.30,-50.17,190.69,-30.78. Now two interesting questions: what is your layer's maxExtent in the GetCapabilities response? And does the url below return a feature info? http://maps.gns.cri.nz/geoserver/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&LAYERS=gns%3APETROLEUM.NZ_2D_SEIS_LINES&QUERY_LAYERS=gns%3APETROLEUM.NZ_2D_SEIS_LINES&STYLES=&BBOX=16731556.455300998%2C-6475305.631310003%2C1189768.3702969998%2C-3603719.353092&FEATURE_COUNT=1&HEIGHT=587&WIDTH=919&FORMAT=image%2Fpng&INFO_FORMAT=application%2Fvnd.ogc.gml&SRS=EPSG%3A900913&X=754&Y=363 Note that this is the same url as your original one, but with the right edge at 10.69 instead of 190.69. ------ Well, since this is a public server, I can answer the questions myself: 1) The maximum extent of the layer as advertised in GetCapabilities is -180.0,-86.63,180.0,90.0 2) The request that OpenLayers sends is correct. The modified url raises an exception ("org.geoserver.platform.ServiceException: illegal bbox, minX: 1.6731556455300998E7 is greater than maxX: 1189768.3702969998"). Especially 2) makes me think that this issue should be fixed on the GeoServer side. The only other option would be to split the map extent at the dateline and send two GetFeatureInfo requests.