Re: [Geoserver-users] Recode Transform problem when used with stroke-dasharray

Thanks - this subtlety is not obvious in the documentation (to me) - especially since the parameter to Recode is a Literal. So the next question is, is there a way to convert the Recode output into a Literal. I have tried wrapping the entire function invocation in a Literal block (doesn't

Re: [Geoserver-users] Recode Transform problem when used with stroke-dasharray

On Thu, Feb 28, 2013 at 6:22 PM, Tom S tom-sourcefo...@fatsheepfarm.comwrote: Thanks - this subtlety is not obvious in the documentation (to me) - especially since the parameter to Recode is a Literal. So the next question is, is there a way to convert the Recode output into a Literal. I

[Geoserver-users] Recode Transform problem when used with stroke-dasharray

I am seeing an odd behavior in GeoServer V2.2.2 with Style processing. I have a style that includes sld:Rule sld:MaxScaleDenominator8000.0/sld:MaxScaleDenominator TextSymbolizer Label ogc:Function name=Recode ogc:PropertyNamedata_type/ogc:PropertyName ogc:Literal0/ogc:Literal !-- Other --

Re: [Geoserver-users] Recode Transform problem when used with stroke-dasharray

On Thu, Feb 28, 2013 at 3:50 AM, Tom S tom-sourcefo...@fatsheepfarm.comwrote: I am seeing an odd behavior in GeoServer V2.2.2 with Style processing. stroke-dasharray only works with literals, there is no support for freeform expressions. There is some interest in making it allow freeform