We're in the process of changing how the renderer works. Before I
commit this change to the DefaultRasterMapProducer, could you check and
see if this is going to affect anything on the WMS-with-raster/WCS
branch?
Here is the new interface:
http://svn.geotools.org/geotools/branches/2.1.x/module/main/src/org/geotools/renderer/lite/Renderer.java
here is the new renderer code (basically the same as 2.1.x lite2 with
minor changes):
http://svn.geotools.org/geotools/branches/2.1.x/module/main/src/org/geotools/renderer/lite/StreamingRenderer.java
I've attached the entire DefaultRasterMapProducer.java to this message.
If this is going to affect you, please say now. Most likely the only
change will be to add methods to the interface, but I want to see whats
required and whats not. I've tested this code on the "normal" WMS
stuff, but I dont know if something special is required for
WMS-with-raster or WCS.
The main difference in the renderer is that you send hints to it instead
of set/get methods. Currently only "optimizedDataLoadingEnabled" does
anything.
------------------------
Here's the modified DefaultRasterMapProducer code (around line 200):
renderer = new StreamingRenderer();
renderer.setContext(map);
RenderingHints hints = new
RenderingHints(RenderingHints.KEY_ANTIALIASING,
RenderingHints.VALUE_ANTIALIAS_ON );
renderer.setJava2DHints(hints);
//we already do everything that the optimized data loading
does...
//if we set it to true then it does it all twice...
Map rendererParams = new HashMap();
rendererParams.put("optimizedDataLoadingEnabled",new
Boolean(true) );
Envelope dataArea = map.getAreaOfInterest();
AffineTransform at =
this.renderer.worldToScreenTransform(dataArea, paintArea);
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/
(attachments)
DefaultRasterMapProducer.java (8.12 KB)