[GRASS-dev] 2D to 3D points
benjamin.ducke at ufg.uni-kiel.de
Sun Mar 2 15:40:25 EST 2008
As far as I am aware, the term "extrusion" is pretty well defined
as the operation of extending an object in 3D space by "pulling
it out" with a predefined bearing and length. This would convert a point
to a line, a line to a plane and a polygon to, well, a polygon with a
volume, I guess.
Personally, I'd be more in favour of wrapping a little script
"v.points.to.3d" around v.transform. For the beginners' sake.
Dylan Beaudette wrote:
> On Saturday 01 March 2008 10:20:45 pm Hamish wrote:
>> Benjamin Ducke wrote:
>>> 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.
>> So we make little wrapper scripts like v.dissolve and v.centroids.
>> That's much better than dealing with code duplication.
>> but that shouldn't wrap 3 module commands together with temporary maps
>> etc to perform something as simple as the 2d+attr column -> 3d points
>> conversion. If as Maciek suggests v.transform could do the job then
>> it's not so bad. The v.transform name even sounds right for the job.
> I agree that we should avoid code duplication at any cost, and v.transform
> does the job. However, doesn't it make more sense to put that code (for
> points) into v.extrude ? Or, is v.extrude primarily for areas by design?
Benjamin Ducke, M.A.
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
D 24098 Kiel
Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
More information about the grass-dev