Hello Peter
Bolla Péter a écrit :
> Now here comes my idea: when there are more CRS in a compound target CRS
> than in the source, we may add the needed number of dummy CRSes to the
> source, where these dummy CRSes could be transformed to any other CRS,
> filling the ordinates with some default values.
We could do that, but I would like to keep the CoordinateReferenceSystem object
as an accurate description of the "real" axis...
I'm rather thinking about just modifying the swapAndScaleAxis method. But in
order to confirm my idea, it would help if you could post the stack trace that
you get. This is in order to refresh my memory about which part of the code is
checking for extra dimensions.
> Regarding the question of mandatoriness, my idea is that we may add a
> special attributte to each axle of a CRS, that sets the default value.
> (I don't know yet, wether this is possible.) If there is a default value
> set, than we do the dummy transformation, and when it is not set, then
> we throw the exception just like now. This wouldn't break any working
> code then.
This idea make sense (we could create an OptionalAxis class which extends the
default axis class). But it would work only for users who create their CRS
programmatically. It would not work for CRS created from an EPSG authority code
or from parsing a WKT string for example.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
