>
> That's nothing, what about:
>>
>     <Function name="strConcat">
>         <Literal>10</Literal>
>         <PropertyName>units</PropertyName>
>     </Function>
>

Not sure I understand - are you implying a conflict between literal syntax
and function arguments?

>
>> Sadly I think the first example is more consistent with the spirit of SE
>> 1.1 you quoted. The "2 3 10 1 m" allows you no ability to "fall back" to
>> the symboliser default.
>
>
> I don't understand this point.  How is "falling back" allowed in the first
> case but not the latter?
>
>
In the first example each numeric either:
a) has a unit; or
b) explicitly does not have a unit - implying it will use the default unit
for the symbolizer

In the second example the unit "m" applies to the array of literals "2 3 10
1". This does not provide the option of indicating 2 (default unit from
symbolizer) 3 10 1 (explicit unit "m")

> --
> David Winslow
> Boundless - http://boundlessgeo.com/
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to