Difference between revisions of "GRASS Digitizing tool"

From GRASS-Wiki
Jump to: navigation, search
 
Line 1: Line 1:
=GRASS digitizing tool= should be
+
GRASS digitizing tool should be
 
* written in Python Programming language or Tcl
 
* written in Python Programming language or Tcl
 
* it should extend functionality of map display just like new Georeferencing tool does:
 
* it should extend functionality of map display just like new Georeferencing tool does:
Line 6: Line 6:
 
* There should be graphical tool for database management, at least for adding (?and removing?) columns, adding new features and editing existing ones.
 
* There should be graphical tool for database management, at least for adding (?and removing?) columns, adding new features and editing existing ones.
  
While digitising, edited vector file would be drawed to map display. ''Only currently edited or selected features would be stored in  
+
While digitising, edited vector file would be drawed to map display. ''Only currently edited or selected features would be stored in memory.'' This should spead up digitising and redrawing process significantly.
memory.'' This should spead up digitising and redrawing process significantly.
 
  
 
=v.edit=
 
=v.edit=

Revision as of 06:08, 7 December 2006

GRASS digitizing tool should be

  • written in Python Programming language or Tcl
  • it should extend functionality of map display just like new Georeferencing tool does:
    • (like ArcGIS does) only new "Digitizing Toolbox" would appear, after digitizing tool is started
    • Vector file editing will happen in current map display, with all it's functions for zooming, quering and so on
  • There should be graphical tool for database management, at least for adding (?and removing?) columns, adding new features and editing existing ones.

While digitising, edited vector file would be drawed to map display. Only currently edited or selected features would be stored in memory. This should spead up digitising and redrawing process significantly.

v.edit

GRASS graphical digitising tool should be graphical front-end for new v.edit module. v.edit should be CML tool for

  • adding new features (points, lines, polylines, centroids)
  • removenig old features (with database record)
  • moving whole feature
  • moving specified vertex
  • spliting new vertex between two existing ones
  • IMHO funtionality for adding 'z' values to vector contour lines should be back too

v.edit should accept feature selection by:

  • bbox
  • catlist
  • single coordinates