<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16414" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=493395918-01032007><FONT face=Arial
color=#0000ff size=2>Personally, I'd call that loose definition ambiguous,
especially in a standard that is supposed to be all about interoperability.
:) It's very implementation-specific, and way looser than an already
somewhat "subject-to-misinterpretation" spec. It basically doesn't
allow you to design a generic client app that uses it. Of course, I
haven't looked at recent WMS specs; maybe they've gotten
tighter.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=493395918-01032007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=493395918-01032007><FONT face=Arial
color=#0000ff size=2>Speaking of specifications; I wasn't specific enough.
In saying that I didn't think MapGuide supported GetFeatureInfo, I meant on the
consumer side. I don't think you can bring in a WMS service as a
layer, and then query GetFeatureInfo through the MapGuide web app without custom
programming?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=493395918-01032007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=493395918-01032007><FONT face=Arial
color=#0000ff size=2>Jason</FONT> </SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Thomas M. Tuerke<BR><B>Subject:</B> RE:
[mapguide-users] How to deal with data served by ArcIMS with
WMS<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">GetFeatureInfo is not
so much ambiguous as it is loosely defined. It’s purpose is to provide
<I><SPAN style="FONT-STYLE: italic">supplemental</SPAN></I> information on
features at a certain location in the raster. In short, it’s “hey server,
what feature is that at <I><SPAN style="FONT-STYLE: italic">pixel</SPAN></I> x,y
of the map just asked for with these parameters?” (As such, it’s not a
substitute for a WFS, which gives you raw, unrendered features as opposed to a
pretty picture.) It’s often used for roll-over effects such as “tool tips”
or some other status display.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=#0000ff size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT> </P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p><SPAN
class=493395918-01032007>[snip]</SPAN></o:p></SPAN></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">And yes, MapGuide does
support GetFeatureInfo, though it can be configured away wholesale in the
templates, or on a layer-by-layer basis (that’s the purpose of the “queryable”
attribute.) The templates also allow you to define your own text-based
response “format”, if you’re so inclined. If memory serves, text/plain and
text/html come for free out of the box.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-
Thomas<o:p></o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT face=Arial
color=#0000ff size=2><SPAN
style="FONT-SIZE: 12pt"><o:p></o:p></SPAN></FONT> </DIV></DIV></DIV></BODY></HTML>