Hi Steve,<br>thx for hint.<br><br>I read the doc and also the RFC 36.<br>I'm having also some doubt.<br><br>I try to set this output format:<br>
<br>
OUTPUTFORMAT<br>
NAME "delimitazione_fogli_xml"<br>
MIMETYPE "text/xml"<br>
DRIVER "TEMPLATE"<br>
FORMATOPTION "FILE=/pat-to-ex-template-on-layer-level/template_xml.tmpl"<br>
END<br>
<br> at WEB level I set this value:<br>
WEB<br>
METADATA<br>
"wms_feature_info_mime_type" "text/xml"<br>
END<br>
END<br>
<br>
And how explained from RFC I comment the template from layer level and try to add the tag<br>QUERYABLE TRUE<br>(But this option seem to be not supported from MapServer 6.2 trunk)<br><br>If I remove the template tag from layer level I have this error:<br>
<br>msWMSFeatureInfo(): WMS server error. Requested layer(s) are not queryable.<br><br>And if I try to add the QUERYABLE TRUE tag I have <br>this error:<br><br>>Unknown identifier. Parsing error near (QUERYABLE)<br><br>
So I need to maintain the template ad Layer level. This force the layer to use the template from that tag instead of the tag from FORMATOPTION.<br><br>Also I don't understand how to link the specific format option the a specific layer.<br>
<br>Thx,<br><br>Andrea.<br><br><br><div class="gmail_quote">2012/7/6 Lime, Steve D (DNR) <span dir="ltr"><<a href="mailto:Steve.Lime@state.mn.us" target="_blank">Steve.Lime@state.mn.us</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hi Andrea: You can define multiple output formats that use the template driver. They can each have different names and mime-types. You can even use mime subtypes
if you needed, say, two XML formats. The MapServer CGI supports a parameter called qformat that allows you to change the query template to be used. I’m not sure how this works with WFS, probably via mime-type.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Steve<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<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""> <a href="mailto:mapserver-users-bounces@lists.osgeo.org" target="_blank">mapserver-users-bounces@lists.osgeo.org</a> [mailto:<a href="mailto:mapserver-users-bounces@lists.osgeo.org" target="_blank">mapserver-users-bounces@lists.osgeo.org</a>]
<b>On Behalf Of </b>Andrea Peri<br>
<b>Sent:</b> Tuesday, July 03, 2012 5:42 PM<br>
<b>To:</b> <a href="mailto:mapserver-users@lists.osgeo.org" target="_blank">mapserver-users@lists.osgeo.org</a><br>
<b>Subject:</b> [mapserver-users] One template for every text type<u></u><u></u></span></p>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi,<br>
<br>
As report from documentation, MapServer will allow to define a template to set the return from an identify.<br>
<br>
I need to define almost two distinct kind of returns:<br>
One for user (text/plain or text/html) and one for business application (text/xml).<br>
<br>
So I like to define not only a template for return an XML but also a template for return an html page.<br>
<br>
I don't know how to say to MapServer what template us for text/html and what for text/xml.<br>
<br>
Is this possibile ?<br>
<br>
Thx.<br clear="all">
<br>
-- <br>
-----------------<br>
Andrea Peri<br>
. . . . . . . . . <br>
qwerty àèìòù<br>
-----------------<u></u><u></u></p>
</div></div></div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>-----------------<br>Andrea Peri<br>. . . . . . . . . <br>qwerty àèìòù<br>-----------------<br><br>