Tighten up the javadocs; make sure the bounds are described as contraining the contents (but perhaps not being minimal). The definition in GML2 had similar wording; a fact you can make use of when quickly returning bounds based on a BBOX query (use the origional query bounds).
Jody Jesse Eichar wrote: > Hi, > > The contract on FeatureSource is clear for count and bounds. If they > cant be efficiently calculated return -1 or null. But for > FeatureCollection it says to see the Collections.size method which says > nothing about -1 and the getBounds says nothing about null. The > DefaultFeatureCollection calculates the size and bounds and always > returns a value. > > ContentFeatureCollection calls the FeatureSource equivalents of the > methods. Easy code but doesnt seem to fullfill the contract. > > Comments? > > Jesse > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
