The WMSGetFeatureInfo
doesn't work by requesting info on the feature being currently clicked as such. It works by formulating a WMS GetFeatureInfo request which passes a BBOX string to the WMS server. So, when you click on the map the location coordinates are captured and then sent to a WMS server as the request. You could see this in action by using something like Fiddler2 to inspect the request being made.
It is possible to create this elegantly without resorting to Ajax as the control does not have to be associated to a specific layer at creation. You can set the layer on the beforegetfeatureinfo
event. Something like this would work:
var queryableMapLayers = [];
var getFeatureControl = new OpenLayers.Control.WMSGetFeatureInfo({
url: your_wms_url.here // Your WMS server url here,
drillDown: false, // Or true if you want drill down (see the docs)
hover: false, // Or true if you want but bear in mind this could get chatty
layers: queryableMapLayers,
eventListeners: {
getfeatureinfo: function (event) {
// Code here if you want to process the results
},
beforegetfeatureinfo: function(event) {
// Code here to set the content of queryableMapLayers
// The event object will contain xy of mouse click
},
nogetfeatureinfo: function(event) {
// Code here if no queryable layers are found
}
}
});
// Add the control to your map
map.addControl(getFeatureControl);
We use this approach in our applications along with a custom JSON response from GeoServer to emulate an ArcGIS style feature info dialog.