You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Using geostyler-lyrx-parser, I can read polygon with FillGraphic pattern. But I can not translate the padding around repeated symbols. (The offset didn't help)
The result is this one:
Describe alternatives you've considered
Otherwise, it would be possible to add a adding in the PointSymbol itself, but I think it doesn't make sens in other context than the GraphicFill/FillSymbolizer.
Additional context
In my use case, the GraphicFillPadding would be translated as VendorOption "graphic-margin" in the geostyler-sld-parser.
See also the related geostyler-lyrx-parser issue: geostyler/geostyler-lyrx-parser#64
The text was updated successfully, but these errors were encountered:
Feature Request
Is your feature request related to a problem? Please describe.
Using
geostyler-lyrx-parser
, I can read polygon withFillGraphic
pattern. But I can not translate the padding around repeated symbols. (The offset didn't help)The result is this one:
Describe the solution you'd like
I would like a solution to have space around
PointSymbolizer
fill marker in polygon. I propose to add aGraphicFillPadding?: expression<number>[]
next to theGraphicFill
poperty in on theFillSymbolizer
: https://geostyler.github.io/geostyler-style/docs/main/interfaces/FillSymbolizer.html#graphicFillThe result could be something like:
Describe alternatives you've considered
Otherwise, it would be possible to add a adding in the
PointSymbol
itself, but I think it doesn't make sens in other context than theGraphicFill
/FillSymbolizer
.Additional context
In my use case, the
GraphicFillPadding
would be translated asVendorOption "graphic-margin"
in the geostyler-sld-parser.See also the related
geostyler-lyrx-parser
issue: geostyler/geostyler-lyrx-parser#64The text was updated successfully, but these errors were encountered: