Subject: improving v.digit
Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: grass63CVS
My name is Marco Rigotti and I'm writing as I wish the v.digit module to be improved.
v.digit has a severe handicap: it lacks an efficient editing tool. v.digit functionalities
would benefit to a high extent if we could allow the snap to work not only with
nodes but with all kind of vertexes. Furthermore if the mouse pointer changed
its shape (or colour) when pointing on any geometrical element, the user would
know in a far easier way when the snap is working or not.
Such improvements would help in making the v.digit easier to use and much more
complete than it is by now. At present, the v.digit module doesn't allow for
complex editing/digitising, forcing people to use other GIS softwares (Arcview,
Geomedia, ...) in order to achieve their objectives. |
|
guest wrote (Thu, Dec 21 2006 16:05:14):
Hi!
> v.digit functionalities would benefit to a high extent if we could allow the
> snap to work not only with nodes but with all kind of vertexes.
Why would you want to snap to vertices other than nodes, within a currently
edited vector? (FYI, node is a special case of vertex actually - a vertex on
an either end of a linear vector feauture, ie. a line or a boundary). Given
the *topological* model of GRASS vector format, I don't see any use for
snapping to vertices in the currently digitized vector.
However, it would certainly be nice if one could snap to vertices of a vector
displayed in the *background* - so that reproducing some particular shape or
a
feature location of it, in the currently edited vector, could be possible.
> Furthermore if the mouse pointer changed its shape (or colour) when pointing
> on any geometrical element, the user would know in a far easier way when the
> snap is working or not.
That would be usefull.
> Such improvements would help in making the v.digit easier to use and much
> more complete than it is by now. At present, the v.digit module doesn't
> allow for complex editing/digitising, forcing people to use other GIS
> softwares (Arcview, Geomedia, ...) in order to achieve their objectives.
Please note that v.digit compared to QGIS 0.8 GRASS Edit tool is much less
powerfull and more buggy. I'm using the GRASS Edit myself for serious vector
editing and I can accomplish all I need uisng it. Sad truth is that v.digit is
a complex tool and has no active maintainer currently, so it is unlikely to be
improved or seriously fixed soon. Currently a new native GRASS GUI, based on
wxPython, is in the making, which will include a completely new digitizing
tool. However, it might take months before a release candidate is published.
For now I recommend the QGIS 0.8 + GRASS Edit, or please join the wxPython
GRASS GUI development and give us a hand!
Maciek
|
|