WMSGetFeatureInfo control & Exceptions. If I use a Control.Click to build some GetFeatureInfo requests I can define an Exceptions parameter as part of the request. I've noticed that if I'm using the WMSGetFeatureInfo control then there is Exceptions parameter to define. I'm wondering if this is something that's missing from the control or it's handled deep within the library. Or as a developer is it something to be worried about.
infoFormats. To place this in context: I'm working on an OL application with a collection of WMS layers of interest on top of some national base mapping. We're dealing with probably about 40-50 WMS publishers who use a good healthy mix of supported infoFormats :-/ We wish to implement an Info tool for all visible layers. The WMSGetFeatureInfo control is rather attractive for us as it allows a drillDown but I'm wondering if a more resilient approach would be to capture the infoFormats when we do our initial getCapabilities (as part of the GeoExt tree panel) and then build separate GetFeatureInfo requests for each layer. That way we would at least be able to identify which features come from which WMS layer. I've noticed that with the drillDown/WMSGetFeatureInfo approach not all features are returning with a type value. If two separate WMS layers are defined from the same WMS then i can't distinguish between the two. Your thoughts/code would be appreciated on either matter! Andy _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
