Changes between Version 146 and Version 147 of Grass6Planning


Ignore:
Timestamp:
05/02/15 22:31:03 (10 years ago)
Author:
neteler
Comment:

cleanup

Legend:

Unmodified
Added
Removed
Modified

  • Grass6Planning

    v146 v147  
    5353
    5454 * modify Makefile system to support [ticket:846 translated HTML pages]. Store translated HTML files in centralized directory with locale specific subdirs, file name is module name.
    55 
    56  * Implement [source:grass/branches/releasebranch_6_4/doc/vector/TODO vector improvements] as suggested by Radim
    57 
    58  * Integrate [source:grass-addons/imagery/i.points.auto/ i.points.auto] (merge into i.vpoints) - note that A Scianna/Palermo has modernized version
    59 
    60  * Make sqlite the default DB? <- done for 7
    61 
    62  * drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
    63   * 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
    64     * 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 OBSOLETE?  -- MarisN 08:24, 16 February 2007 (CET)
    65     * --HB: ok, d.m man page updated.
    66 
    67  * raster maps: implement SQL based time series support <- done for 7
     55 * ~~Implement [source:grass/branches/releasebranch_6_4/doc/vector/TODO vector improvements] as suggested by Radim~~ <- done in GRASS GIS 7
     56 * ~~Make sqlite the default DB~~ <- done for 7
     57 * Integrate [source:grass-addons/imagery/i.points.auto/ i.points.auto] (merge into i.vpoints) - note that A Scianna/Palermo has modernized version - ???
     58 * ~~raster maps: implement SQL based time series support~~ <- done for 7
    6859
    6960=== Updates to vector querying ===
    … …  
    9081  * deprecate v.patch because v.overlay with the OR operator replaces it. (If we wanted to do this before GRASS 7, we'd have to create a new module, maybe named v.combine or something like that because this changes the default behavior of v.overlay).
    9182   * --HB: does it completely? I could be totally wrong, but my thought was that v.patch is very fast and does not attempt to clean (overlay) features, just lump them together in the file. Certainly for most tasks v.overlay should be the suggested route in the documentation.
    92 
    93 === In progress ===
    94 
    95  * Database connection for v.out.vtk: -- User:Huhabla 20:47, 14 August 2006 (CEST)
    96   * single column support for numerical data (int, float, double)
    97   * GRASSRGB column support (done for ps.map)
    98   * multiple column support for vector data
    99  * rewrite most of the g3d modules to fulfill the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST)
    100 
    10183
    10284----