WMS Enhancement? (Was: Re: [mapguide-internals] [RFC Review] RFC095 OGC WMS 1.3.0 Support)

[Jason Birch]

I definitely see a need to publish both individual feature type layers
(MapGuide Layers) and composite layers (MapGuide Maps) via WMS.

In my ideal world, I could

- set the WMS metadata on individual layers, and set a flag whether to
publish directly or not.

-  set WMS metadata on the map definition, and set flags to publish a
composite WMS layer for the map, publish all child layers with WMS metadata
as individual WMS layers, or both.

I'm not sure how this would be best implemented in the GetCapabilities.  I
understand that there is the concept of nested layers in WMS; would this
allow us to send the MapDefinition render if the outside layer is requested,
and the LayerDefinition render if the inside layer is requested?  Or would
it be better to just publish the MapDefinition as another top level WMS
layer?

(here's an example of a GetCapabilities with nested layers:
http://atlas.gc.ca/cgi-bin/atlaswms_en?VERSION=1.1.1&request=Getcapabilities&service=wms
 )

Jason

On 12 June 2010 02:29, Arthur Liu wrote:

> The first option is combining all the layers in a map as one single WMS
> layer, which means we drop the functionality to publish layers as WMS
> layers. The response of GetMap request is always a map image, and the client
> cannot get a layer's image.
>
> The second option is that we provide user the capability to publish both
> MapDefinition and LayerDefinition, that means user can get a whole map's
> image and he can also get some particular layers' image.
>
> Of course, the second option is better, I just want to know if it's
> necessary?
>
> Thanks,
> Arthur