Jody Garnett ha scritto:
> That information was in there; I remember adding the ability to get the
> parameter names last year.
>> The GeoApi Function javadoc says that FilterCapabilities
>> should be used to provide the intel on what functions
>> are available, and what arguments they do provide.
Justin Deoliveira ha scritto:
> Hi Andrea,
>
> I ran up against this exact same issue a while ago to. And the response
> was to indeed use FilterCapabilities and some other construct... Library
> or some such... can't quite remember.
Well, let's hope Jody fills us in, at the moment it seems to
That information was in there; I remember adding the ability to get the
parameter names last year.
> The GeoApi Function javadoc says that FilterCapabilities
> should be used to provide the intel on what functions
> are available, and what arguments they do provide.
> Unfortunately someone had a c
Hi Andrea,
I ran up against this exact same issue a while ago to. And the response
was to indeed use FilterCapabilities and some other construct... Library
or some such... can't quite remember.
Jody should be able to provide more information. But I do think the idea
of breaking out a separate
Hi,
I'm stumbling in a few places in GeoTools where it's hard to perform
a switch to the GeoApi filter API because of a design issue.
Basically, GeoApi does not seem to offer any way to figure out
the function arguments count and their types. Given that functions
are not standardized as filters, a
