[Mapserver-users] getfeatureinfo

Shane Nelson snelson at refractions.net
Wed Nov 19 15:01:54 EST 2003


Quoting Doug Cates <doug at moximedia.com>:


> 
> Well, we can do whatever we want with the GetFeatureInfo response
> because it is undefined by OGC, so your suggestion would work, but the
> WFS specification says that a WFS _MUST_ support GML2 responses for the
> GetFeature response, so the layer name must be returned as an element,
> not an attribute of an element.
> 
> 


The issue of the GetFeatureInfo response recently came up on the wms-dev mailing
list.  For those who missed it:

------------------------------


--- Dirk-Willem van Gulik <dirkx at webweaving.org> wrote:
> 
> > However, we can't properly cascade GetFeatureInfo requests (with some
> > simple exceptions), but that's mostly because there hasn't been one single
> > good standard simple GML format in common between the different clients
> > and servers.  All the WMS specification has to do to rectify this is to
> > recommend that clients and servers support, for example, the GML 3 level 0
> > (OGC document #03-003R10) format for GetFeatureInfo requests.
> 
> Aye - now we are talking :-)
> 
> Dw

I have been working on adding GetFeatureInfo into the arc3wms client
(http://www.refractions.net/arc3wms).  I have also found the results to be less
than useful.  I'd like to be able to put the results into a table much like the
arcview Identify tool works.  When all I have to work with is text/html or any
other random result this is impossible - I am forced to launch an external web
browser to view the results.
 
A computer parse-able format would be very helpful.





More information about the mapserver-users mailing list