I actually think the GeoAPI javadocs for this function are clear. They make sense to me, taken directly from the ISO 19107 specs, and I'm not sure what could be written differently to describe the same thing.
I think the original implementation just ignored these docs by accident or perhaps the javadocs were not up to snuff at that time. Graham. Jody Garnett wrote: > Bleck - looks like a "simple" mistake. We should check that the GeoAPI > javadocs are *clear* so nobody else makes the same mistake. > Jody > >> It looks like the getDimension() implementation is either incorrect >> or not implemented in many cases throughout this module. It is meant >> to return the dimension of the geometry object, but for instance in >> MultiPrimtiveImpl it returns the dimension of the coordinate >> reference system. The ISO 19107 specs state in section 6.2.2.9 that: >> >> "The dimension of a collection of geometric objects shall be the >> largest >> dimension of any of its pieces. Points are 0-dimensional, curves are >> 1-dimensional, surfaces are 2- >> dimensional, and solids are 3-dimensional..." etc >> >> A quick browse through some other objects show that getDimension() >> returns a hardcoded value (ie: 2 for SurfaceImpl). I'll be going >> through this code to try and fix any getDimension() problems. >> >> > > -- Graham Davis Refractions Research Inc. [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
