GRASS 7 ideas collection: Difference between revisions
Jump to navigation
Jump to search
⚠️Msieczka (talk | contribs) |
⚠️Msieczka (talk | contribs) |
||
| Line 16: | Line 16: | ||
* Remove [http://intevation.de/rt/webrt?serial_num=3600 doubled units in v.to.db GUI] | * Remove [http://intevation.de/rt/webrt?serial_num=3600 doubled units in v.to.db GUI] | ||
* Fix the [http://intevation.de/rt/webrt?serial_num=3623 Column 'cat_' already exists (duplicate name)] in v.in.ogr. Maybe by creating columns ''cat_1'', ''cat_2'' etc. each time a Grass vector is exported to shapefile and imported back to Grass? | |||
== General == | == General == | ||
Revision as of 12:59, 26 July 2006
Raster
Library
- Rewrite library from scratch
Modules
- Remove r.in.arc and r.out.arc, if a related bug in r.in.gdal is fixed. The integer/floating point detection for AAIGrid driver in GDAL was fixed after 1.3.2 release, so r.in.gdal and r.out.gdal should be enough now.
- Remove the code from r.info that makes it print projection information - we have g.region and g.proj for that. Moreover, r.info always prints a bogus (zone 0) information in non-UTM locations, which is confussing. See a bug report.
Vector
Library
Modules
- Remove doubled units in v.to.db GUI
- Fix the Column 'cat_' already exists (duplicate name) in v.in.ogr. Maybe by creating columns cat_1, cat_2 etc. each time a Grass vector is exported to shapefile and imported back to Grass?
General
Data management
- store vertical units on per-map base, using code from units software
- store vertical map datum on per-location base (GDAL/OGR needs the same enhancement)
Visualization
GUI
- Multiplatform
- Fast
- Small on monitor
- Number of window reduction
- Managable from command line via d.* modules (which will have to be rewritten too)
- Python?
- WxWidgets?