[GRASS-user] v.to.3d -r option not working properly

[Anna Petrášová]

Hi,

On Tue, Jun 16, 2015 at 9:42 AM, JanaKr <jkrajc at 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?

Anna


>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/v-to-3d-r-option-not-working-properly-tp5211241.html
> Sent from the Grass - Users mailing list archive at Nabble.com.
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20150616/4775acc0/attachment.html>