[mapserver-users] understanding behind the GetFeatureInfo...
Jukka.Rahkonen at mmmtike.fi
Thu Nov 19 14:41:58 EST 2009
I would say that the safest and perhaps also simpliest way might be to forget the text/html and let Mapserver read your data through database view so there is nothing to hide left. Each layer could then have inlude_items set to "all".
Martin Ouellet wrote:
> You're right, the template is acting as the controller for the html format
so there's no need to put the include/exclude items on top of it. I
was just trying to found out the safest (and the easiest) way to control my
data before exposing it.
> In a real case scenario, if a table structure beyond a layer change, I will
have to modify the html template but also all the wms|ows|gml include items.
> It's not such a big deal but since we have around 300 layer to maintain, It
would been convenient to have a unique list of field to updated. It would
also reduce the risk of error (ex: allowing one field in the gml mode but
not in the html mode)
> thanks again Daniel for your comments.
2009/11/19 Daniel Morissette <dmorissette at mapgears.com>
>> Martin Ouellet wrote:
>>> 3) GetFeatureInfo with INFO_FORMAT=text/html
>> Result: the only required tag is TEMPLATE (a dummy file will return no
>> data). But if you supply a valid html template, ALL the field will be
>> returned because the METADATA tag ows_<include|exclude>_items or
>> wms_<include|exclude>_items are ignored. So if my layer is a Oracle spatial
>> table, I must then create a view to expose only the field I want. Would it
>> be relevant to control the field with the "wms_include_items" tag ? Is there
>> a reason why is not working that way?
>> When you use a HTML template, it is the template itself that controls which
> fields are returned, so I am not sure to understand the benefit of
> supporting the include/exclulde items on top of that.
>> Are you saying that there is a situation where all the fields end up being
> unexpectedly dumped into the template out of your control? Maybe there is a
> hidden feature I am not aware of in the template processor, if that's the
> case then could you please elaborate?
> Daniel Morissette
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
More information about the mapserver-users