Hi Martin,

I gathered some questions for yesterday's meeting, however at the end we 
didn't have time for them, and you weren't there too. So here they come 
now:  :)

Right now I'm working on making possible to transform from 2d CRSes to Nd.

What I found out by now, that there is already a special case, when we 
transform from 2d to 3d: WGS84 to WGS84_3D, and there we fill the 
elevation with 0.

The other thing I recognized is, that when using compound CRSes, we 
transform pairwise, so splitting the CRSes, and trying to pair them in a 
way, that each pair can be transformed to each other.

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.

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.

What do you think about these? (And am I right regarding the current 
operation?)

Cheers,
Peter

-------------------------------------------------------------------------
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

Reply via email to