> Bryce wrote: "Looks like GM_GenericCurve will get you 90% of the way > to where you want to go."
> Agreed. The question is, what can I do about the other %10. Also, I > don't see a way to specify acceptable accuracy tolerances in some of > the GenericCurve methods. This is important to me. > I would write wrappers. There's a lot of headaches already handled. Only tackle new headaches. :) > Byrce wrote: "It's not > quite clear from your interface what exactly happens between the two > endpoints of your LinearGeometry. If I may assume that you linearly > interpolate, then you're talking about a GM_LineSegment." > > I think I would need to clarify this in the supporting documentation > for the interface. If I understand what your saying, then no I don't > want to have linear interpolation in most cases. I want the interface > to work with true curves. Then the curve interface is exactly what you want. A curve is composed of curve segments which can have arbitrary "shapes". For instance, a line segment could be connected to a spline connected to an arc, etc. You can treat all of these alike because they all inherit the same "GenericCurve" interface. > I'm a little confused about the purpose of TransfiniteSet. Either this > class is a little too abstract for my purposes or I need more > explanation in the Javadoc comments. :] I don't think so. :) TransfiniteSet is JTS. It just uses some different terminology (from set theory). A circle is what? The _set_ of all points exactly radius "r" from a center point. If you ask circle.contains(pointA), you'll get a "true" if and only iff "pointA" is exactly circle.radius away from circle.center. A curve is the _set_ of all points which lie along the curve. "Is pointA on the curve?" is exactly the same as asking curve.contains(pointA)? Same thing different words. 19107 was written by math geeks. > I don't think this is quite close enough for what I want to do. Maybe > I can use some wrappers? At any rate, the code is of interest to me, > and I will look at it closely. (For example, I forgot to include a > tangent method.) I know it won't do everything (For example, they forgot to include a "normal" method.) :) But it does sort out a lot of headaches and give you a giant head start. Plus, if you code against GeoAPI, you're not tied to a particular implementation. As to specifying precision...that's going to have to be implementation dependent for now. As you noticed, there's no means of specifying precision or tolerances in the interfaces. That's because 19107 left it out too. But adding precision to a single implementation sounds easier than starting from scratch using your own interfaces. :) Have a good weekend. I don't wanna sound like a salesman for GeoAPI. I'd just hate to see you start from scratch when it sounds like so much is already done. :) Bryce ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
