It was part of the Filter 1.1 stuff - and I agree it has not been
communicated to my satisfaction either. At the time not a lot of people
were on trunk and I did well to even write down the interface changes.
Bleck,
Jody
> Jody Garnett ha scritto:
>> Nope I ment FeatureList - the provided query
Jody Garnett ha scritto:
> Nope I ment FeatureList - the provided query was supposed to request a
> sort order :-(
Jody,
frankly it's the first time I've heard speaking about FeatureList, and
of the supposed requirement to return an instance of it when sorting
stuff...
Cheers
Andrea
--
Nope I ment FeatureList - the provided query was supposed to request a
sort order :-(
Jody
> Gertjan van Oosten ha scritto:
>> As quoted from Jody Garnett <[EMAIL PROTECTED]>:
>>> I have gathered up the two FeatureList examples provided and place
>>> them onto the following page:
>>> - http://do
Gertjan van Oosten ha scritto:
> As quoted from Jody Garnett <[EMAIL PROTECTED]>:
>> I have gathered up the two FeatureList examples provided and place them
>> onto the following page:
>> - http://docs.codehaus.org/display/GEOTDOC/10+FeatureList
>
> You wrote:
>
> FeatureList featureList = (Fe
As quoted from Jody Garnett <[EMAIL PROTECTED]>:
> I have gathered up the two FeatureList examples provided and place them
> onto the following page:
> - http://docs.codehaus.org/display/GEOTDOC/10+FeatureList
You wrote:
FeatureList featureList = (FeatureList) source.getFeatures(query);
Can I
I have gathered up the two FeatureList examples provided and place them
onto the following page:
- http://docs.codehaus.org/display/GEOTDOC/10+FeatureList
> Well, actually I was using:
>
> final FeatureIterator iter = features.features();
> while (iter.hasNext()) {
> // ...
> }
> iter.
Hi Gertjan,
Andrea is correct when he states that FeatureCollection is an
inconsistent entity in geotools. To be quite honest with you it is a
complete mess.
The *only* part of the FeatureCollection api that is actually
implemented relativley consistently is the iterator part of it. This is
s
As quoted from Andrea Aime <[EMAIL PROTECTED]>:
> Geoserver uses feature sorting, so it works, but only if you specify
> it in the Query apparently?
For those keeping notes (or trying to get their own question answered by
searching through the archives): this way of sorting does not currently
work
Gertjan van Oosten ha scritto:
> As quoted from Andrea Aime <[EMAIL PROTECTED]>:
>> FeatureCollection is one of those topics where geotools developers
>> are not agreeing with each other, as such is not evenly covered usage
>> wise (which also mean QA wise). I personally don't like them, and
>> don
As quoted from Andrea Aime <[EMAIL PROTECTED]>:
> FeatureCollection is one of those topics where geotools developers
> are not agreeing with each other, as such is not evenly covered usage
> wise (which also mean QA wise). I personally don't like them, and
> don't rely on them more than as a glorif
Gertjan van Oosten ha scritto:
> Hello again,
>
> If I try to sort a FeatureCollection, I get a null FeatureList.
> So I do:
>
> final FeatureCollection fc = source.getFeatures(filter);
>
> and this returns my feature collection (an instance of
> JDBCFeatureCollection to be precise). Good. B
Hello again,
If I try to sort a FeatureCollection, I get a null FeatureList.
So I do:
final FeatureCollection fc = source.getFeatures(filter);
and this returns my feature collection (an instance of
JDBCFeatureCollection to be precise). Good. But:
final SortBy rt = ff.sort(sortField,
12 matches
Mail list logo
