On Wed, Oct 21, 2015 at 4:15 AM, Pedro Venâncio <[email protected]> wrote:
> Hi Anna, > > > > Will this be backported to 7.0.x? >> >> I believe I backported it, 7.0.2 RC1 release is just going on now, there >> will be an announcement soon. >> >> > Thanks, I will check! > > > > >>> >>> Then I wanted to transform the z-coordinate to >>>> >>>>> an attribute column using >>>>> v.to.3d -r input=contour_3d col="CONC" output=contour_2d >>>>> (I added CONC column to contour_3d before, using v.db.addcol >>>>> map=contour_3d >>>>> columns="CONC double precision"). >>>>> However, the resulting contour_2d column CONC remains empty. No error >>>>> is >>>>> reported. >>>>> >>>>> >>> It is not possible to avoid this procedure, of creating the new column >>> in the layer of origin (3d layer), to get the height column in the 2d >>> layer? Something like the 'column' parameter of v.random (Name of column >>> for z values; Writes z values to column), where we just give a name to the >>> height column in the resulting layer? >>> >>> >>> > What do you think about this workflow? > I think how it currently works, doesn't make sense for the reverse case, please create a ticket. The column should be created in the new vector. > > Thanks! > Pedro > >
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
