>> - Some kind of grid coverage (image moasic?) work needs to be brought >> forward to trunk from 2.5.x? Simone I think you are on this one ... > > I am porting it right now. There is one problem I foresee the changes > that emily made a while ago to fiddle with the index. In my new scheme > I am having an hard time to find a place for them, that is why I have > been waiting this long. Some time from her myght be needed. > I also want daniele to come up with a milestone for imageio-ext 1.1 > that uses a newer version of gdal. > What do you mean by having a hard time to find a place for them? Perhaps I do not know your new scheme :-) As I recall they just detect a couple additional attributes in the moasic feature collection and slap on some JAI operations?
Emily do you have some to help with this? Or can we sort this out on the email list and not interrupt your work? I have one more odd issue (that may be either for Simone on Andrea) - have a look at the screen snaps here - http://jira.codehaus.org/browse/UDIG-1561 That is a series of GridCoverages (coming out of a tile server) that have been passed to the GeoTools renderer. Each individual grid coverage is being rotated/resampled due to the change of projection - resulting in a very cool effect. Simone is there any hope of sorting this out; or should we construct an image moasic of the tiles and try and using that rendering pathway? Andrea already caught us out using GridCoverageRenderer directly so we may already be on the hook for a rewrite... Jody ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
