I dont understand why what I suggest keeps you from specifying styles for the overlays. it’s my understanding that, in a normal (eg image/png) WMS request:
LAYERS=layer1,layer2,layer3&STYLES=style1,style2,style3
means to apply style1 to layer 1, style 2 to layer 2, etc. Why not just do the same with the OpenLayers version? in OpenLayers, you can specify a style for each WMS layer if you want, be it a base layer or overlay.
as for adding more parameters to the WMS GET string, I thought that was a big no-no, since it is non-standards compliant.
I maybe be missing Andrea’s point; I’m not really so sure what you mean by CQL filters, OGC filters, and normal and list-based params.
thanks,
mike
Michael Frumin ha scritto:
I dont understand why what I suggest keeps you from specifying styles for the overlays. it's my understanding that, in a normal (eg image/png) WMS request:
LAYERS=layer1,layer2,layer3&STYLES=style1,style2,style3
means to apply style1 to layer 1, style 2 to layer 2, etc. Why not just do the same with the OpenLayers version? in OpenLayers, you can specify a style for each WMS layer if you want, be it a base layer or overlay.
That's not the only way to specify a style. There is also SLD_BODY and
the SLD url location.
as for adding more parameters to the WMS GET string, I thought that was a big no-no, since it is non-standards compliant.
Quite the opposite, for non standard behaviour vendor parameters are
foreseen by the standard itself.
I maybe be missing Andrea's point; I'm not really so sure what you mean by CQL filters, OGC filters, and normal and list-based params.
These are vendor extensions to support the same filtering abilities you
would have with a WFS GetFeature request. Quite useful when you need it.
Oh, CQL is a non XML human readable way to specify a filter.
Cheers
Andrea