Hi, thx very much. your suggestion is reallly useful. this setting, ows_include_items "all" seem to be not available on documentation.
the documentation report only the "gml_include_items" but it don't work for text/plain. I you setting and all the attributes are appeared. Also I'm see-ing the outputformat (a template driven I have setting) is ignored. I don't know if this is correct. Actually seem MapSever will generate the output of a GetFeatureInfo using template driven only if not set the ows_include_items "all" Andrea. 2012/7/11 Eichner, Andreas - SID-NLKM <[email protected]> > The URL actually gives a feature result (#135), but no attribute data. > You need to set {wms,ows}_include_items metadata at layer level: > * wms/ows_include_items: comma delimited list or keyword 'all' > > HTH > > > -----Ursprüngliche Nachricht----- > > Von: [email protected] > > [mailto:[email protected]] Im Auftrag > > von Andrea Peri > > Gesendet: Mittwoch, 11. Juli 2012 12:45 > > An: Lime, Steve D (DNR) > > Cc: [email protected] > > Betreff: Re: [mapserver-users] One template for every text type > > > > Hi Steve, > > > > thx very much for you rhint. > > I ubnderstand and start to try it. > > > > Now I found some strange. > > It seem mapserver trunk don't work well when mime/type = text/plain. > > > > I see infact the sample link in the documentation for text/plain > > repeort this result > > (no feature listed) > > http://demo.mapserver.org/cgi-bin/wms?SERVICE=WMS&VERSION=1.1. > > 1&REQUEST=GetFeatureInfo&BBOX=-11.332970,24.121208,47.584718,5 > > 7.965035&SRS=EPSG:4326&WIDTH=1001&HEIGHT=575&LAYERS=cities&STY > > LES=&FORMAT=image/png&TRANSPARENT=true&QUERY_LAYERS=cities&INFO_FORMAT=text/plain&X=229&Y=280 > > > > Instead using the html link mapserver list the features. > > > > http://demo.mapserver.org/cgi-bin/wms?SERVICE=WMS&VERSION=1.1. > > 1&REQUEST=GetFeatureInfo&BBOX=-11.332970,24.121208,47.584718,5 > > 7.965035&SRS=EPSG:4326&WIDTH=1001&HEIGHT=575&LAYERS=cities&STY > > LES=&FORMAT=image/png&TRANSPARENT=true&QUERY_LAYERS=cities&INFO_FORMAT=text/html&X=229&Y=280 > > > > > > > > 2012/7/9 Lime, Steve D (DNR) <[email protected]> > > > > > > The QUERYABLE parameter was never implemented so you > > still must define a layer TEMPLATE to mark a layer as being > > queryable. The template need not exist so typically I just do: > > > > > > > > TEMPLATE 'void' > > > > > > > > The link between layers and OUTPUTFORMAT templates are > > in the templates themselves via the [resultset] tag. > > > > > > > > Steve > > > > > > > > From: Andrea Peri [mailto:[email protected]] > > Sent: Monday, July 09, 2012 5:15 AM > > To: Lime, Steve D (DNR) > > Cc: [email protected] > > Subject: Re: [mapserver-users] One template for every text type > > > > > > > > Hi Steve, > > thx for hint. > > > > I read the doc and also the RFC 36. > > I'm having also some doubt. > > > > I try to set this output format: > > > > OUTPUTFORMAT > > NAME "delimitazione_fogli_xml" > > MIMETYPE "text/xml" > > DRIVER "TEMPLATE" > > FORMATOPTION > > "FILE=/pat-to-ex-template-on-layer-level/template_xml.tmpl" > > END > > > > at WEB level I set this value: > > WEB > > METADATA > > "wms_feature_info_mime_type" "text/xml" > > END > > END > > > > And how explained from RFC I comment the template from > > layer level and try to add the tag > > QUERYABLE TRUE > > (But this option seem to be not supported from > > MapServer 6.2 trunk) > > > > If I remove the template tag from layer level I have this error: > > > > msWMSFeatureInfo(): WMS server error. Requested > > layer(s) are not queryable. > > > > And if I try to add the QUERYABLE TRUE tag I have > > this error: > > > > >Unknown identifier. Parsing error near (QUERYABLE) > > > > 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. > > > > Also I don't understand how to link the specific format > > option the a specific layer. > > > > Thx, > > > > Andrea. > > > > > > > > 2012/7/6 Lime, Steve D (DNR) <[email protected]> > > > > 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. > > > > > > > > Steve > > > > > > > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Andrea Peri > > Sent: Tuesday, July 03, 2012 5:42 PM > > To: [email protected] > > Subject: [mapserver-users] One template for every text type > > > > > > > > Hi, > > > > As report from documentation, MapServer will allow to > > define a template to set the return from an identify. > > > > I need to define almost two distinct kind of returns: > > One for user (text/plain or text/html) and one for > > business application (text/xml). > > > > So I like to define not only a template for return an > > XML but also a template for return an html page. > > > > I don't know how to say to MapServer what template us > > for text/html and what for text/xml. > > > > Is this possibile ? > > > > Thx. > > > > -- > > ----------------- > > Andrea Peri > > . . . . . . . . . > > qwerty àèìòù > > ----------------- > > > > > > > > > > -- > > ----------------- > > Andrea Peri > > . . . . . . . . . > > qwerty àèìòù > > ----------------- > > > > > > > > > > -- > > ----------------- > > Andrea Peri > > . . . . . . . . . > > qwerty àèìòù > > ----------------- > > > > > > > -- ----------------- Andrea Peri . . . . . . . . . qwerty àèìòù -----------------
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
