<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><base target="_blank"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Consolas;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>Phil,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks again for your reply. I checked the NET tab of the debugger and I still was not sure about the source of the problem. But, you got me to thinking and I setup a test between GeoServer 2.4.3 and 2.5.1. Sure enough, the problem did not exist in GeoServer 2.4.3. I did some searching on the changes in 2.5.1, and I found the bug report below:<o:p></o:p></p><p class=MsoPlainText><a href="http://jira.codehaus.org/i#browse/GEOS-6420">http://jira.codehaus.org/i#browse/GEOS-6420</a><o:p></o:p></p><p class=MsoPlainText>The problem that I was having is not the same as in the bug report, but the recommendation of adding -Dorg.geoserver.wms.featureinfo.render.enabled=false to the JVM startup parameters to revert back to the old GetFeatureInfo engine resolved my problem for now. I need to do some additional research to determine why the new GetFeatureInfo engine was causing me problems, but at least I have the control working correctly now.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I always appreciate your input, and you seem to always get me back on the right track.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Jerome Wendell<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: openlayers-users-bounces@lists.osgeo.org [mailto:openlayers-users-bounces@lists.osgeo.org] On Behalf Of Phil Scadden<br>Sent: Thursday, July 03, 2014 7:00 PM<br>To: openlayers-users@lists.osgeo.org<br>Subject: Re: [OpenLayers-Users] Issue with WMSGetFeatureInfo Control<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>No answers but a strategy to tie down the issue: I would look at the request that OL emitted when you clicked in the NET tab of the debugger that resulted in the wrong hit. If the request is what you expect (what it sends to geoserver should only return one polygon), then I suggest take it up with geoserver list, giving them the request data. If OL has unnecessarily expanded the request parameters, then its a problem with OL. Post the request data here and lets look at it.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Notice: This email and any attachments are confidential.<o:p></o:p></p><p class=MsoPlainText>If received in error please destroy and immediately notify us.<o:p></o:p></p><p class=MsoPlainText>Do not copy or disclose the contents.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>Users mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:Users@lists.osgeo.org"><span style='color:windowtext;text-decoration:none'>Users@lists.osgeo.org</span></a><o:p></o:p></p><p class=MsoPlainText><a href="http://lists.osgeo.org/mailman/listinfo/openlayers-users"><span style='color:windowtext;text-decoration:none'>http://lists.osgeo.org/mailman/listinfo/openlayers-users</span></a><o:p></o:p></p></div></body></html>