Milton Jonathan ha scritto: > Hello folks > > Humbly stepping in: I believe that if there is support for multiple > geometries (and thankfully there is!), then all such geometries should > be considered for every operation when the user has not specified anything. > > In fact, I have noticed that this is indeed the behavior implemented in > SimpleFeatureImpl.getBounds(): it checks all geometries to compute the > feature's bounds. > > On the other hand, this is NOT the way things are implemented in > MemoryDataStore.getBounds(): it could have just asked for each Feature's > bounds, but for some reason it computes the bounds explicitly using only > the default geometry. In my current view of things, this would be > considered a bug..
It looks like one to me as well. If you want to open a bug report.. (and maybe also attach a patch to solve it? ;-) Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
