Simone Giannecchini a écrit :
>> * getHorizontalCRS returns the GeographicCRS or ProjectecCRS part that apply
>> to the Earth's surface, so at the difference of 'getCRS2D' it has a real
>> geophysics meaning and for this reason is a commited API. Note however that
>> if you have a DerivedCRS, this method will unwrap it up to the underyling
>> GeographicCRS or ProjectedCRS, which may not be what you want (it depends
>> what you want to do). Note also that current implementation will fail for
>> 3D GeographicCRS with ellipsoidal height.
>
> It seems that this would be the right method to use for most of m
> needs but I am wondering about what we could do about the cases you
> mention here where the method would fail. I have not looked at the
> method's code yet, do you think it would be hard/ possible to fix
> them?
The 3D GeographicCRS would requires some work, not only in CRS.getHorizontalCRS
but also (the most tricky part) in DefaultCoordinateOperationFactory.
The unwrapping of DerivedCRS is not really a work that need to be done. It is an
arbitrary choice based on the assumption that GeographicCRS or ProjectedCRS is
usually what we want when we think about "horizontal CRS", but that choice can
be criticize. We may need to scan through getHorizontalCRS usage and see if this
choice still appropriate.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
