Bryce wrote: "I would write wrappers. There's a lot of headaches already handled. Only tackle new headaches. :) "
Roger that. Byrce wrote: "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." Roger that. Bryce wrote: "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." Roger that. Thanks for this explanation. (Why didn't they just use a name like "InfiniteSetOfPoints"? That'd be to easy.) Bryce wrote: "19107 was written by math geeks." That explains the confusing name of TransfiniteSet. I think mathematicians do that to make casual math users like myself feel stupid. :] Bryce wrote: " 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." Roger that. Bryce wrote: "But adding precision to a single implementation sounds easier than starting from scratch using your own interfaces. :)" I'll see what I can do with the interface you pointed out. I think everything that I need is there, and I can use a wrapper. Jody wrote: "Bryce we add a Precision class to GeoAPI 2.1 - simply because all the implementations we have access to make use of something like that internally." I'd be willing to use a class like that, if it is already defined. What package is it in? The Sunburned Surveyor On 6/22/07, Jody Garnett <[EMAIL PROTECTED]> wrote: > Bryce L Nordgren wrote: > > 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. :) > > > Bryce we add a Precision class to GeoAPI 2.1 - simply because all the > implementations we have access to make use of something like that > internally. > > 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. :) > > > Remember that "done" is one half definition of the problem, and the > other "half" solving the problem. > Jody > ------------------------------------------------------------------------- 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
