[udig-devel] UDIG 0.6 short term reprojection targets

[Jody Garnett <jgarnett@xxxxxxxxxxxxxxx>]

We have been brainstorming the short term target of reprojection support 
for UDIG 0.6 - thanks for the help Martin BTW.
Geotools gets tagged w/ this email as well since CRSAuthorty is 
mentioned as part of this work.

What we have so far: (x = done, - = not done)
x CRS Object specified by Viewport
- CRSAuthority (owned by gt2 CRSService) responsible for keeping a weak 
referenced cache.
 When/if Martin/Rueben switch to a small database (hibernate?) for this 
data structure the api
  can remain the same.
- Projection UI based on EPSG codes for the first cut, will remember the 
last EPSG code
 via plugin settings persistence rather than a back pointer from CRS 
object to EPSG code.
x FeatureRenderer reprojection on rendering
- FeatureRenderer backprojection on info and select
- ArcGrid import
- GridRenderer reprojection is needed, based on the J2D renderer model 
of back projecting
  points to resample the origional.
- GridRenderer backprojection on info and select
- WMSRenderer reprojection on rendering.
  Will need to convert from the EPSG codes supplied by the 
GetCapabilities object
  to real CRS objects. From there we can use CRS.equals(..) to figure 
out transformation.
  To repeat we will not remember the EPSG code for WMS, it will be 
responsible for
  maintatining its own mapping for the codes it understands.
- WMSRenderer backprojection on info and select
- The back projecting trick can be used by WMS to cover any projections 
not directly supported
  by the server.

Did I miss anything?
Jody