11 | | * no real plan to release, used as interim version between 7.x and 6.4 stable |
| 11 | * ... add issues here |
| 12 | |
| 13 | == Bugs to be fixed in GRASS GIS 6 == |
| 14 | |
| 15 | * Open bugs concerning [/report/16 GRASS 6] |
| 16 | |
| 17 | == Can do in GRASS GIS 6 == |
| 18 | |
| 19 | Merge in replacements from [browser:grass-addons Addons]: |
| 20 | |
| 21 | Modules to consider: |
| 22 | * '''v.pack''' |
| 23 | |
| 24 | == HTML manual pages polishing == |
| 25 | |
| 26 | The [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Ffull_index.html&spider=yes validator] reports faulty pages. Correct pages are also needed for a future [ticket:151 reST/Sphinx] conversion |
| 27 | |
| 28 | DONE: |
| 29 | |
| 30 | * gis.m |
| 31 | * d.colorlist |
| 32 | * d.extend |
| 33 | * d.nviz |
| 34 | * d.profile |
| 35 | * d.rast.arrow |
| 36 | * db.execute |
| 37 | * db.select |
| 38 | * g.mkfontcap |
| 39 | * g.proj |
| 40 | * d.what.rast |
| 41 | |
| 42 | TODO list (you may use validator [http://validator.w3.org/#validate_by_upload file upload], the `dillo` web browser also has a nice validator built in): |
| 43 | |
| 44 | * d.graph (needs dl around dd instruction list [fixed in devbr6]) [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Fd.graph.html validation report] |
| 45 | * g.region (doesn't like `div` inside a `dt` list) [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Fg.region.html validation report] |
| 46 | * wxGUI (missing ALT tags with `img src`) [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2FwxGUI.html validation report] |
| 47 | |
| 48 | == Wishlist == |
| 49 | |
| 50 | * 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. |
| 51 | |
| 52 | * Implement [source:grass/branches/releasebranch_6_4/doc/vector/TODO vector improvements] as suggested by Radim |
| 53 | |
| 54 | * Integrate [source:grass-addons/imagery/i.points.auto/ i.points.auto] (merge into i.vpoints) - note that A Scianna/Palermo has modernized version |
| 55 | |
| 56 | * Make sqlite the default DB? <- done for 7 |
| 57 | |
| 58 | * drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI) |
| 59 | * 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 |
| 60 | * 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) |
| 61 | * --HB: ok, d.m man page updated. |
| 62 | |
| 63 | * raster maps: implement SQL based time series support <- done for 7 |
| 64 | |
| 65 | === Updates to vector querying === |
| 66 | |
| 67 | * v.select (query using a vector map): |
| 68 | * 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. |
| 69 | * 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. |
| 70 | * 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. --HB: op="not" too please. |
| 71 | * 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). |
| 72 | * --HB: input order counts, so named map options have a function. |
| 73 | |
| 74 | * v.what (query using coordinates): |
| 75 | * add flags -p and -g for current behavior (-pg could be the default if we wanted to do this before GRASS 7) |
| 76 | * add "output=" option to allow v.what to create a new map from the results of its query, like v.select does |
| 77 | * allow multiple maps for input, as with the suggestion for v.select |
| 78 | * allow coordinates to be read optionally as a line or area boundary (-l or -a?) instead of only as individual points. |
| 79 | * add operators overlap, contains, adjacent.(This also would make possible interactive vector selection with a mouse drawn box or polygon from the GUI) |
| 80 | |
| 81 | * 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. |
| 82 | |
| 83 | * v.overlay (boolean combination of maps): |
| 84 | * drop the ainput and binput. Replace with just input. --HB: careful, order of maps can matter. |
| 85 | * allow multiple maps to be entered into input, not just 2 |
| 86 | * 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). |
| 87 | * --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. |
| 88 | |
| 89 | === In progress === |
| 90 | |
| 91 | * Database connection for v.out.vtk: -- User:Huhabla 20:47, 14 August 2006 (CEST) |
| 92 | * single column support for numerical data (int, float, double) |
| 93 | * GRASSRGB column support (done for ps.map) |
| 94 | * multiple column support for vector data |
| 95 | * rewrite most of the g3d modules to fulfill the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST) |
| 96 | |
| 97 | |
| 98 | ---- |
103 | | ==== Can do in GRASS GIS 6 ==== |
104 | | |
105 | | Merge in replacements from [browser:grass-addons Addons]: |
106 | | |
107 | | Modules to consider: |
108 | | * ~~'''v.pack''' |
109 | | |
110 | | ==== HTML manual pages polishing ==== |
111 | | |
112 | | The [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Ffull_index.html&spider=yes validator] reports faulty pages. Correct pages are also needed for a future [ticket:151 reST/Sphinx] conversion |
113 | | |
114 | | DONE: |
115 | | |
116 | | * gis.m |
117 | | * d.colorlist |
118 | | * d.extend |
119 | | * d.nviz |
120 | | * d.profile |
121 | | * d.rast.arrow |
122 | | * db.execute |
123 | | * db.select |
124 | | * g.mkfontcap |
125 | | * g.proj |
126 | | * d.what.rast |
127 | | |
128 | | TODO list (you may use validator [http://validator.w3.org/#validate_by_upload file upload], the `dillo` web browser also has a nice validator built in): |
129 | | |
130 | | * d.graph (needs dl around dd instruction list [fixed in devbr6]) [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Fd.graph.html validation report] |
131 | | * g.region (doesn't like `div` inside a `dt` list) [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2Fg.region.html validation report] |
132 | | * wxGUI (missing ALT tags with `img src`) [http://www.htmlhelp.com/cgi-bin/validate.cgi?url=http%3A%2F%2Fgrass.osgeo.org%2Fgrass64%2Fmanuals%2FwxGUI.html validation report] |
133 | | |
134 | | ==== Wishlist ==== |
135 | | |
136 | | * 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. |
137 | | |
138 | | * Implement [source:grass/branches/releasebranch_6_4/doc/vector/TODO vector improvements] as suggested by Radim |
139 | | |
140 | | * Integrate [source:grass-addons/imagery/i.points.auto/ i.points.auto] (merge into i.vpoints) - note that A Scianna/Palermo has modernized version |
141 | | |
142 | | * Make sqlite the default DB? <- done for 7 |
143 | | |
144 | | * drop d.m display manager (as now almost unmaintained; there is gis.m and/or a python based GUI) |
145 | | * 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 |
146 | | * 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) |
147 | | * --HB: ok, d.m man page updated. |
148 | | |
149 | | * raster maps: implement SQL based time series support <- done for 7 |
150 | | |
151 | | ===== Updates to vector querying ===== |
152 | | |
153 | | * v.select (query using a vector map): |
154 | | * 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. |
155 | | * 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. |
156 | | * 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. --HB: op="not" too please. |
157 | | * 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). |
158 | | * --HB: input order counts, so named map options have a function. |
159 | | |
160 | | * v.what (query using coordinates): |
161 | | * add flags -p and -g for current behavior (-pg could be the default if we wanted to do this before GRASS 7) |
162 | | * add "output=" option to allow v.what to create a new map from the results of its query, like v.select does |
163 | | * allow multiple maps for input, as with the suggestion for v.select |
164 | | * allow coordinates to be read optionally as a line or area boundary (-l or -a?) instead of only as individual points. |
165 | | * add operators overlap, contains, adjacent.(This also would make possible interactive vector selection with a mouse drawn box or polygon from the GUI) |
166 | | |
167 | | * 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. |
168 | | |
169 | | * v.overlay (boolean combination of maps): |
170 | | * drop the ainput and binput. Replace with just input. --HB: careful, order of maps can matter. |
171 | | * allow multiple maps to be entered into input, not just 2 |
172 | | * 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). |
173 | | * --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. |
174 | | |
175 | | ===== In progress ===== |
176 | | |
177 | | * Database connection for v.out.vtk: -- User:Huhabla 20:47, 14 August 2006 (CEST) |
178 | | * single column support for numerical data (int, float, double) |
179 | | * GRASSRGB column support (done for ps.map) |
180 | | * multiple column support for vector data |
181 | | * rewrite most of the g3d modules to fulfill the grass function naming convention --huhabla 20:47, 14 August 2006 (CEST) |
182 | | |
183 | | |