I don't remember.
Notes during the release process are here:
- http://udig.refractions.net/confluence/display/UDIG/1.2.0
They indicate the bug is http://jira.codehaus.org/browse/UDIG-1715
The class was called SLDs - it is an extension of the GeoTools SLD class which
contains lookup functions fo
Jody,
thanks for answering. But I still get the same problem - I'd prefer to
debug it in details before making noise in Jira, so please point me
which Java file has try/catch block you have added so I may debug into
it.
regards
Lukasz
Cytowanie Jody Garnett :
I closed that one before 1
I closed that one before 1.2.0; and updated the the docs with the example sld.
Please keep email on the public list :-)
- http://udig.refractions.net/confluence/display/EN/Style+Layer+Descriptor
I will be away the next couple weeks preparing for and then attending foss4g.
Maurcio (who may be abl
I was meaning in the layers view; see in your stack trace this line?
- at net.refractions.udig.ui.graphics.Glyph$6.getImageData(Glyph.java:363)
That Glyph class is only used by the Layers view so it can have something to
show for your layer. I think if your style is so much fun; it should focus o
Jody,
This error appears even if I do not have 'Legend' layer created.
regards
Lukasz
Cytowanie Jody Garnett :
It is just for the legend graphic I think.
On 06/08/2010, at 7:31 PM, Lukasz Stawicki wrote:
Jody,
I feel that catching an error and then drawing b&w is not a perfect
solut
It is just for the legend graphic I think.
On 06/08/2010, at 7:31 PM, Lukasz Stawicki wrote:
> Jody,
>
> I feel that catching an error and then drawing b&w is not a perfect solution
> - as I refer inside the function to attributes of feature I want to draw,
> maybe just use the real featur
Jody,
I feel that catching an error and then drawing b&w is not a perfect
solution - as I refer inside the function to attributes of feature I
want to draw, maybe just use the real feature to be drawn, not the
fake one?
Here is problematic part of my SLD. It is for some electrodevice, and
Oh cool.
Yeah the glphy code creates a fake feature in the hopes of drawing
something "in your style". We should put some catch statements around
that and perhaps draw the feature in B&W if we were unable to figure
out the style?
Lukasz can you sort out a way for us to reproduce the problem with
Hi,
I used instead of if_then_else.
Anyway, it crashes in CategorizeFunction.java line 152:
String lookupValue = lookupExp.evaluate(object, String.class);
Object is null - I debugged it up and finally digged what a object is
evaluated. net.refractions.udig.ui.graphics.Glyph.java, line 36
Please keep discussion on the list (that way I can be corrected by others :-D ).
Sorry for the quick message before; was focused on getting a bug report in. I
was not being intentionally opaque - the geotools website is down for me as
well.
Looking at the code the functions are:
- CategorizeFun
The GeoTools website was hacked last month; I think the DNS is being updated
now to point to a new server.
As for your example; you are doing a lot of work to map colours? There is a
couple of color lookup functions available now
which should make it easier.
I have reported your issue here:
-
Now we are talking - that is something I can make into a geotools bug report
and fix :-)
There is now 5 years difference between the rendering and filter code used in
uDig 1.1 and that available in the uDig 1.2 release.
Any "regressions" we can capture as a test case really help quality.
Jody
12 matches
Mail list logo
