GeoTools, the Java GIS toolkit

Hello all

Andy Turner a =E9crit:
> I now agree to use JAI and I think we both agree that it would be a goo=
d=20
> thing to have a custom TileCache implementation.

Sure, we can do that. But there is no rush :). We can write some spatial=20
algorithm first (in order to gets more experience with JAI), and look at=20
a custom TileCache implementation later if we feels we need it.=20
Furthermore, maybe some OpenSource implementations of TileCache exist=20
around there? The nice think with JAI is that the user can "plug in"=20
whatever TileCache implementation he wants without the need to change=20
anything to existing libraries.


> I think I understand:  Process what is needed and so only have in=20
> memory what is needed for that.  (There may be an argument also for
> processing more if idling just in case it is needed?)

Yes, this is a good point. There is a "prefecthTiles(...)" method=20
exactly for that purpose in javax.media.jai.PlanarImage:

http://java.sun.com/products/java-media/jai/forDevelopers/jai-apidocs/jav=
ax/media/jai/PlanarImage.html#prefetchTiles(java.awt.Point[])



>>   - Gets a RenderedImage as input.
>>
>>   - Use javax.media.jai.iterator.RectIter in order to iterate through
>>     all pixels values in this RenderedImage.
>=20
>=20
> Next week hopefully. Have a good weekend.

Many thanks for yours work :). Have a good weekend too,

	Regards

		Martin.

On Saturday 22 Mar 2003 7:37 am, Martin Desruisseaux wrote:
> Cameron Shorter a =E9crit:
> > You may be right in that the transform in DotToCoorinateTransformImpl
> > should be moved into MapPaneImpl.  I moved it out into it's own class
> > because I anticipated that Renderer eventually should used this trans=
form
> > too and by moving it into its own class I can ensure that Renderer
> > doesn't need to depend on MapPaneImpl.
>
> Sure, the Renderer will needs to know the 'dotToCoordinateSystem'. But
> instead of querying the MapPane for that, what about the opposite way:
> MapPane invokes Renderer.setDotToCoordinateSystem(AffineTransform) when
> needed (mostly just before to invokes Renderer.paint(Graphics2D))?

Yes, you are right, that was the other way I thought about writing it, ho=
wever=20
I thought creating a seperate class would be cleaner.