[Martin Desruisseaux <martin.desruisseaux@te...>]

andriusb@... a =E9crit :

> Maybe any one can help me to improve drawing, or knows witch class in g=
eotools
> is responsible for feature drawing? Or maybe geotools is not ready for =
such
> amount of data?=20

The performance problem in J2D renderer is complex. It already has some=20
feature that try to speed it up (decimation, clipping, caching...), but=20
this is not enough. Some area that need to be implemented are:

  - Avoid putting all coordinates in memory before to start drawing
    (to be done with specialized implementation of PointArray).

  - Finish the implementation of geometry tiling (this is already
    partially implemented; we need to write the last piece of code
    that will enable it).

  - Speed-up Geometry.contains(...) and intersect(...) methods
    (I have some idea about how to do that).

  - Multi-thread rendering on bi-processor machine.

  - Progressive rendering if possible (already implemented for
    GridCoverage, providing that the underlying RenderedImage
    is tiled).


> If any one knows some forum, article, what ever, related to this proble=
m, please
> help me.

Unfortunatly, I have been unable to do any significant work on J2D=20
renderer for at least one year. I sincerly hope that this situation will=20
improves before the end of this year (I know, I said exactly that one=20
years ago... :( ).

In the mean time, there is some links of potentiel interest:

    http://jira.codehaus.org/browse/GEOT-5
    http://jira.codehaus.org/browse/GEOT-52
    http://jira.codehaus.org/browse/GEOT-51


	Martin.