[GRASS-dev] 3D vector support in v.overlay

Would anybody be interested in adding support for 3D vectors in v.overlay ? How big a task would this be? I am wanting to extract 3D contours over a defined area.

Mark

On Mon, Feb 22, 2010 at 9:02 AM, Mark <mscaife@mac.com> wrote:

Would anybody be interested in adding support for 3D vectors in v.overlay ?
How big a task would this be? I am wanting to extract 3D contours over a
defined area.
Mark

I see in the source code:

main.c: Vect_open_new(&Out, out_opt->answer, WITHOUT_Z);

Not sure if it would be sufficient to change this to WITH_Z) and
recompile?

Markus

Hi,

Does it Work or not ?

Thanks,
Sylvain
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/3D-vector-support-in-v-overlay-tp4610942p5393406.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

I try it under Ubuntu 10.04 and it work well !

Great ! Should it be integrated to the next version ?
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/3D-vector-support-in-v-overlay-tp4610942p5393742.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

In fact, it didn't work as I expect:

See the screenshot, you will see the difference between v.overlay2D and
v.overlay3D (operator and as intersect).
v.overlay3D produce 2 layers and the result is very bad

v.overlay2D => http://yfrog.com/afvoverlay2dp
v.overlay3D => http://yfrog.com/n3voverlay3dp

How could I improve this to work that I expect (v.overlay2D) to produce a 3D
vector?
How could I work around the problem ?

Thanks in advance
--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/3D-vector-support-in-v-overlay-tp4610942p5411421.html
Sent from the Grass - Dev mailing list archive at Nabble.com.