Changes between Version 13 and Version 14 of Grass6Planning


Ignore:
Timestamp:
11/25/10 01:30:19 (14 years ago)
Author:
martinl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Grass6Planning

    v13 v14  
    4545 * v.out.ogr, r.out.gdal: datum transform parms saved to WKT
    4646 * [wiki:Release/6.4.0RC1-News 6.4.0RC1] (23 Dec 2008)
     47
     48==== HTML manual pages polishing ====
     49
     50The [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Fhtml64_user%2Ffull_index.html&spider=yes validator] reports faulty pages. Correct pages are also needed for a future [ticket:151 reST/Sphinx] conversion
     51
     52DONE:
     53
     54 * gis.m
     55 * d.colorlist
     56 * d.extend
     57 * d.nviz
     58 * d.profile
     59 * d.rast.arrow
     60 * db.execute
     61 * db.select
     62 * g.mkfontcap
     63 * g.proj
     64
     65TODO list (you may use validator [http://validator.w3.org/#validate_by_upload file upload]):
     66
     67 * d.graph
     68 * d.what.rast
     69 * g.region
     70 * wxGUI
     71
     72==== Wishlist ====
     73
     74 * 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.
     75
     76 * Implement [source:grass/grass_trunk/doc/vector/TODO vector improvements] as suggested by Radim
     77
     78 * Integrate [source:grass/grass-addons/imagery/i.points.auto/ i.points.auto] (merge into i.vpoints) - note that A Scianna/Palermo has modernized version
     79
     80 * Make sqlite the default DB? <- done for 7
     81
     82 * drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI)
     83  * 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
     84    * 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)
     85    *--HB: ok, d.m man page updated.
     86
     87 * raster maps: implement SQL based time series support (working code from Soeren in GRASS Addons)
     88
     89 * Clean up Makefile system to support extension compilation and installation outside the GRASS installation and without the full GRASS source.  Much like what GEM does, but without needing the module source setup and not limited to installing within the GRASS installation dir.  This could also simplify GEM on the compilation side. 
     90
     91===== Updates to vector querying =====
     92
     93 * v.select (query using a vector map):
     94  * add flags -p and -g for text output instead of creating a new map. It would report which map(s) and feature(s)/cat(s) meet the query criteria.
     95  * allow multiple maps to be selected. This would directly address Eric's question. If the output is a map, it would be the equivalent of v.patch on all queried vector elements.
     96  * add operators "contains" and "adjacent". Contains=all vector features whose nodes are completely inside a polygon (or inside or touching the boundary). Adjacent=all vector features who share a node/point or line/boundary with the selecting feature. Because GRASS is topologically correct, adjacency information is readily available.<BR>--HB: op="not" too please.
     97  * maybe change option names from ainput and binput to selector and selected or queried. This would have to wait until GRASS 7, of course. I find ainput and binput not very clear where used in other vector operations either (maybe I'm just dense).
     98   * --HB: input order counts, so named map options have a function.
     99
     100 * v.what (query using coordinates):
     101  * add flags -p and -g for current behavior (-pg could be the default if we wanted to do this before GRASS 7)
     102  * add "output=" option to allow v.what to create a new map from the results of its query, like v.select does
     103  * allow multiple maps for input, as with the suggestion for v.select
     104  * allow coordinates to be read optionally as a line or area boundary (-l or -a?) instead of only as individual points.
     105 * add operators overlap, contains, adjacent.(This also would make possible interactive vector selection with a mouse drawn box or polygon from the GUI)
     106
     107 * In other words, have v.select and v.what work the same except that v.select uses a vector map for querying and v.what uses a set of coordinate points.
     108
     109 * v.overlay (boolean combination of maps):
     110  * drop the ainput and binput. Replace with just input. --HB: careful, order of maps can matter.
     111  * allow multiple maps to be entered into input, not just 2
     112  * 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).
     113   * --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.
     114
     115===== In progress =====
     116
     117 * complete and further stabilize the native WinGRASS Current Status (seems to be in a good shape now)
     118
     119 * Database connection for v.out.vtk: -- User:Huhabla 20:47, 14 August 2006 (CEST)
     120  * single column support for numerical data (int, float, double)
     121  * GRASSRGB column support (done for ps.map)
     122  * multiple column support for vector data
     123 * rewrite most of the g3d modules to fulfill the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST)
     124 * adding further (organized) keywords to every GRASS command and script
     125 * continue with wxGUI
     126 * improve Python-SWIG interface
     127 * less verbose commands (work in progress)
     128 * BLAS/LAPACK updates (?)
     129 * Provide interactive environment on GRASS startup [http://wald.intevation.org/tracker/index.php?func=detail&aid=521&group_id=21&atid=205 #521]
     130 * [wiki:Release/6.4.0RC1-News 6.4.0RC1] (23 Dec 2008)