[mapguide-internals] RFC39 - Ready For Review - "Add layer name toWMS GetFeatureInfo response"

[Jason Birch]

Wow, just re-read the spec for GetFeatureInfo (even at 1.3), and am once
again wondering why they even bothered to include it.  There is no way
of reliably using the information returned from any server, without
having a knowledge of that server's implementation.

Since there is no guidance at all on what should be included in the
response to this query, I'm OK with this workaround.  It doesn't seem
"right" to bake application-specific logic into WMS, but it seems to be
what the spec requires...  

I'm thinking that for this kind of application WFS would be a better
approach anyway?  Not knowing anything about WFS, is there a way of
redirecting WMS GetFeatureInfo to WFS resources?  Or using a WFS
response to GetFeatureInfo (not sure if this problem exists in WFS as
well, or if it's specifically constrained to single-layer access)?

Jason 

-----Original Message-----
From: Chris Claydon
Subject: [mapguide-internals] RFC39 - Ready For Review - "Add layer name
toWMS GetFeatureInfo response"

MapGuide Open Source RFC 39 is now ready for review. It can be found at
the following location:

http://trac.osgeo.org/mapguide/wiki/MapGuideRfc39