> That still leaves a lot of processes in org.geotools.process.raster.gs: > Perhaps I don't understand your question?
My question is can we move the contents of the raster.gs package into raster and delete the gs package ? > I don't mind if we add the static methods; it was not done yet as it is not > required by the interface (only a convention we made to make it easier for > people to use quickly). Let me re-phrase my question. Is it now so easy to run the processes directly that we no longer require the static helper methods ? And if the answer is no, then would it actually be preferable to have direct use via coverage operations (or something) than via static methods in processes ? And for bonus points: If raster process classes start to multiply (e.g. because they are convenient for GeoServer use) then could this be a source of confusion for users looking at coverage operations vs processes ? Michael ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
