I imported a GMT multisegment ASCII file with contour lines using v.in.ogr,
resulting in 3D vector file. 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.
I am sure contour_3d contains correct Z-values (I transformed it to raster
to see).
On Tue, Jun 16, 2015 at 9:42 AM, JanaKr <jkrajc@gmail.com> wrote:
Hello,
I imported a GMT multisegment ASCII file with contour lines using v.in.ogr,
resulting in 3D vector file. 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.
I am sure contour_3d contains correct Z-values (I transformed it to raster
to see).
Does anyone know what I am doing wrong, please?
nothing, it just was not implemented for lines, since 3D lines can have vertices of different heights, but we can upload only one value. However, since it makes perfectly sense for contours, I added the support for lines there (r65493). Any chance you are using GRASS 7.1 (trunk) to try it out?
On Wed, Jun 17, 2015 at 2:57 AM, Jana Krajcovicova <jkrajc@gmail.com> wrote:
No, I am using GRASS 6.4.
So it is only newly implemented in 7.1?
Yes, since yesterday. What operating system do you use? For Windows, there
are daily builds available and for Ubuntu there is a PPA. The change might
not be in today's binaries, probably tomorrow.
Anna
Jana
On Wed, Jun 17, 2015 at 4:33 AM, Anna Petrášová <kratochanna@gmail.com>
wrote:
Hi,
On Tue, Jun 16, 2015 at 9:42 AM, JanaKr <jkrajc@gmail.com> wrote:
Hello,
I imported a GMT multisegment ASCII file with contour lines using
v.in.ogr,
resulting in 3D vector file. 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.
I am sure contour_3d contains correct Z-values (I transformed it to
raster
to see).
Does anyone know what I am doing wrong, please?
nothing, it just was not implemented for lines, since 3D lines can have
vertices of different heights, but we can upload only one value. However,
since it makes perfectly sense for contours, I added the support for lines
there (r65493). Any chance you are using GRASS 7.1 (trunk) to try it out?
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?
Will this be backported to 7.0.x?
Thank you very much!
Best regards!
Pedro
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.
nothing, it just was not implemented for lines, since 3D lines can have vertices of different heights, but we can upload only one value. However, since it makes perfectly sense for contours, I added the support for lines there (r65493). Any chance you are using GRASS 7.1 (trunk) to try it out?
On Tue, Oct 20, 2015 at 6:41 PM, Pedro Venâncio <pedrongvenancio@gmail.com>
wrote:
Hi Anna,
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?
nothing, it just was not implemented for lines, since 3D lines can have
vertices of different heights, but we can upload only one value. However,
since it makes perfectly sense for contours, I added the support for lines
there (r65493). Any chance you are using GRASS 7.1 (trunk) to try it out?
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.
I believe I backported it, 7.0.2 RC1 release is just going on now, there will be an announcement soon.
Will this be backported to 7.0.x?
Then I wanted to transform the z-coordinate to
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?
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.
On Wed, Oct 21, 2015 at 4:15 AM, Pedro Venâncio <pedrongvenancio@gmail.com>
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.