[GRASSweb-list]paul: web/announces announce_grass530.html,1.1,1.2

[grass at intevation.de]

Author: paul

Update of /grassrepository/web/announces
In directory doto:/tmp/cvs-serv21139

Modified Files:
	announce_grass530.html 
Log Message:
Further updates


Index: announce_grass530.html
===================================================================
RCS file: /grassrepository/web/announces/announce_grass530.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- announce_grass530.html	17 May 2004 16:15:43 -0000	1.1
+++ announce_grass530.html	21 May 2004 13:04:08 -0000	1.2
@@ -93,7 +93,8 @@
 <dd>Updates to the <em>nviz</em> 3-D visualisation tool include experimental loading
 and saving of 3d.view files from the GRASS database, off-screen rendering and
 implementation of many planned features for which 'stub' functionality only has
-existed up to now.</dd>
+existed up to now. In addition the new module <em>d.nviz</em> allows automated
+creation of fly-through animations in nviz.</dd>
 
 <dt><strong>Experimental LIDAR processing tools</strong><dt>
 <dd><em>s.bspline.reg</em>, <em>s.correction</em>, <em>s.edgedetection</em>, 
@@ -105,8 +106,70 @@
 <dt><strong>Experimental large-scale watershed computation</strong><dt>
 <dd><em>r.terraflow</em></dd>
 
-<dt><strong>Useful scripts</strong><dt>
-<dd></dd>
+<dt><strong>G3D 3-D Raster Voxel tools enabled</strong><dt>
+<dd>The 3-D raster processing tools are fully enabled in this release of
+GRASS. This includes the modules
+<em>g3.region</em>,
+<em>g3.list</em>,
+<em>g3.remove</em>,
+<em>g3.rename</em>,
+<em>g3.setregion</em>,
+<em>r3.colors</em>,
+<em>r3.in.ascii</em>,
+<em>r3.in.grid3</em>,
+<em>r3.in.v5d</em>,
+<em>r3.info</em>,
+<em>r3.mapcalc</em>,
+<em>r3.mask</em>,
+<em>r3.mkdspf</em>,
+<em>r3.null</em>,
+<em>r3.out.ascii</em>,
+<em>r3.out.v5d</em>,
+<em>r3.showdspf</em>,
+<em>r3.timestamp</em>, 
+<em>r3.to.sites</em>,
+<em>g3.createwind</em>,
+<em>s.to.rast3</em>,
+<em>s.vol.idw</em> and
+<em>s.vol.rst</em>
+</dd>
+
+<dt><strong>MATLAB import and export</strong><dt>
+<dd>GRASS can now import and export rasters from the MATLAB binary '.mat'
+format. The relevant modules are <em>r.in.mat</em> and <em>r.out.mat</em></dd>
+
+<dt><strong>Raster time series Statistical Analysis</strong><dt>
+<dd><em>r.series</em> can be used to create an output raster map where each 
+cell value is a statistical function (average, count, median, mode, minimum, 
+maximum, stddev, sum, variance, diversity, slope or offset)
+of the values of the corresponding cells in all the input raster maps.</dd>
+
+<dt><strong>Vis5D Output</strong><dt>
+<dd><em>r3.in.v5d</em> and <em>r3.out.v5d</em> already exist to allow data
+conversion between Vis5D and GRASS G3D format. Now in addition 2-D raster
+and vector data can be output to a Vis5D model (for further enhanced
+visualisation) using the new modules <em>r.out.v5d.topo</em> and
+<em>v.out.v5d.map</em>. <em>g.region.v5d</em> sets the region from a Vis5D
+file.</dd>
+
+<dt><strong>Other new modules</strong><dt>
+<dd>Miscellaneous new modules include 
+<em>d.info</em>,
+<em>s.kernel</em>,
+<em>r.texture</em>,
+<em>s.sv2svfit</em>,
+<em>d.sites.icons</em>,
+<em>d.out.png</em>,
+<em>d.3d.views</em>,
+<em>d.nviz</em>,
+<em>r.out.gdal</em>,
+<em>r.grow2</em>,
+<em>m.cogo</em>,
+<em>s.cellstats</em>,
+<em>r.univar2</em> and
+<em>i.tasscap.tm7</em>
+</dd>
+
 </dl>
 
 
@@ -120,9 +183,9 @@
 in the other. Even if datum transformation parameters were specified (e.g. dx, dy,
 dz) they were ignored and the NADCON tables used. In GRASS 5.3 any datum 
 transformation parameters present in the PROJ_INFO file will be used. These are 
-likely to be less accurate than the NADCON transformation (unless g.setproj is re-run
+likely to be less accurate than the NADCON transformation (unless <em>g.setproj</em> is re-run
 for the location and the NADCON parameters specifically selected). Many more
-datum transformation options are available in this release of GRASS and g.setproj
+datum transformation options are available in this release of GRASS and <em>g.setproj</em>
 should be re-run if in any doubt that the location is using the most up-to-date
 datum parameters.</p>