[mapserver-dev] MapServer SLD support

[Lime, Steve D (MNIT)]

Hi Jérome: Exellent news! What you outline would be a most welcome set of improvements. I have a feeling that most of the folks that initially build SLD support in MapServer aren’t very active anymore so we may be on our own. I’ll do what I can to help though and will take some time to familiarize myself with the SLD code a bit more.

It would be great to see you in Mpls this spring!

—Steve
________________________________
From: mapserver-dev <mapserver-dev-bounces at lists.osgeo.org> on behalf of jbo-ads <jbo-ads at laposte.net>
Sent: Thursday, February 21, 2019 10:36:02 AM
To: mapserver-dev at lists.osgeo.org
Subject: [mapserver-dev] MapServer SLD support

Hi,

I’m starting to work on improving SLD support in MapServer. So far,
we’ve identified seven issues that should be fixed for the benefit of our
internal projects and hopefully of the whole community of MapServer
users. These issues are:

        1. GetStyles: WMS “GetStyles” request returns a SLD file based
        only on MapFile configuration even if a SLD or SLD_BODY
        parameter is present in the request.

        2. UserLayer: MapServer implementation of SLD doesn’t handle
        <UserLayer> element.

        3. Add, Sub, Mul, Div: MapServer implementation of SLD doesn’t
        handle arithmetic operations in <SvgParameter> or other elements
        expected to hold arithmetic expressions.

        4. Style overriding: When several styling rules apply to a
        feature, only the first one is taken into account, instead of
        appliyng them all by following the “painters model” as described
        in Symbology Encoding specification.

        5. LineSymbolizer: Mark, ExternalGraphic: MapServer
        implementation of SLD doesn’t handle <Mark> or <ExternalGraphic>
        elements in a <LineSymbolizer> element.

        6. LineSymbolizer + PolygonSymbolizer: MapServer implementation
        of SLD doesn’t handle both <LineSymbolizer> and
        <PolygonSymbolizer> in the same <Rule> element (which is more
        expressive than both <Fill> and <Stroke> in the same
        <PolygonSymbolizer>).

        7. Literal, PropertyName: MapServer implementation of SLD
        doesn’t handle <Literal> or <PropertyName> elements in
        <SvgParameter> or other elements expected to hold arithmetic
        expressions.

Currently I’m working on issues #7 and #3. I plan to open issues and write RFC.
Any comments, discussions or advices from former developers of SLD in MapServer, or from other
MapServer experts, are warmly welcome.

Moreover, I am studying the possibility of attending the upcoming OSGeo
Community Sprint 2019 to be held in Minneapolis in May.

Regards,
Jérome.


_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fmapserver-dev&data=02%7C01%7Csteve.lime%40state.mn.us%7C3bbce58142b54d5d018b08d6981e1090%7Ceb14b04624c445198f26b89c2159828c%7C0%7C1%7C636863652227298564&sdata=qHViNP0TxFItT7XMuVzXeFg4Mxipu8Dt4Dno1UEKo%2FY%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20190222/432930d2/attachment.html>