Hi there, > I believe that the minX and maxX parameters to that function are > relative to the origin of the raster coordinates which means you would > add each of them to the raster's origin (rasterMinX) to get an absolute > min/maxX. So they look correct as written. > > If this change fixes the problem, then it is a side effect of moving the > right edge of the "startRow" call out to the right some more. That > could indicate that perhaps maxX was not calculated correctly in the > first place and so expanding it out "covers up" the problem.
Without having looked at the code, maybe this is a rounding problem? I think the pisces code was written for fixed point and adopted to floating point for OpenJDK. > It sounds like it needs more investigation than that simple change... Yeah. I will have a look as this also bothers me a little. /Roman -- Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org aicas Allerton Interworks Computer Automated Systems GmbH Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-48 USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe Geschäftsführer: Dr. James J. Hunt
