I've got a question about the best way to implement the the plug-in I'm working on for CRS transformations.
This plug-in will use the CRS code from the deegree library to perform a transformation. The GUI of the plug-in asks the user to select the Layer that is the target of the transformation, and also to enter the source and destination EPSG codes. Here is my question: As the plug-in is currently implemented I obtain the FeatureCollectionWrapper from the selected Layer and get an Iterator over the Features from it. I then pass each Feature to my transformer. A reference to the same feature is returned from the transformation method, BUT WITH A MODIFIED JTS GEOMETRY that results from the transformation process. When the code has finished transforming all of the Feature objects in the layer, the AbstractLayerable.fireLayerChanged method is called. Do you guys see any issues with this implementation? Should I be cloning the features and returning a new Layer or FeatureCollection object instead of modifying the existing Layer in place? Which technique would work the best for most of our users? Thanks for the input. I should begin unit testing the plug-in Monday and I may have an alpha release by the end of next week. The ability to transform images will be the next step, and will be very easy to add since the underlying deegree library already has the needed functionality. The Sunburned Surveyor ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
