All,
At the moment we don't really deal with Coordinate Reference Systems in
a Task except for the WMS where you get to select the Coordinate
Reference Systems to send to the WMS server.
What I think we should do is have it so that you can select the
Coordinate Reference Systems for a task. Then any layers in the task
which use Coordinate Reference Systems can read that Coordinate
Reference Systems and do something with it. So in the case of WMS it
could read the CRS and send it to the server. Or if you have a
projection enabled loader it could project the data if required using
the CRS.
I think we should utilize QNames for specifying the CRS so for EPSG
codes it would be {EPSG}4326 (this is how QName in java encodes it as a
string). By using QName rather than an int it will allow us to support
different registries of CRS's.
We would need to add the CRS to the task and also support for setting
it. I know there was a plugin at some point which did something like this.
We would also need an option to set it for the task, this maybe a pop-up
when you create a new task.
The WMS plug-in could be modified to not ask for the CRS if the server
supports the current CRS or ask for it if it doesn't or if the CRS isn't
set for the task?
The driving need for this for me is I have a projection library and data
in different projections which I want to be automatically transformed
when loading it into JUMP.
Paul
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
