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. > > > Hamish >
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? Dylan -- Dylan Beaudette Soil Resource Laboratory http://casoilresource.lawr.ucdavis.edu/ University of California at Davis 530.754.7341 _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
