GRASS Digitizing tool: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→v.edit) |
||
Line 21: | Line 21: | ||
* catlist | * catlist | ||
* single coordinates | * single coordinates | ||
==v.edit input types== | |||
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=== | |||
* x,y | |||
===For moving vertex=== | |||
* identification by x,y | |||
* moving like moving of whole feature |
Revision as of 15:38, 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
v.edit input types
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
- x,y
For moving vertex
- identification by x,y
- moving like moving of whole feature