stroke-dasharray and perpendicularoffset conflict in geoserver 2.16

[pvgenuchten]

bridge-style seems to always add a perpendicularoffset of 1 (why?)
seems in geoserver perpendicularoffset and stroke-dasharray conflict
stroke-dasharray is displayed as line, but when you remove perpendicularoffset, then the dasharray is displayed.

Does it relate to this SLD1.0 does not have perpendicularoffset?

In above picture also the arrow lines are missing, got a nice warning though in warning panel

[volaya]

That was an error in the conversion. It automatically converted measurement with a zero value to 1, assuming that they representa hairline width for stroke width parameters. That is correctly handled now.

[pvgenuchten]

@volaya i tried to reproduce this morning, but couldn't, the thing I noticed however was this.
Apparently geoserver applies the linecap inside the stroke-dash-array gap, with a high line width, the gap easily gets filled up with the linecaps.
Not sure if this will be considered as a bug in geotools, else we need to increase the gap size if a linecap is applied.

[volaya]

I made the gap twice as big in case there is a gap. See here:

dc38970

However, that won't work if the dash array has an odd number of elements, since each of the values willbe used for both the line and the gap. I guess it's a corner case and we can live with that...

[pvgenuchten]

why twice as big? afaik the gap size increase should be 2 * line-width (2 because the cap is added on both sides of the gap)