Hi Andrea - I fixed this problem with a quick hack for now...
The following code is used in a lot of places:
> public static CoordinateReferenceSystem decode(final String code)
> throws NoSuchAuthorityCodeException, FactoryException
> {
> return decode(code, false );
> }
As you can see the above value of false indicates that the calling code
does not want the value "forced" into XY terms. Really what the method
means is that the calling code does not care one way or another..
Here is the hack:
> public static CoordinateReferenceSystem decode(final String code)
> throws NoSuchAuthorityCodeException, FactoryException
> {
> return decode(code,
> Boolean.getBoolean(LongitudeFirstFactory.SYSTEM_DEFAULT_KEY));
> }
This turns the problem around so that if the calling code does not care,
we consult a system property (which the application uses to force the
issue in the event it does care).
I am committing this hack - and the test that matches your email.
To remove this hack we should make the ForceXY thing a proper Hint and
take the initial value from the System properties.
Please let me know if this does in fact improve matters for GeoServer.
Cheers,
Jody
-------------------------------------------------------------------------
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
