Okay Jody, I will do that. Thanks for your help. Regards,
David Walden Software Engineer Pitney Bowes Business Insight (formerly Encom) 355 Newcastle Street | Northbridge, WA 6003 Australia Phone 61 8 9436 8707 | Main 61 8 9226 0101 Fax 61 8 9226 0102 [email protected] www.pbbusinessinsight.com.au<http://www.pbbusinessinsight.com.au> From: Jody Garnett [mailto:[email protected]] Sent: Saturday, 4 June 2011 8:27 PM To: David Walden Cc: [email protected] Subject: Re: [Geotools-devel] Retrieving bounds for multiple geometries I think you can grab the feature collection back; and go through the results to build up the bounds yourself. What you can do is report this as an issue so the module maintainer knows about it. We don't get that many people with more than one geometry per row; so feedback and testing on this kind of topic is pretty rare. -- Jody Garnett On Saturday, 4 June 2011 at 9:51 PM, David Walden wrote: Hi Jody, Thanks for the response. The code buildEnvelopeAggregates doesn’t look right to me. If the idea behind it is to capture all geometry columns , shouldn’t SP_GEOMETRY2 be included in the sql string creation? Is there anything on the java side that I can do to get the result I want – ie modify the Query()/Filter object/s, without resorting to a db specific implementation? Regards, David Walden Software Engineer Pitney Bowes Business Insight (formerly Encom) 355 Newcastle Street | Northbridge, WA 6003 Australia Phone 61 8 9436 8707 | Main 61 8 9226 0101 Fax 61 8 9226 0102 [email protected]<mailto:[email protected]> www.pbbusinessinsight.com.au<http://www.pbbusinessinsight.com.au> From: Jody Garnett [mailto:[email protected]] Sent: Saturday, 4 June 2011 7:19 PM To: David Walden Cc: [email protected]<mailto:[email protected]> Subject: Re: [Geotools-devel] Retrieving bounds for multiple geometries I am guessing from what I have seen from the code, that the calculated bounds should include all geometry columns in the result. Is this correct? That is the intension; the "default" geometry is also supposed to represent the feature in this respect; often the default geometry can be something like a city area; and a secondary column be a point location representing the city centre. In the implementation (on the java side) both FeatureImpl and SimpleFeatureImpl check all the values producing a bounds of the result. The feature data structure can also store the bounds - if your database offers a data structure like an index which has this information already. Is there anything I can do to include SP_GEOMETRY2 in the bounds calculation? I think you would need to look at the "dialect" class for sql server in the code base. I expect you could modify it to query more than one geometry; and possibly have it look at the FeatureType first to check which geometry columns to ask for. Thanks for any help. Regards David ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Geotools-devel mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
