Difference between revisions of "GRASS Digitizing tool"

From GRASS-Wiki
Jump to: navigation, search
m (show new digitizer first)
 
(27 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=v.digit=
+
__TOC__
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.
+
== GUI vector digitizer ==
  
=v.edit=
+
=== New digitizer ===
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:
+
Quick overview:
* bbox
+
* Editing of vector objects:
* catlist
+
** Add, Break, Copy, Connect, Convert Type, Delete, Flip direction, Merge, Move, Select lines by query, Snap, Split
* single coordinates
+
* Cats:
 +
** Copy, Delete, Z-Bulk Labeling
 +
* Vertex:
 +
** Insert, Delete, Move
  
==v.edit input types==
+
* '''For details, see [[WxGUI#Vector_digitizer|Vector digitizer]] in [[wxGUI]]'''
v.edit should accept inputs in following formats (based on v.in.acii):
 
=== For adding new features===
 
* point
 
e.g.
 
x|y|z
 
10|20|30
 
* standard
 
e.g.
 
L 1
 
10 20 30
 
20 30 40
 
1
 
===For removing existing features===
 
* list of categories with specified separator
 
* coordinate pair
 
x,y
 
* bounding box
 
x1,y1,x2,y2
 
  
===For moving existing feature===
 
Feature identification like for removing existing featuer
 
* Dx,Dy
 
* new x,y of first node
 
  
===For breaking line===
+
[[Image:WxGUI-vdigit-win0.png|thumb|400px|center]]
* x,y
 
  
===For moving vertex===
+
=== Old digitizer ===
* identification by x,y
+
* TCL/TK-based old fashioned [http://grass.osgeo.org/grass63/manuals/html63_user/v.digit.html v.digit] module
* moving like moving of whole feature
+
* no longer maintained
 +
 
 +
[[Image:V digit tcltk.png|thumb|400px|center]]
 +
 
 +
== Command Line (CLI) vector digitizer ==
 +
 
 +
See manual page of {{cmd|v.edit}}.
 +
 
 +
== Raster digitizer ==
 +
 
 +
The {{cmd|r.in.poly}} ASCII format is almost the same as the standard vector ASCII format. So the new digitizer should be able to output for both, and then we have a replacement for {{cmd|r.digit}} too!
 +
 
 +
[[Category:Development]]
 +
[[Category:Vector]]

Latest revision as of 08:33, 8 October 2012

GUI vector digitizer

New digitizer

Quick overview:

  • Editing of vector objects:
    • Add, Break, Copy, Connect, Convert Type, Delete, Flip direction, Merge, Move, Select lines by query, Snap, Split
  • Cats:
    • Copy, Delete, Z-Bulk Labeling
  • Vertex:
    • Insert, Delete, Move


WxGUI-vdigit-win0.png

Old digitizer

  • TCL/TK-based old fashioned v.digit module
  • no longer maintained
V digit tcltk.png

Command Line (CLI) vector digitizer

See manual page of v.edit.

Raster digitizer

The r.in.poly ASCII format is almost the same as the standard vector ASCII format. So the new digitizer should be able to output for both, and then we have a replacement for r.digit too!