Hello all
The issue is reported here:
http://jira.codehaus.org/browse/GEOT-1917
I don't think it is related to iteration order, since I'm usually careful about
avoiding iteration-order dependant code with HashMap/Set. Last time I looked at
this issue, I had the feeling that it may be related to the way floating point
numerical values are computed. Floating point arithmetic are not as determinist
than integer arithmetic - this is one of the few areas in the Java language
where the behavior is allowed to change slightly on different platforms. When
used in non-linear equations - especially in formulas like Math.exp(double), and
the projection code do have this kind of expression - a very small departure may
be amplified.
I'm right now working on projections in geotidy. I'm adding tests that the
referencing module never had before. I'm especially stretching right now (today)
what is happening close to poles where small departures get big amplifications.
As a benefit to the Geotools community, I think that we will get projections
that are more "mathematically smooth" (I means less discontinuities in the form
of "if" statement or ProjectionException).
As for the backport to Java 5, I commit myself to help with that.
Martin
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
