Le lundi 19 février 2007 à 15:37 +0100, Andrea Aime a écrit : > > [...snip...] Is it a big problem, or is it okay if > > CRS.equalsIgnoreMetadata(ProjectedCRS, ProjectedCRS) work better only on > > Geotools 2.4? > > Hum... well, is it something that happens only sometimes, on some > obscure cases, or always?
Always when one ProjectedCRS is from SQL-backed database and the other ProjectedCRS is from WKT. > I can help with the backport if you wish. Looked around, I cannot spot > the revision number at which you committed the fixes on trunk. It should be revision 24275 according http://jira.codehaus.org/browse/GEOT-1160 but I need to check to be sure. The bug is related to interaction between different classes (especially "ProjectedCRS" vs "Conversion"), so the fix was not in a single place, but rather spread over maybe 10 files. A "svn merge" will probably produces some conflicts. I can imagine a workaround to put in a single place on the 2.3 branch that may work, at the risk of being too permisive (the fix on trunk tries to be as accurate as possible). I don't know if "too permisive" for the 2.3 branch will be a problem in practice... The idea is to ignore the "Conversion" object in "ProjectedCRS", and compare "Conversion.getMathTransform()" instead. It is build on the assumption that we are unlikely to have 2 ProjectedCRS with different Conversion but identical MathTransform. Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
