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. _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
