3D operations (Re: [geos-devel] C API coordinate sequence dimensions)

[Sean Gillies]

David, thank you.

Cheers,
Sean

On Jan 14, 2009, at 9:07 AM, David William Bitner wrote:

> Here are the specs that were used, the only requirement was for  
> intersection, but I'm not sure if anything else was affected.
>
>
>
> On Wed, Jan 14, 2009 at 3:04 AM, strk <strk at keybit.net> wrote:
> On Wed, Jan 14, 2009 at 07:54:21AM +0000, Mark Cave-Ayland wrote:
>
> > Can anyone with more experience with BuildArea (like Martin!)  
> comment on
> > whether this is a GEOS bug or simply a problem with behaviour > 2
> > dimensions being undefined?
>
> JTS didn't support 3d when I added it to GEOS, so can't really
> serve as a source of information. The 3d task was added driven by
> customer needs, so the only working and tested functions was the one
> the customer needed. If I recall correctly it was mainly Intersection
> and probably Union.
>
> Since other functions are based on the former, there may be side- 
> effects
> you wouldn't care about if you aren't using 3d features.
>
> Paul draw the specs about expected behaviour. Dunno if there's a doc
> around and I likely lost mine (Oops).
>
> --strk;
>
>  Free GIS & Flash consultant/developer      ()  ASCII Ribbon Campaign
>  http://foo.keybit.net/~strk/services.html  /\  Keep it simple!
> _______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel
>
>
>
> -- 
> ************************************
> David William Bitner
> <zpreservation.PNG>_______________________________________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geos-devel