GRASS 6.3 Feature Plan

GRASS 6.3.x feature plan

About feature plan

To make GRASS releases more often and more predictable, here is GRASS next releases feature plan. This feature plan has to be filled by developers working on GRASS 6.3.

Basic principles:

1. Add a short feature description, bug No., etc. what You want to see and what YOU will implement or fix in upcoming GRASS 6.3 to #TODO list. Sign it using four tildes ~~~~!
2. If You work on it, and You think it will make to next release, MOVE to #In progress section.
3. When You finish and commit Your work, MOVE it to #Finished section.

Warning After freeze start, You will not be able to commit any new features till freeze end. Only bugfixes and commits related to items listed in In progress section.

TODO

Must do

• complete and stabilize the native winGRASS port
• modify Makefile system to support translated HTML pages. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.

• replace r.proj with r.proj.seg; d.text with d.text.new

Mostly done?

• Create GRASS Addons SVN repository and really use GEM: GRASS Addons SVN is available now - contact Markus, see GRASS AddOns page
• Are there outstanding v.surf.idw versus v.surf.idw2 issues??

Wishlist

• Implement vector improvements as suggested by Radim
• Integrate i.points.auto (merge into i.vpoints) - see also Image processing
• Make sqlite the default DB?
• drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)

Some people still prefer it (see posts to grass-dev) and I will fix bugs in it, but not enhance/add new modules to it without good reason. So I don't see the need to drop it before the WxPython version is ready. It's not hurting us any keeping it. --Hamish

We should keep plain d.mon interface but why keep d.m, if gis.m has become really good? Probably we should clearly state, that d.m is UNMAINTAINED and OBSOLATED? MarisN 08:24, 16 February 2007 (CET)

• raster maps: implement SQL based time series support

In progress

• native MS Windows port
• Database connection for v.out.vtk: --huhabla 20:47, 14 August 2006 (CEST)
  • single column support for numerical data (int, float, double)
  • GRASSRGB column support
  • multiple column support for vector data
• rewrite most of the g3d modules to fulfil the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST)
• adding further (organized) keywords to every grass command and script [1] and [2]:
  • display commands
  • database commands
  • general commands
  • imagery commands
  • misc commands
  • paint commands
  • photo commands
  • postscript commands
  • raster commands
  • raster3D commands
  • vector commands
• continue with wxpython prototype
• write (Python based?) GUI wizard to create new locations (MN and terrestris.de)
• implement Python-SWIG interface
• less verbose commands

Finished

• All fixes as done for GRASS 6.2.x
• rewrite of r.to.rast3, r.to.rast3elev, v.out.vtk and r.out.vtk to fulfil the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST)
• basic keyword support added Neteler 15:52, 19 August 2006 (CEST)

User Wishes

This section is not really development related...

• Create 3D animation w nviz showing GRASS 3D coolness. MarisN 12:00, 4 August 2006 (CEST)
• here are some examples to get inspired (apparently that's already possible):
  • dynamic surfaces and volumes
  • some water
  • particles
  • solar radiation and energy
• Convince the users to use ParaView [3] for sophisticated animations --huhabla 20:47, 14 August 2006 (CEST)
  • (Add support for Paraview in GDAL/OGR or add GDAL/OGR support in ParaView to read directly data from GRASS) see diskussion
• Or use VisIt software, it should be able to read GRASS maps directly via GDAL