Jody Garnett wrote:
> Sounds *great* Daniele; a strong +1 from me :-)
>
> I would like to start communicating "unsupported" modules a bit
> better; and "raise the bar" for participation. Could I ask you set up
> a documentation page with a code example earlier rather then later.
Ummm... I am not
Ok,
I have created a wiki page:
http://docs.codehaus.org/display/GEOTOOLS/IDL+Process
I will upgrade it with more info as soon as possible (I'm waiting for some
info from IDL people).
Regards,
Daniele
On Fri, Oct 30, 2009 at 2:14 AM, Ben Caradoc-Davies
wrote:
> +1 from me. Sounds like a useful
+1 from me. Sounds like a useful addition.
On 29/10/09 20:54, Daniele Romagnoli wrote:
> Hi list,
> I would like to add a new gt-idl-process unsupported module (leveraging on
> gt-process) on geotools trunk to allow exposing IDL algorithms/functions as
> geotools processes.
> We have used it on
Hi Daniele,
+1 from me as well.
I'm also very much in agreement with Jody's comments. As a general
aside, I'd also add that it would be great to have adequate javadocs
in unsupported module code. I know lack of docs isn't a problem
restricted to unsupported modules, but I think it's another hurdl
Daniele Romagnoli ha scritto:
> Hi list,
> I would like to add a new gt-idl-process unsupported module (leveraging
> on gt-process) on geotools trunk to allow exposing IDL
> algorithms/functions as geotools processes.
> We have used it on gt-2.5.x (within a private SVN) to add
> feature-extracti
Sounds *great* Daniele; a strong +1 from me :-)
I would like to start communicating "unsupported" modules a bit
better; and "raise the bar" for participation. Could I ask you set up
a documentation page with a code example earlier rather then later.
(I am tired of documentation / communication be
Hi list,
I would like to add a new gt-idl-process unsupported module (leveraging on
gt-process) on geotools trunk to allow exposing IDL algorithms/functions as
geotools processes.
We have used it on gt-2.5.x (within a private SVN) to add feature-extraction
(IDL based) capabilities to the geoserver