[GRASS-SVN] r40455 - in grass/branches/releasebranch_6_4:
display/d.nviz display/drivers/HTMLMAP lib/init
raster/r.in.gdal raster/r.out.vtk raster/r.profile
raster/r.sun raster3d/r3.out.vtk scripts/r.tileset
vector/v.surf.idw vector/v.to.points
svn_grass at osgeo.org
svn_grass at osgeo.org
Fri Jan 15 09:57:27 EST 2010
Author: neteler
Date: 2010-01-15 09:57:25 -0500 (Fri, 15 Jan 2010)
New Revision: 40455
Modified:
grass/branches/releasebranch_6_4/display/d.nviz/description.html
grass/branches/releasebranch_6_4/display/drivers/HTMLMAP/description.html
grass/branches/releasebranch_6_4/lib/init/variables.html
grass/branches/releasebranch_6_4/raster/r.in.gdal/description.html
grass/branches/releasebranch_6_4/raster/r.out.vtk/description.html
grass/branches/releasebranch_6_4/raster/r.profile/description.html
grass/branches/releasebranch_6_4/raster/r.sun/description.html
grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html
grass/branches/releasebranch_6_4/scripts/r.tileset/description.html
grass/branches/releasebranch_6_4/vector/v.surf.idw/description.html
grass/branches/releasebranch_6_4/vector/v.to.points/description.html
Log:
Fix spelling errors (trac #872)
Modified: grass/branches/releasebranch_6_4/display/d.nviz/description.html
===================================================================
--- grass/branches/releasebranch_6_4/display/d.nviz/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/display/d.nviz/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -75,7 +75,7 @@
number 2000.
<DT><B>route</B>
-<DD>The comma seperated geographic coordinates for keyframe locations.
+<DD>The comma separated geographic coordinates for keyframe locations.
<DD>The interactive flag (<EM>-i</EM>) overrides this option.
</DL>
@@ -102,7 +102,7 @@
<p>
If the GRASS region is changed the <EM>d.nviz</EM> command must be re-run.
<p>
-The current GRASS region and the user supplied paramters are included
+The current GRASS region and the user supplied parameters are included
as a comment at the top of the output script. This information can be
used to easily re-create the animation.
<p>
Modified: grass/branches/releasebranch_6_4/display/drivers/HTMLMAP/description.html
===================================================================
--- grass/branches/releasebranch_6_4/display/drivers/HTMLMAP/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/display/drivers/HTMLMAP/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -92,7 +92,7 @@
</LI><BR>
<LI><B>GRASS_HTMLMAXPOINTS=n</B><BR>specifies the maximum number of
vertices included in a polygon's clickable area.
- The default is <tt>99</tt>. Some browsers can only accomodate polygons of
+ The default is <tt>99</tt>. Some browsers can only accommodate polygons of
100 vertices or less. The HTMLMAP driver automatically ensures that a
polygon is closed by making the last point the same as the first
point.</LI><BR>
Modified: grass/branches/releasebranch_6_4/lib/init/variables.html
===================================================================
--- grass/branches/releasebranch_6_4/lib/init/variables.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/lib/init/variables.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -480,7 +480,7 @@
This variable is automatically created
by <em><a href="g.parser.html">g.parser</a></em> so that the
<tt>--overwrite</tt> option will
- be inherited by dependant modules as the script runs. Setting either the
+ be inherited by dependent modules as the script runs. Setting either the
GRASS_OVERWRITE environment variable or the OVERWRITE gisenv variable detailed
below will cause maps with identical names to be overwritten.</dd>
@@ -496,7 +496,7 @@
</ul>
This variable is automatically created by <em><a href="g.parser.html">g.parser</a></em>
so that the <tt>--verbose</tt> or <tt>--quiet</tt> flags will be inherited
- by dependant modules as the script runs.</dd>
+ by dependent modules as the script runs.</dd>
<br>
<dt>GRASS_REGION</dt>
@@ -586,7 +586,7 @@
This variable is automatically created
by <em><a href="g.parser.html">g.parser</a></em> so that the
<tt>--overwrite</tt> option will
- be inherited by dependant modules as the script runs. Setting either the
+ be inherited by dependent modules as the script runs. Setting either the
GRASS_OVERWRITE environment variable or the OVERWRITE gisenv variable detailed
below will cause maps with identical names to be overwritten.</dd>
</dl>
Modified: grass/branches/releasebranch_6_4/raster/r.in.gdal/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.in.gdal/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/raster/r.in.gdal/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -120,7 +120,7 @@
<p>
-The <em>r.in.gdal</em> comand does support the following features, as long as
+The <em>r.in.gdal</em> command does support the following features, as long as
the underlying format driver supports it:
<p>
Modified: grass/branches/releasebranch_6_4/raster/r.out.vtk/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.out.vtk/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/raster/r.out.vtk/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -44,9 +44,9 @@
<em><a href="http://mayavi.sourceforge.net">MayaVi</a></em> which are based on VTK.
If you have a raster map with partly no data, use the threshold filter in paraview to
visualize the valid data. Just filter all data which is greater/lesser than the
-choosen null value in the VTK-ASCII file.
+chosen null value in the VTK-ASCII file.
<br>
-If elevation map is choosen, a polygonal grid is created with <i>quads</i>,
+If elevation map is chosen, a polygonal grid is created with <i>quads</i>,
but the user can choose also <i>triangle strips</i> or <i>vertices</i>.
These dataformats a documented at <em><a href="http://www.vtk.org">VTK Toolkit</a></em>.
<br>
Modified: grass/branches/releasebranch_6_4/raster/r.profile/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.profile/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/raster/r.profile/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -87,7 +87,7 @@
The advantage of this method is that the same profile points can be piped into
different GRASS rasters by changing the input parameter.
<p>
-With this method the coordinates must be given as space or tab seperated easting
+With this method the coordinates must be given as space or tab separated easting
and northing. Labels after these values are ignored.
<p>
Another example using d.where:
Modified: grass/branches/releasebranch_6_4/raster/r.sun/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster/r.sun/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/raster/r.sun/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -52,7 +52,7 @@
and defined projection/coordinate system (check it with the <a href="g.proj.html">
g.proj</a>
command). If you have undefined projection, (x,y) system, etc. then the latitude
-can be defined explicitely for large areas by input raster map <i>latin</i>
+can be defined explicitly for large areas by input raster map <i>latin</i>
with interpolated latitude values or, for smaller areas, a single region
latitude value <i>lat</i> can be used instead. All input raster maps must
be floating point (FCELL) raster maps. Null data in maps are excluded from
Modified: grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html
===================================================================
--- grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/raster3d/r3.out.vtk/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -20,7 +20,7 @@
<EM><A HREF="http://mayavi.sourceforge.net">MayaVi</A></EM> which are based on VTK.
If you have a 3D raster map with partly no data, use the threshold filter in paraview to
visualize the valid data. Just filter all data which is greater/lesser than the
-choosen null value in the VTK-ASCII file.
+chosen null value in the VTK-ASCII file.
<BR><BR>
The top and bottom region settings are expected in meters.
Modified: grass/branches/releasebranch_6_4/scripts/r.tileset/description.html
===================================================================
--- grass/branches/releasebranch_6_4/scripts/r.tileset/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/scripts/r.tileset/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -10,7 +10,7 @@
<H2>OUTPUT FORMAT</H2>
-Each tile is listed on a seperate line in the output. The lines are formatted as follows:
+Each tile is listed on a separate line in the output. The lines are formatted as follows:
<dl>
<dt>
@@ -19,7 +19,7 @@
</pre></div>
<dd>
-This is the default output format. It is the tile's minimum x coordinate, minimum y coordinate, maximum x coordinate, maximum y coordinate, width in cells, and height in cells seperated by the "|" character. The fields can be seperated by a different character by changing the fs option.
+This is the default output format. It is the tile's minimum x coordinate, minimum y coordinate, maximum x coordinate, maximum y coordinate, width in cells, and height in cells separated by the "|" character. The fields can be separated by a different character by changing the fs option.
<p>
@@ -52,7 +52,7 @@
<div class="code"><pre>
r.tileset sourceproj=+init=epsg:4326 maxrows=1024 maxcols=2048
</pre></div>
-<dd> Generates tiles in latitude longitude that cover the current region, each tile will be less than 1024 cells high and 2048 cells across. The bounds and sizes of tiles in the output are seperated by |
+<dd> Generates tiles in latitude longitude that cover the current region, each tile will be less than 1024 cells high and 2048 cells across. The bounds and sizes of tiles in the output are separated by |
<p>
Modified: grass/branches/releasebranch_6_4/vector/v.surf.idw/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/v.surf.idw/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/vector/v.surf.idw/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -48,7 +48,7 @@
<p>
If more than <EM>count</EM> points fall into one target raster cell,
the mean of all the site values will determine the cell value (unless
-the -n flag is specifed, in which case only the <EM>count</EM>
+the -n flag is specified, in which case only the <EM>count</EM>
points closest to the centre of the cell will be interpolated).</p>
<P>
Modified: grass/branches/releasebranch_6_4/vector/v.to.points/description.html
===================================================================
--- grass/branches/releasebranch_6_4/vector/v.to.points/description.html 2010-01-15 08:14:33 UTC (rev 40454)
+++ grass/branches/releasebranch_6_4/vector/v.to.points/description.html 2010-01-15 14:57:25 UTC (rev 40455)
@@ -36,7 +36,7 @@
adjoining polygons share a topological boundary, the boundary only
gets converted to points once.</li>
<li>
-If the <em>type</em> paramter is set to <em>area</em>, the boundary of
+If the <em>type</em> parameter is set to <em>area</em>, the boundary of
each area is converted to points <i>regardless</i> of whether or not
there is a topological boundary between adjacent areas. In other
words, the common boundary of two adjoining areas, for example, gets
More information about the grass-commit
mailing list