I think for a few specific cases, such as an SLD Recode function or Interpolate function we could look at the style definition and come up with an legend. If you just have the colors directly listed in your table we could not determine them statically from just the SLD file.
aside: if a developer did want to recognize recode / interpolate functions during legend graphic generation I would I recommend constraining it so polygon symbolizer would just be based on the expression used for fill for example. Rather than do the power set of variations of fill and stroke. This would be a feature request, happy to talk a volunteer through the design, or recommend on of our service providers. One thing I would recommend both of you doing is using the Geoserver style editor to provide an online resource (ie ready made icon) for the style. At the very least this would avoid you having a black polygon. You may also be able to use the Symbology Encoding 1.1 fallback value (which is used if a function is not available) to avoid having the default "black" used. -- Jody Garnett On Fri, 3 May 2019 at 07:20, Katie <[email protected]> wrote: > Hi all, > > I would like to know if someone has solved the Dynamic Legend issue that > Geowolf raised? > > I now have the same problem. I have a postgres table that I styled with a > sld using the color attribute from the color column. My map displays the > colors perfectly but does not show anything in the legend part from a black > polygon. > > Is there a way that I can edit the sld file to load attributes from a > column > in the same postgres table. > > Any help appreciated. > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
