Christian Müller ha scritto: > Some questions: > > 1) > Should I rename gt-imagemosaicJDBC to gt-imagemosiac-jdbc ?
This would be consistent with the other modules, so it's a good idea. > 2) For testing I decided to use 3 pyramids, the third pyramid contains only > 1 image. The biggest dir contains the tiles for the original image, using > 9.6 MB. The whole src dir needs 16 MB. I found some modules which have > equal size, e.g widgets-swing-pending needs about 15 MB, or the ogc module. Wow, this is bad. How can widgets-swing-pending need that much data? Are you sure you're not including in your size count stuff that is generated during the build? Please avoid that, you don't need that much data. You can make a pyramid we a few hundreds of kilobytes, size does not matter for unit testing, and for performance testing, the current 12MB are not enough anyways. The ideal (but this is more work, so nobody is asking you to do so) would be to generate your test data on the fly. I mean, you don't really need a specific image content, so you can just generate buffered images on the fly, draw a number or something inside of them, and save them on the disk. > The tiles for itself will not change. I know the binary file problem from > CVS assuming there are the same problems with SVN. Since mosaicing and > selecting the correct pyramid is the key feature, I need these images for > testing. The problem is not about how svn handles svn data, but put yourself in the pants of someone that has to check out geotools from a country with slow internet connection. Moreover, I believe there are performance issues in svn when the repository becomes too big. Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
