That would be nice indeed.
My only limit there is that my client wants me to use geotools 2.5, so
I'm not sure I will be allowed to use your new version in the end.
I will have a look at it anyway, it's interesting.
I have another remark about the JMapPane, regarging performances...
They are not very good and decrease very rapidly with the number of
I have, for example, a file containing up to two million points. Yeah,
I know, it's a lot and displaying all of it may be irrelevant. That's
why I'm looking for ways to optimize it by not loading the whole file,
but sometimes, I still have a lot of points to draw.
The problem with the JMapPane is that when a feature changes in a
layer, it reads and displays again the whole layer, which in my case
becomes prohibitive. I thought the StreamingRenderer was about
streaming data. I don't know if it is badly used by the JMapPane or if
it doesn't provide the function, but it would be really interesting to
reload only the changes and to stream the data to the viewer in order
not to freeze everything for a couple of seconds when loading a big
amount of data.
I will soon investigate further these performance issues I have and
let you know what are the solutions I found.
Le 27 févr. 09 à 11:26, Michael Bedward a écrit :
> 2009/2/27 Benoît Thiébault <thiebault@...>:
>> The only problem is when you decide to resize the window containing
>> the map
>> : at some point, it seems the JMapPane (or is it the
>> StreamingRenderer ?)
>> asks all layers for their bounds and goes back to a view containing
>> all your
>> data (even if you were zoomed in...). Not very convenient...
> Hi Benoît,
> I've removed that behaviour from the revised JMapPane. Perhaps you
> could try it out when I commit the new code.