Thanks Simone; I have a look when uDig rejoins trunk (it is holding at 2.6-M2 while we wait on some documentation).
So from your stand point are you in the clear with respect to things to move forward from 2.5.x? Are you content if we cut a release candidate shortly? I did notice you cleaning up some deprecated methods - thanks you :- ) Jody On Fri, Sep 4, 2009 at 7:29 AM, Simone Giannecchini<[email protected]> wrote: > On Wed, Sep 2, 2009 at 6:35 AM, Jody Garnett<[email protected]> wrote: >>>> 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? >>> >>> On a practical side, I am not so happy about exposing the internal >>> index to users so that they can play with it. >>> On the less practical side, I am not entirely sure that we should let >>> people do this kind of operations (band selection, color correction, >>> etc...) inside the mosaic while it should rather be part of a >>> processing step performed after loading. >> >> I agree it should be part of the data processing; it is much faster to >> do a fix once after all. In this case a customer was unable to >> modify the original dataset that had been processed incorrectly. >> >> I understand your hesitation to expose more of the internals; you are >> already exposing location for file location and toggle if the >> path is relative or not... >> > > Jody, I have committed on trunk the work I did for mosaic, just in > case you or Emily wanted to take a look. > > Simone. > >>>> 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... >>> >>> What's happening, at least from a cursory look, seems normal to me >>> since you are reprojecting the tiles individually. I'd rather first >>> mosaic them and then reproject as a whole. >>> I have a Mosaic operation on my todo list for GeoTools truunk, I guess >>> this is a case where it would be handy. >> >> Let me know when you have it and I can revisit this issue; for now it >> looked like they came up with a workaround. >> 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 >> > ------------------------------------------------------------------------------ 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
