Allow disabling geometry output for WFS

[sdlime]

In some cases one might not want to output the geometry associated with a
feature as part of a WFS response. I propose taking advantage of the
gml_geometries metadata element. That element allows you to define the
geometry(ies) associated with a layer (MapServer will create a default if not
set). By setting that value to "none" that would trigger MapServer to:
  
  - ommit the geometry from the describeFeatureType response
  - ommit the geometry (and bounding box) from a WFS query response

I've tested the proposed solution and it works nicely and could be taken
advantage of via WFS filters that exclude certain properties by setting metadata
on-the-fly.

[dmorissette]

Sounds like a good idea. BTW, how would that relate to the options discussed in
bug 300 comment 7 for instance? Bug 337 also contains related discussions.

[sdlime]

This fix can be applied to the GML writer for WMS too and would solve the 
geometry output problem defined in both of the bugs you reference. The 
include/exclude stuff also applies to WMS.

Steve

[dmorissette]

Cool. 

And then to really address all issues we should add a way to specify through
which service protocols a given layer should be available, along the lines of the  
SERVICES WMS|WFS|WCS|NONE that was suggested in bug 337.

[sdlime]

I did commit the geometry hiding code for both WMS or WFS to CVS HEAD.

Steve

[sdlime]

Dan: Another bug should be created for the services idea (SERVICES 
WMS|WFS|WCS|NONE). Then we can shut down this bug and those older ones. Sound 
reasonable?

Steve

[sdlime]

This was fixed long ago and if those other issues warrant tickets then I'm sure they'll show up... Closing.

Steve