<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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=MsoNormal><span style='color:#1F497D'>Two quick observation. It looks like GeoMOOSE (identify.php) is sending the correct X and Y parameters coordinates 50 and 50. It could be possible that there is not feature at exactly that pixel coordinate. I’m not sure how WMS specs handle tolerance on those coordinates. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The other thing I noticed is it is not sending it a valid INFO_FORMAT parameter value. It is sending it a request of GML. That would be more of a WFS format. A better format for GetFeatureInfo would be text/xml. Take a look at this web page for valid request parameters. <a href="http://webhelp.esri.com/arcims/9.2/general/mergedProjects/wms_connect/wms_connector/get_featureinfo.htm">http://webhelp.esri.com/arcims/9.2/general/mergedProjects/wms_connect/wms_connector/get_featureinfo.htm</a> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bottom line is if this is what GeoMOOSE identify.php is sending as the WMS GetFeatureInfo request it appears to be wrong and in my opinion is likely a bug that would need to be fixed in identify.php code.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Hope this helps.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-family:"Arial","sans-serif";color:#1F497D'>Brian Fischer,</span></b><span style='color:#1F497D'> </span><span style='color:#595959'>CFM GIS Project Manager<br><b>Houston Engineering, Inc.</b><br>Phone: Direct: 763-493-6664 / W: 763.493.4522 / M: 763.229.2734<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Miller, Elizabeth (DOT) [mailto:Elizabeth.Miller@state.mn.us] <br><b>Sent:</b> Thursday, June 17, 2010 9:56 AM<br><b>To:</b> Brian Fischer; geomoose-users@lists.sourceforge.net<br><b>Subject:</b> RE: Identify Attributes on a WMS<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>So, I’ve been working on this for a couple months now – still no luck! I’ve stopped using a mapfile and I now have my wms only as a source in my mapbook file. I am hitting the wms on the map with the identify tool and I am trying to get the identify.php to send the proper GetFeatureInfo request so that it can populate the wms_record.html. As an example, I am using the wms services at <a href="http://www.datafinder.org">www.datafinder.org</a>. The url that the identify.php is building for my request is this:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="http://www.datafinder.org/wmsconnector/com.esri.wms.Esrimap/MN_MetroGIS_DataFinder_WMS_Recreation_Tourism?&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&WIDTH=100&HEIGHT=100&X=50&Y=50&EXCEPTIONS=application/vnd.ogc.se_xml&LAYERS=bikeways&QUERY_LAYERS=bikeways&BBOX=508702.025,4993206.245,508902.025,4993406.245&SRS=EPSG:26915&STYLES=&INFO_FORMAT=application/vnd.ogc.gml">http://www.datafinder.org/wmsconnector/com.esri.wms.Esrimap/MN_MetroGIS_DataFinder_WMS_Recreation_Tourism?&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&WIDTH=100&HEIGHT=100&X=50&Y=50&EXCEPTIONS=application/vnd.ogc.se_xml&LAYERS=bikeways&QUERY_LAYERS=bikeways&BBOX=508702.025,4993206.245,508902.025,4993406.245&SRS=EPSG:26915&STYLES=&INFO_FORMAT=application/vnd.ogc.gml</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>As you can see if you hit this url, I am not getting any attribute information back. Any ideas why? Is there something missing from my request?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(Yes, the wms layer is queryable.)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks for your help!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Liesa Miller<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>MnDOT Metro District<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Fischer [mailto:bfischer@houstoneng.com] <br><b>Sent:</b> Thursday, April 22, 2010 12:17 PM<br><b>To:</b> Miller, Elizabeth (DOT); geomoose-users@lists.sourceforge.net<br><b>Subject:</b> Re: [Geomoose-users] Identify Attributes on a WMS<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>In your mapfile that you are trying to identify on are you using?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> METADATA<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> 'wms_record' 'identify_parcel.html'<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> END<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I believe that is what tells the GeoMOOSE code to make a WMS identify request versus a MapServer identify request. Have you look to see what firebug is return for results? When I look through the identify.php code it appears to all be in there, but it is looking for the wms_record parmater in the mapfile.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Like I said I have not tried to use this feature myself but it is suppose to be supported. Hope this helps you debug it a little bit more.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-family:"Arial","sans-serif";color:#1F497D'>Brian Fischer,</span></b><span style='color:#1F497D'> </span><span style='color:#595959'>CFM GIS Project Manager<br><b>Houston Engineering, Inc.</b><br>Phone: Direct: 763-493-6664 / W: 763.493.4522 / M: 763.229.2734<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Miller, Elizabeth (DOT) [mailto:Elizabeth.Miller@state.mn.us] <br><b>Sent:</b> Thursday, April 22, 2010 11:52 AM<br><b>To:</b> Brian Fischer; geomoose-users@lists.sourceforge.net<br><b>Subject:</b> RE: Identify Attributes on a WMS<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Thanks Brian,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Yep, the WMS source should have attributes available for request. Here’s my current METADATA code. As you can see, I think I’ve thrown everything but the kitchen sink in there. If you have any ideas or see any glaring errors let me know. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>LAYER...<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> METADATA <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_identify" "identify_data.html"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_record" "identify_data.html"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_title" "layertitle" <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_srs" "EPSG:26915"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_name" "layername"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_server_version" "1.1.1"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_format" "image/gif"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_styles" ""<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_exceptions" "application/vnd.ogc.se_inimage"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_request" "GetMap"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_request" "GetFeatureInfo"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_include_items" "all"<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> "wms_feature_info_mime_type" "text/html" <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> END<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> DUMP TRUE<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> TEMPLATE '/ms4w/.../identify_data.html' <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> TOLERANCE 3<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>...END<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Brian Fischer [mailto:bfischer@houstoneng.com] <br><b>Sent:</b> Wednesday, April 21, 2010 3:43 PM<br><b>To:</b> Miller, Elizabeth (DOT); geomoose-users@lists.sourceforge.net<br><b>Subject:</b> RE: Identify Attributes on a WMS<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Liesa,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>First thing you will have to figure out is if the WMS source has setup any attributes to return with a getinfo wms request. It should be published in the GetCapbilities if it is. Not all WMS servers are setup by default to return all attributes.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I have never tried to use the identify with a WMS data source, but I believe Dan added support for it. I have seen there are configuration settings for the html templates in settings.ini file.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-family:"Arial","sans-serif";color:#1F497D'>Brian Fischer,</span></b><span style='color:#1F497D'> </span><span style='color:#595959'>CFM GIS Project Manager<br><b>Houston Engineering, Inc.</b><br>Phone: Direct: 763-493-6664 / W: 763.493.4522 / M: 763.229.2734<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Miller, Elizabeth (DOT) [mailto:Elizabeth.Miller@state.mn.us] <br><b>Sent:</b> Wednesday, April 21, 2010 3:07 PM<br><b>To:</b> geomoose-users@lists.sourceforge.net<br><b>Subject:</b> [Geomoose-users] Identify Attributes on a WMS<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m looking for help in setting up an identify on a wms layer. I am using a mapfile to bring in the layer rather than setting up the connection in the mapbook. Does anyone have an example of how to do this? I would like to be able to click with the identify tool on the layer and return attributes in an html template. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Liesa Miller<o:p></o:p></span></p><p class=MsoNormal>MnDOT Metro District<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>