Paul,
You wrote: "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."
I agree that this is a good idea. I t
Hei,
sorry Paul for the late response. I am reading some of the left over
emails lately.
I think your idea sounds reasonable and makes sense to me.
However, I would hear first a comment by Andreas (because they have the
new lib and also have done the WMS/WFS stuff).
What you have been referein
Michaël,
I've found the QName very useful in my DataObject framework which is why
I was suggesting using it. It's also nice because it's part of Java so
we don't need to have a special jar for a custom identifier. This might
then be messy if we want to support using this identifier for many
d
>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.
>
>
Hi,
I'm just curious : is there a technica
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. T
