<!--/*SC*/DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"/*EC*/-->
<html><head><title></title><style type="text/css"><!-- body{padding:1ex;margin:0;font-family:sans-serif;font-size:small}a[href]{color:-moz-hyperlinktext!important;text-decoration:-moz-anchor-decoration}blockquote{margin:0;border-left:2px solid #144fae;padding-left:1em}blockquote blockquote{border-color:#006312}blockquote blockquote blockquote{border-color:#540000} --></style></head><body><div style="font-family: Verdana; font-size: small;" dir="ltr"><div>
Thanks Bart,</div>
<div>
</div>
<div>
That's very useful information. So it sounds like we'll make a stab at modifying our use of the GeoExt.tree.WMSCapabilitiesLoader to capture the available exception and info_format values.</div>
<div>
</div>
<div>
Merry christmas,</div>
<div>
Andy</div>
<div class="defangedMessage">
<div id="me43249">
<div>
</div>
<div>
</div>
<div>
On Wed, Dec 21, 2011, at 05:37 PM, Bart van den Eijnden wrote:</div>
<blockquote class="me43249QuoteMessage" type="cite">
<div dir="ltr" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Andrew,
<div>
</div>
<div>
the control just uses the EXCEPTIONS parameter value as specified on the WMS Layer. So you can control it that way.</div>
<div>
</div>
<div>
infoFormat can also be specified on a WMS layer: parameter name is INFO_FORMAT</div>
<div>
</div>
<div>
wrt the type value, e.g. ArcGIS Server returns an XML structure that does not allow us to determine from which layer a feature came when requesting GetFeatureInfo for multiple layers from an ArcGIS service. Not much we can do about this. I've reported this to ESRI in the past.</div>
<div>
</div>
<div>
Best regards,</div>
<div>
Bart</div>
<div>
<br />
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>
<div>
<span class="me43249Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="me43249Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="me43249Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="me43249Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">-- <br />
Bart van den Eijnden<br />
OSGIS - <a href="http://osgis.nl">http://osgis.nl</a></span></span></span></span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br />
<div>
<div>
On Dec 21, 2011, at 5:25 PM, Andrew Bailey wrote:</div>
<br class="me43249Apple-interchange-newline" />
<blockquote type="cite">
<div>
WMSGetFeatureInfo control & Exceptions.<br />
<br />
If I use a Control.Click to build some GetFeatureInfo requests I can<br />
define an Exceptions parameter as part of the request. I've noticed that<br />
if I'm using the WMSGetFeatureInfo control then there is Exceptions<br />
parameter to define. I'm wondering if this is something that's missing<br />
from the control or it's handled deep within the library. Or as a<br />
developer is it something to be worried about.<br />
<br />
infoFormats.<br />
<br />
To place this in context: I'm working on an OL application with a<br />
collection of WMS layers of interest on top of some national base<br />
mapping. We're dealing with probably about 40-50 WMS publishers who use<br />
a good healthy mix of supported infoFormats :-/<br />
<br />
We wish to implement an Info tool for all visible layers. The<br />
WMSGetFeatureInfo control is rather attractive for us as it allows a<br />
drillDown but I'm wondering if a more resilient approach would be to<br />
capture the infoFormats when we do our initial getCapabilities (as part<br />
of the GeoExt tree panel) and then build separate GetFeatureInfo<br />
requests for each layer. That way we would at least be able to identify<br />
which features come from which WMS layer. I've noticed that with the<br />
drillDown/WMSGetFeatureInfo approach not all features are returning with<br />
a type value. If two separate WMS layers are defined from the same WMS<br />
then i can't distinguish between the two.<br />
<br />
Your thoughts/code would be appreciated on either matter!<br />
Andy<br />
_______________________________________________<br />
Users mailing list<br />
<a href="mailto:Users@lists.osgeo.org">Users@lists.osgeo.org</a><br />
http://lists.osgeo.org/mailman/listinfo/openlayers-users<br />
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>
</div>
</div></body></html>