Hey Gabriel, Justin, Thanks for the response. I am definitely expecting to have to write a GtGeometryAttributeImpl once I figure out better what is going on. I'm also hoping to be able to extract those properties from the features without actually getting and building the features. It seems there are some AttributeReader classes but perhaps those are unused, from the old feature model, or otherwise non-functional---we will see.
Meanwhile, a new question along the same lines: why are the various interfaces declaring getBounds() as returning the 2D BoundingBox rather than the completely general Envelope? Is this an oversight or are you really intending to facilitate the 2D case at the expense of generality? If the latter, how are we going to edit the javadoc to declare which 2D one should pull out of the various 3D CRS's and what to do with 1D CRSs? Finally, perhaps the text below clarifies slightly the Feature.getBounds() javadoc: * The coordinate reference system (CRS) of the returned bounds must be * derived from the geometric attributes which were used to compute the * bounds. In the event that the feature contains multiple geometric * attributes which have different CRSs, the returned bounds should use * the CRS defined by [EMAIL PROTECTED] #getDefaultGeometry()} and the calculation * of the bounds should reproject all other geometric attributes to that * CRS. * </p> * * @return the feature bounds, possibly empty. */ BoundingBox getBounds(); unfortunately, you'll have to edit the text to re-align it to the code. --adrian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
