That should work but it may not exactly be easy to locate for a
novice user.
How about a little wrapper script for v.transform that simplifies
this action?
I am increasingly concerned about the number of, sometimes basic,
geoprocessing functions that are present in GRASS but "hidden"
in complex module options. Of course people can always mail to
this list but in the first place it will create frustration for
them and possible turn them away.
Benjamin
Maciej Sieczka wrote:
Michael Barton pisze:
It doesn't seem to. I think it makes columns from the points.
If the input is a 3d point it makes a vertical 3d line out of it (the
lines's 2d length = 0, 3d length = 0 + input 3d point's z). As the
manual says. It takes 2 additional commnads to extract the top node:
v.extrude input=pt output=pt3d_ln hcolumn=wys type=point layer=1
v.to.points -n input=pt3d_ln output=pt3d_pt type=line llayer=1
v.extract input=pts3d_pt output=pts3d_pt_top type=point layer=2 new=-1
where="along>0"
For tranforming 2d points into 3d directly there is v.transform I guess,
using 'table' and 'columns' option.
Maciek
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany
Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
