<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML DIR=ltr><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"></HEAD><BODY>
<DIV id=idOWAReplyText57254 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><!--StartFragment --><FONT
size=3><FONT face="Times New Roman">Hi all,</FONT></FONT></FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr>I'm working on a few WMS services for my organisation (still very
much in the development stage), and I'm testing my mapfiles in IE 6, ArcMap
9.0, ArcExplorer 4, ArcExplorer 9, and Gaia 2.1.0.</DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><FONT size=3><FONT
face="Times New Roman"></FONT></FONT></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><FONT size=3><FONT
face="Times New Roman"><TR><TD class=postvalue>Thus far I've been unable to get
GetFeatureInfo requests (via the Identify tool) working in ArcMap - if I use
Identify on a particular layer, I always get "Nothing found", and if I use it
for a group of layers, I get a blank response. Querying the same area in Gaia
2.0.1 works fine, either on that layer or the group as a whole. <BR><BR>I've
used my webserver logs to compare the URLs used by both Gaia and ArcMap for
GetFeatureInfo Requests. Below is the entry in the webserver log for ArcMap's
GetFeatureInfo request (edited for readability & path removed).
</FONT></FONT></FONT></DIV></DIV>
<P><FONT face=Arial color=#000000><FONT><FONT face="Times New Roman"
size=2>2005-06-01 00:33:24 10.0.0.11 GET /scripts/mapserv.exe
<BR><BR>map=<path>\wms_1-250k.map<BR>&VERSION=1.1.1<BR>&REQUEST=GetFeatureInfo<BR>&SRS=EPSG:4326<BR>&BBOX=104.859217282479,-53.2952,162.115782717521,-2.5148<BR>&WIDTH=946<BR>&HEIGHT=839<BR>&QUERY_LAYERS=hotspots_200505161346_P_A_MOD14.shp<BR>&STYLES=<BR>&EXCEPTIONS=application/vnd.ogc.se_xml<BR>&&INFO_FORMAT=text/html<BR>&FEATURE_COUNT=50<BR>&X=343</FONT></FONT></FONT><FONT
face=Arial color=#000000><FONT><FONT face="Times New Roman" size=2>&Y=283
<BR></FONT></FONT></FONT><FONT face=Arial color=#000000 size=2><FONT
size=3><FONT face="Times New Roman"><BR>If I reverse engineer this into the
appropriate URL and test it in IE, I get an XML document back containing the
error "msWMSLoadGetMapParams(): WMS server error. Invalid layer(s) given in the
LAYERS parameter." <BR><BR>Now the interesting part: if I then add on to the URL
"&LAYERS=hotspots_200505161346_P_A_MOD14.shp" </FONT></FONT></FONT><FONT
face=Arial color=#000000 size=2><FONT size=3><FONT face="Times New Roman">(same
layer as the QUERY_LAYERS parameter), then I get a nifty response back -
features are found and displayed via my html template. Incidentally, Gaia's URL
does include this parameter. <BR><BR>Is this a bug in ArcMap's WMS compliance?
How can I get around it?? </FONT></FONT></FONT></P>
<P><FONT face=Arial color=#000000 size=2><FONT size=3><FONT
face="Times New Roman"><BR><BR>All advice much appreciated! :)
<BR><BR><BR>Cheers, <BR><BR><BR>Bonnie </TD> </TR><TR><TH> </TH>
</FONT></FONT></FONT></P>
<DIV id=idSignature94644 dir=ltr>
<DIV><FONT face=Arial color=#000000 size=2><FONT face=Helv size=2>
<DIV>________________________________</DIV>
<DIV>Bonnie Stewart</DIV>
<DIV>Research Officer</DIV>
<DIV>Satellite Remote Sensing Services</DIV>
<DIV>Department of Land Information</DIV>
<DIV> </DIV>
<DIV>Email: <A
href="mailto:Bonnie.Stewart@dli.wa.gov.au">Bonnie.Stewart@dli.wa.gov.au</A></DIV>
<DIV>Phone: 9387 0342</DIV></FONT></FONT></DIV></DIV><FONT SIZE=3><BR>
<BR>
This e-mail and any files transmitted with it are intended only for the use of the addressee(s). It may contain information that is confidential and privileged. If you are not an intended recipient, any use, interference with, disclosure, distribution or copying of this material is unauthorised and prohibited. If you receive this in error, please notify the author by Return email to the sender. Information in this message not relating to the official business of DLI shall be understood as neither given nor endorsed by it. While every care is taken, it is recommended that you scan any attachments for viruses. DLI liability is limited to re-supplying affected attachments.<BR>
</FONT>
</BODY></HTML>