[GRASS5] Cleaning and merging v.in.dxf, v.in.dxf2

[David D Gray]

Michel Wurtz wrote:
> 
> David D Gray wrote:
> > I suggest v.in/out.mif as v.in/out.mapinfo is ambiguous and we might
> > want to reserve it for possible use in importing binary mapinfo in
> > future.
> 
> I agree with you. BTW, all import export program use the same
> naming convention : v.in.xxx or v.out.xxx with xxx = e00, mif, dxf, ...
> at the exception of shape (should we call them v.in.shp and
> v.out.shp instead of v.in.shape and v.out.shape ?)
> 
> --

Michel

Yes, for the sake of compatibility, using the conventional extension
makes it clearer from the outset. People not familiar with GRASS might
think v.*.shape and i.shape are related for example. I'm not sure that
this change should be made now in the stable branch as it might cause
more confusion, but maybe for the next minor release.

David

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'