So Martin I am stuck on this one - what should I do? If you explain the 
problem well enough I do not mind trying my hand at an implementation. 
As I understand it any CRS with more than two axis is fatal right now?

Jody
> Andrea Aime a écrit :
>> Martin, how hard would it be to make that method work with ellipsoidal
>> height?
>
> Not really hard. At the difference of other cases, the 3D Ellipsoid 
> case requires the instantation of new objects.
>
> We need to add in CRS.getHorizontalCRS(...) a special test for the 
> GeographicCRS 3D case. We need to get its EllipsoidalCS, inspect the 
> axis and retains the ones that are not height (may be at any index - 
> checking the direction should be okay). Then we create a new 
> EllipsoidalCS with those axis, and a new GeographicCRS with that CS.
>
> We may need to handle a FactoryException. Adding this throws clause 
> would be compatibility break. We may decide that it is acceptable, or 
> we may also decide that we could log it and returns null since it is 
> documented as a valid return value when the 2D part can't be obtained 
> for some reason...
>
>     Martin


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to