Steve,
Many thanks for the thoughtful reply. I haven't looked at Mapserver's
rendering logic yet, but as the CLASS NAME binding would only be relevant for
MODE=LEGEND, perhaps there could be a separate bit of code developed for
generating a data-driven legend.
The use of the INCLUDE in
Hi Brent: Producing legends with bound styling is indeed problematic. MapServer
has no way to know how many variations are possible and it doesn't cache those
encountered in a map draw. Binding a class name might help but the binding is
at the feature level and a class name would generally apply
