Use the group attribute for all WFS interfaces

[assefa]

Upgrade the WFS interfaces to use the group attribute of a layer if availabale.
Also upgrade the interface DescribeLayer to use the group.

Initilally reported by : bart.van.den.eijnden@geodan.nl

[assefa]

*** Bug 518 has been marked as a duplicate of this bug. ***

[dmorissette]

How should that work? WFS doesn't allow nested layers like WMS does, so I'm not
sure to understand if we should honour the group attribute at all and how that
should work in the WFS interface.

Can you please explain what the expected behavior would be?

[bartvde@…]

You're right about the nesting part Daniel.

The grouping for WFS would only mean in my case grouping several shapefiles of 
different areas in the Netherlands into one WFS typeName. 

Also there is an area where both point and polygon features are present, so 2 
shapefiles are needed for this. In WFS ofcourse this can be 1 typeName.

These shapefiles are delivered every month by institutions, so grouping the 
data all the time would mean a lot of extra work.

So no actual nesting is needed, only grouping several datasets together into 
one big WFS typename.

[dmorissette]

Um... but there are other issues: all features of a given type in WFS need to
share the same schema (attributes) and SRS. What you're asking would require
that we scan the shapefiles of all layers in the same group to validate that
they share the same schema, that would also mean that the individual layers that
are part of a group should not be displayed individually (a side-effect that
other could consider as bugs). Not to mention the nightmare to handle this
internally in MapServer.

How about using a tileindex to group your shapefiles instead? That should do the
trick. And actually tiled OGR connections on shapefiles should already support
the mixed geometry types.

[bartvde@…]

Hi Daniel,

I did not think of that> It seems the right solution, to aggregate on the data 
side.

I will try this solution so I think we can delete this bug.

[bartvde@…]

Hi Daniel,

I have been testing this but run into two problems:

-GetFeatureInfo is not working on layers with a tileindex. Don't know why.
-in my WMS I was combining layers with different classifications. With the 
tileindex ofcourse I cannot do this.

--
It says queryable in the GetCapabilities, but no results are found using the 
GetFeatureInfo request.

<Layer queryable="1" opaque="0" cascaded="0">
        <Name>2002</Name>
        <Title>2002_vlakken</Title>
        <Abstract>2002_vlakken</Abstract>
        <SRS>epsg:28992</SRS>
        <LatLonBoundingBox minx="3.79733" miny="51.5413" maxx="6.94578" 
maxy="53.4753" />
        <BoundingBox SRS="EPSG:28992"
                    minx="49388.1" miny="395699" maxx="258475" maxy="609776" />
    </Layer>

[dmorissette]

Let's call this a WONTFIX. 

There appears to be an issue with GetFeatureInfo on OGR tile indexed layers, but
that should be a separate bug.