Hello everybody,
while we at uDIG make use of MetaBufferEstimator I run into the following
issue:
The features are LineStrings and the style has the following definition,
represented as ans SLD fragement:
<sld:LineSymbolizer>
<sld:Stroke>
<sld:CssParameter name="stroke">
<ogc:Literal>#008000</ogc:Literal>
</sld:CssParameter>
<sld:CssParameter name="stroke-width">
<ogc:Function name="Categorize">
<ogc:PropertyName>myProperty</ogc:PropertyName>
<ogc:Literal>1</ogc:Literal>
<ogc:Literal>101</ogc:Literal>
<ogc:Literal>2</ogc:Literal>
<ogc:Literal>300</ogc:Literal>
<ogc:Literal>4</ogc:Literal>
</ogc:Function>
</sld:CssParameter>
</sld:Stroke>
</sld:LineSymbolizer>
Having the CategorizeFunction as Literal the Estimator returns false
for isEstimateAccurate() which leads into logging massages in uDIG such as
this:
!MESSAGE Assuming rendering buffer = 0, but estimation is not accurate, you
may want to set a buffer manually
I expected an valid buffer size for this kind of Literal and assumed to get
the greatest value, in this case 4.
I've no idea if there are other Literal functions mere it could make sense
to return the maximum value of all options. What do you think about
extending functionality for strike-width values. I know that this would
lead into several additional cast checks but I guess its worth to get an
accurate estimate.
BTW: uDIG uses the value to find out which area to render if any changes to
the feature occurred.
Whats your opinion?
Thanks
- Frank
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel