From ab90c5e5a9b668894da360fa97ffd4a51a38931e Mon Sep 17 00:00:00 2001 From: Markus Neteler Date: Tue, 17 Dec 2024 20:17:20 +0100 Subject: [PATCH] docs: various updates and text fixes in HTML for MD conversion (#4837) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This PR contains various HTML updates and textual fixes in preparation for the planned markdown conversion (see also #4748). For this PR, I have (briefly) reviewed all ~600 GRASS GIS manual pages by converting them to MD for a quality check, and then updated the original HTML files accordingly. Thus it is also a backport candidate for G84. Changes in detail: - adding missing intro sentences - added module name in the first sentence where missing - http -> https - selected URL updates for broken URLs - selected additions in "SEE ALSO" sections - fix suboptimal HTML formatting (flags, special names, ...) - add missing keywords on metapages - remove leftover `Last changed: $Date$` entries from CVS/SVN days - simplify selected `-
...` to `
  • ...` for improved MD conversion - replaced `...` with `...` For an easier review, the changes have been submitted in separate commits: - [x] **db**: 473b95bdb95d6ead5dd3af5ab9ea10397665bcb4 - [x] **display**: fca42daab0e81b369b42ff7921bb1a70f774c03d - [x] **doc**: e473bc85cf46af0a4b1a84e70ac26e5400dc1e2c - [x] **general**: 00930f566b386683c3d0b7c8e52a4658ea0339d8 - [x] **gui**: e9259cf7c89a4677b162fa44fa84cb63a586ead4 - [x] **imagery**: e700a7c93d4d04d4108f61a0857b784febe908f6, c888dba357797e59ad0d35fd6c1e5efd5d48f08e - [x] **lib**: 6da27ca26e6bc498d3d169a0de14e556e17b9508 - [x] **misc**: bfa7c0d95cdb3ea87af3c578664bd305bd8c29bb - [x] **raster**: 0c5ca83e88cc63df2e24f5cb47ae57648f793327 - [x] **raster3d**: 0c44c957869680fb52d1e09ea42ccbb65c5c2e6f - [x] **scripts**: e5bd68354ff26dc2f9f78cb705b34ffe0eec4dbe, 7b70b03c1e4d9e6f6775f554cd322545f19d0e21 - [x] **temporal**: a173a8f5b09ce2651e45eb5627732f39dc711cc2 - [x] **vector**: b5167faec4bddf99447131ca2151e3a63a085dd5 - [x] **visualization**: 81e97561d2b80c1917d01d2353aaf119fa811157 Extra changes: - [x] replaced `...` with `...` in 14841b2a91e41d18585e329f97ed32fdf42335fb - [x] dot product: replaced `.` with `·` f8ea2004d2b8b06c9293d41fbe27d6aee2c12044 - [x] review by @echoix: 16456855344da3bca75977fc33a04bd624cd9bbc and 6fd0a667f0e2a739db3bea43114a32b39e0b0702 - [x] `utils/g.html2man/htmltags.txt`: dropped outdated file (see instead `utils/g.html2man/ggroff.py`) in 92597b258ffd83c8b19473c183d0a469681bee6f Co-authored-by: Edouard Choinière <27212526+echoix@users.noreply.github.com> --- db/databaseintro.html | 2 +- db/db.connect/db.connect.html | 2 +- db/db.execute/db.execute.html | 2 +- db/db.login/db.login.html | 4 +- db/drivers/ogr/README | 2 +- db/drivers/postgres/README | 4 +- db/drivers/postgres/grass-pg.html | 14 +-- db/drivers/sqlite/grass-sqlite.html | 4 +- display/d.extract/d.extract.html | 2 +- display/d.graph/d.graph.html | 6 +- display/d.grid/d.grid.html | 2 +- display/d.his/d.his.html | 4 + display/d.labels/d.labels.html | 2 +- display/d.legend.vect/d.legend.vect.html | 2 +- display/d.linegraph/d.linegraph.html | 4 +- display/d.mon/d.mon.html | 8 +- display/d.path/d.path.html | 2 +- display/d.profile/d.profile.html | 2 +- display/d.rast.arrow/d.rast.arrow.html | 4 +- display/d.rast.num/d.rast.num.html | 3 +- display/d.rgb/d.rgb.html | 3 + display/d.title/d.title.html | 25 ++-- display/d.vect.thematic/d.vect.thematic.html | 4 +- display/d.vect/d.vect.html | 10 +- display/displaydrivers.html | 2 +- .../legal_aspects_of_code_contributions.md | 2 +- doc/projectionintro.html | 4 +- general/g.filename/g.filename.html | 2 +- general/g.findfile/g.findfile.html | 2 +- general/g.gisenv/g.gisenv.html | 9 +- general/g.gui/g.gui.html | 10 +- general/g.list/g.list.html | 6 +- general/g.mapset/g.mapset.html | 2 +- general/g.mapsets/g.mapsets.html | 11 +- general/g.message/g.message.html | 37 +++--- general/g.mkfontcap/g.mkfontcap.html | 8 +- general/g.parser/g.parser.html | 40 +++---- general/g.proj/g.proj.html | 60 +++++----- general/g.region/g.region.html | 88 +++++++------- general/g.remove/g.remove.html | 10 +- general/g.setproj/g.setproj.html | 6 +- general/g.tempfile/g.tempfile.html | 21 ++-- general/g.version/g.version.html | 10 +- gui/wxpython/dbmgr/g.gui.dbmgr.html | 2 +- gui/wxpython/docs/wxGUI.components.html | 13 +++ gui/wxpython/docs/wxGUI.html | 14 +-- gui/wxpython/docs/wxGUI.iscatt.html | 8 +- gui/wxpython/docs/wxGUI.modules.html | 7 +- gui/wxpython/docs/wxGUI.nviz.html | 4 +- gui/wxpython/docs/wxGUI.toolboxes.html | 45 ++++---- gui/wxpython/docs/wxGUI.vnet.html | 2 +- gui/wxpython/gmodeler/g.gui.gmodeler.html | 44 +++---- gui/wxpython/mapswipe/g.gui.mapswipe.html | 4 +- gui/wxpython/rlisetup/g.gui.rlisetup.html | 12 +- gui/wxpython/vdigit/g.gui.vdigit.html | 2 +- imagery/i.aster.toar/i.aster.toar.html | 2 +- imagery/i.atcorr/i.atcorr.html | 42 +++---- imagery/i.eb.netrad/i.eb.netrad.html | 2 +- imagery/i.landsat.acca/i.landsat.acca.html | 10 +- imagery/i.landsat.toar/i.landsat.toar.html | 2 +- imagery/i.modis.qc/i.modis.qc.html | 4 +- .../i.ortho.elev/i.ortho.elev.html | 10 +- .../i.ortho.transform/i.ortho.transform.html | 2 +- imagery/i.rectify/i.rectify.html | 8 +- imagery/i.segment/i.segment.html | 13 ++- imagery/i.svm.predict/i.svm.predict.html | 7 +- imagery/i.svm.train/i.svm.train.html | 7 +- imagery/i.vi/i.vi.html | 4 +- imagery/imageryintro.html | 6 +- lib/cairodriver/cairodriver.html | 14 +-- lib/db/sqlp/sql.html | 12 +- lib/htmldriver/htmldriver.html | 16 +-- lib/init/grass.html | 52 ++++----- lib/init/variables.html | 108 +++++++++--------- lib/pngdriver/pngdriver.html | 14 +-- lib/psdriver/psdriver.html | 12 +- lib/vector/rtree/docs/sources.htm | 2 +- lib/vector/vectorascii.html | 21 ++-- macosx/ReadMe.md | 4 +- macosx/pkg/resources/ReadMe.rtf | 4 +- misc/m.cogo/m.cogo.html | 4 +- misc/m.transform/m.transform.html | 22 ++-- ps/ps.map/ps.map.html | 62 +++++----- python/grass/docs/src/gunittest_testing.rst | 2 +- raster/r.buffer/r.buffer.html | 4 +- raster/r.buildvrt/r.buildvrt.html | 4 +- raster/r.carve/r.carve.html | 2 +- raster/r.category/r.category.html | 34 +++--- raster/r.circle/r.circle.html | 2 +- raster/r.coin/r.coin.html | 23 ++-- raster/r.colors/r.colors.html | 8 +- raster/r.colors/r3.colors.html | 2 +- raster/r.compress/r.compress.html | 46 ++++---- raster/r.cost/r.cost.html | 8 +- raster/r.covar/r.covar.html | 4 +- raster/r.describe/r.describe.html | 23 ++-- raster/r.fill.stats/r.fill.stats.html | 12 +- raster/r.flow/r.flow.html | 4 +- raster/r.geomorphon/r.geomorphon.html | 5 +- raster/r.gwflow/r.gwflow.html | 4 +- raster/r.his/r.his.html | 2 +- raster/r.horizon/r.horizon.html | 10 +- raster/r.in.ascii/r.in.ascii.html | 2 +- raster/r.in.bin/r.in.bin.html | 2 +- raster/r.in.gdal/r.in.gdal.html | 25 ++-- raster/r.in.lidar/r.in.lidar.html | 42 +++---- raster/r.in.mat/r.in.mat.html | 12 +- raster/r.in.pdal/r.in.pdal.html | 34 +++--- raster/r.in.poly/r.in.poly.html | 8 +- raster/r.in.xyz/r.in.xyz.html | 26 ++--- raster/r.info/r.info.html | 4 +- raster/r.lake/r.lake.html | 8 +- raster/r.li/r.li.cwed/r.li.cwed.html | 8 +- raster/r.li/r.li.daemon/r.li.daemon.html | 2 +- .../r.li/r.li.dominance/r.li.dominance.html | 8 +- .../r.li.edgedensity/r.li.edgedensity.html | 12 +- raster/r.li/r.li.html | 12 +- raster/r.li/r.li.mpa/r.li.mpa.html | 8 +- raster/r.li/r.li.mps/r.li.mps.html | 6 +- raster/r.li/r.li.padcv/r.li.padcv.html | 6 +- raster/r.li/r.li.padrange/r.li.padrange.html | 6 +- raster/r.li/r.li.padsd/r.li.padsd.html | 6 +- .../r.li.patchdensity/r.li.patchdensity.html | 6 +- raster/r.li/r.li.patchnum/r.li.patchnum.html | 6 +- raster/r.li/r.li.pielou/r.li.pielou.html | 8 +- raster/r.li/r.li.renyi/r.li.renyi.html | 8 +- raster/r.li/r.li.richness/r.li.richness.html | 8 +- raster/r.li/r.li.shannon/r.li.shannon.html | 8 +- raster/r.li/r.li.shape/r.li.shape.html | 6 +- raster/r.li/r.li.simpson/r.li.simpson.html | 8 +- raster/r.mapcalc/r.mapcalc.html | 34 +++--- raster/r.mapcalc/r3.mapcalc.html | 16 +-- raster/r.null/r.null.html | 2 +- .../r.object.geometry/r.object.geometry.html | 6 +- raster/r.out.bin/r.out.bin.html | 2 +- raster/r.out.gdal/r.out.gdal.html | 24 ++-- raster/r.out.mat/r.out.mat.html | 4 +- raster/r.out.mpeg/r.out.mpeg.html | 4 +- raster/r.out.png/r.out.png.html | 2 +- raster/r.out.pov/r.out.pov.html | 2 +- raster/r.out.ppm/r.out.ppm.html | 8 +- raster/r.out.vrml/r.out.vrml.html | 8 +- raster/r.out.vtk/r.out.vtk.html | 12 +- raster/r.out.vtk/writeascii.c | 2 +- raster/r.patch/r.patch.html | 4 +- raster/r.profile/r.profile.html | 2 +- raster/r.proj/r.proj.html | 10 +- raster/r.quant/r.quant.html | 32 ++++-- raster/r.random.surface/r.random.surface.html | 2 +- raster/r.reclass/r.reclass.html | 6 +- raster/r.region/r.region.html | 2 +- raster/r.ros/r.ros.html | 16 +-- .../r.series.accumulate.html | 2 +- raster/r.series/r.series.html | 2 +- raster/r.slope.aspect/r.slope.aspect.html | 3 +- raster/r.spread/r.spread.html | 4 +- raster/r.stats.quantile/r.stats.quantile.html | 4 +- raster/r.stats.zonal/r.stats.zonal.html | 4 +- raster/r.stream.extract/r.stream.extract.html | 16 +-- raster/r.sun/r.sun.html | 4 +- raster/r.support/r.support.html | 2 +- raster/r.surf.area/r.surf.area.html | 18 +-- raster/r.surf.gauss/r.surf.gauss.html | 2 +- raster/r.texture/r.texture.html | 2 +- raster/r.timestamp/r.timestamp.html | 2 +- raster/r.to.rast3/r.to.rast3.html | 3 +- raster/r.to.rast3elev/r.to.rast3elev.html | 4 +- raster/r.topidx/r.topidx.html | 16 +-- raster/r.transect/r.transect.html | 2 +- raster/r.univar/r.univar.html | 6 +- raster/r.viewshed/r.viewshed.html | 12 +- raster/r.volume/r.volume.html | 14 +-- raster/r.walk/r.walk.html | 6 +- raster/r.watershed/front/r.watershed.html | 24 ++-- raster/r.what.color/r.what.color.html | 6 +- raster/r.what/r.what.html | 10 +- raster/rasterintro.html | 10 +- raster3d/r3.cross.rast/r3.cross.rast.html | 2 +- raster3d/r3.flow/r3.flow.html | 2 +- raster3d/r3.gradient/r3.gradient.html | 2 +- raster3d/r3.in.lidar/r3.in.lidar.html | 10 +- raster3d/r3.in.v5d/r3.in.v5d.html | 2 +- raster3d/r3.mask/r3.mask.html | 11 +- raster3d/r3.null/r3.null.html | 2 +- raster3d/r3.out.netcdf/r3.out.netcdf.html | 4 +- raster3d/r3.out.v5d/r3.out.v5d.html | 2 +- raster3d/r3.out.vtk/r3.out.vtk.html | 6 +- raster3d/r3.showdspf/r3.showdspf.html | 24 ++-- .../r3.showdspf/r3.showdspf_opengl_mods.html | 16 +-- raster3d/r3.support/r3.support.html | 2 +- raster3d/r3.to.rast/r3.to.rast.html | 6 +- raster3d/raster3dintro.html | 8 +- scripts/d.correlate/d.correlate.html | 2 +- scripts/d.out.file/d.out.file.html | 2 +- scripts/d.rast.leg/d.rast.leg.html | 2 +- scripts/d.shade/d.shade.html | 6 +- scripts/d.to.rast/d.to.rast.html | 2 +- scripts/d.what.rast/d.what.rast.html | 4 +- scripts/d.what.vect/d.what.vect.html | 4 +- scripts/db.droptable/db.droptable.html | 2 +- scripts/db.in.ogr/db.in.ogr.html | 4 +- scripts/db.test/db.test.html | 3 +- scripts/g.extension.all/g.extension.all.html | 6 +- scripts/g.extension/g.extension.html | 18 +-- .../r.plus.example/r.plus.example.html | 2 +- scripts/g.manual/g.manual.html | 2 +- scripts/i.band.library/i.band.library.html | 12 +- scripts/i.in.spotvgt/i.in.spotvgt.html | 2 + scripts/i.oif/i.oif.html | 2 +- scripts/i.pansharpen/i.pansharpen.html | 36 +++--- scripts/i.tasscap/i.tasscap.html | 3 +- scripts/i.tasscap/i.tasscap.py | 2 +- scripts/m.proj/m.proj.html | 40 +++---- scripts/r.fillnulls/r.fillnulls.html | 4 +- scripts/r.import/r.import.html | 6 +- scripts/r.in.srtm/r.in.srtm.html | 9 +- scripts/r.in.wms/r.in.wms.html | 24 ++-- .../r.mapcalc.simple/r.mapcalc.simple.html | 4 +- scripts/r.mask/r.mask.html | 10 +- scripts/r.out.xyz/r.out.xyz.html | 2 +- scripts/r.plane/r.plane.html | 2 +- scripts/r.shade/r.shade.html | 8 +- scripts/r.tileset/r.tileset.html | 25 ++-- scripts/r3.in.xyz/r3.in.xyz.html | 4 +- .../v.db.reconnect.all.html | 10 +- scripts/v.dissolve/v.dissolve.html | 2 +- scripts/v.import/v.import.html | 8 +- scripts/v.in.geonames/v.in.geonames.html | 14 +-- scripts/v.in.geonames/v.in.geonames.py | 12 +- scripts/v.in.lines/v.in.lines.html | 2 +- scripts/v.in.mapgen/v.in.mapgen.html | 4 +- scripts/v.in.wfs/v.in.wfs.html | 2 +- scripts/v.rast.stats/v.rast.stats.html | 6 +- scripts/v.what.vect/v.what.vect.html | 2 +- temporal/t.connect/t.connect.html | 2 +- temporal/t.copy/t.copy.html | 7 +- temporal/t.merge/t.merge.html | 4 +- temporal/t.rast.algebra/t.rast.algebra.html | 2 +- temporal/t.rast.extract/t.rast.extract.html | 2 +- temporal/t.rast.mapcalc/t.rast.mapcalc.html | 4 +- temporal/t.rast.out.vtk/t.rast.out.vtk.html | 2 +- temporal/t.rast.univar/t.rast.univar.html | 4 +- .../t.rast3d.algebra/t.rast3d.algebra.html | 4 +- temporal/t.rast3d.univar/t.rast3d.univar.html | 4 +- temporal/t.register/t.register.html | 4 +- temporal/t.remove/t.remove.html | 14 +-- temporal/t.rename/t.rename.html | 7 +- temporal/t.sample/t.sample.html | 2 +- temporal/t.select/t.select.html | 4 +- temporal/t.support/t.support.html | 3 +- temporal/t.unregister/t.unregister.html | 4 +- temporal/t.upgrade/t.upgrade.html | 4 +- temporal/t.vect.algebra/t.vect.algebra.html | 2 +- temporal/t.vect.extract/t.vect.extract.html | 2 +- temporal/t.vect.list/t.vect.list.html | 2 +- .../t.vect.observe.strds.html | 2 +- utils/g.html2man/htmltags.txt | 28 ----- vector/v.buffer/v.buffer.html | 2 +- vector/v.build/v.build.html | 3 +- vector/v.cluster/v.cluster.html | 13 ++- vector/v.colors/v.colors.html | 10 +- vector/v.db.select/v.db.select.html | 14 +-- vector/v.decimate/v.decimate.html | 2 +- vector/v.delaunay/v.delaunay.html | 2 + vector/v.distance/v.distance.html | 6 +- vector/v.edit/v.edit.html | 4 +- vector/v.external.out/v.external.out.html | 64 +++++------ vector/v.external/v.external.html | 8 +- vector/v.in.ascii/v.in.ascii.html | 20 ++-- vector/v.in.lidar/v.in.lidar.html | 30 +++-- vector/v.in.ogr/v.in.ogr.html | 22 ++-- vector/v.in.pdal/v.in.pdal.html | 4 +- vector/v.label/v.label.html | 24 ++-- .../v.lidar.correction.html | 2 +- .../v.lidar.edgedetection.html | 2 +- vector/v.lidar.growing/v.lidar.growing.html | 2 +- vector/v.lrs/lrs.html | 16 +-- vector/v.lrs/v.lrs.create/v.lrs.create.html | 2 +- vector/v.lrs/v.lrs.label/v.lrs.label.html | 2 +- vector/v.lrs/v.lrs.segment/v.lrs.segment.html | 4 +- vector/v.lrs/v.lrs.where/v.lrs.where.html | 2 +- vector/v.mkgrid/v.mkgrid.html | 4 +- vector/v.net.path/v.net.path.html | 26 ++--- vector/v.net/v.net.html | 6 +- vector/v.out.ascii/v.out.ascii.html | 8 +- vector/v.out.dxf/v.out.dxf.html | 2 +- vector/v.out.lidar/v.out.lidar.html | 6 +- vector/v.out.ogr/v.out.ogr.html | 22 ++-- vector/v.out.postgis/v.out.postgis.html | 64 +++++------ vector/v.out.vtk/v.out.vtk.html | 6 +- vector/v.proj/v.proj.html | 4 +- vector/v.random/v.random.html | 2 +- vector/v.reclass/v.reclass.html | 4 +- vector/v.segment/v.segment.html | 4 +- vector/v.select/v.select.html | 2 +- vector/v.support/v.support.html | 4 +- vector/v.to.db/v.to.db.html | 4 +- vector/v.to.rast/v.to.rast.html | 2 +- vector/v.to.rast3/v.to.rast3.html | 2 +- vector/v.voronoi/v.voronoi.html | 2 + vector/v.what.rast/v.what.rast.html | 8 +- visualization/ximgview/ximgview.html | 10 +- 302 files changed, 1498 insertions(+), 1424 deletions(-) delete mode 100644 utils/g.html2man/htmltags.txt diff --git a/db/databaseintro.html b/db/databaseintro.html index c400ab6e0ed..f7fb11a3b47 100644 --- a/db/databaseintro.html +++ b/db/databaseintro.html @@ -35,7 +35,7 @@

    Attribute data import and export

    Further conversion tools: diff --git a/db/db.connect/db.connect.html b/db/db.connect/db.connect.html index 434124b4e65..5b6e2fa1517 100644 --- a/db/db.connect/db.connect.html +++ b/db/db.connect/db.connect.html @@ -9,7 +9,7 @@

    DESCRIPTION

    NOTES

    -Values are stored in the mapset's VAR file; +Values are stored in the mapset's VAR file; the connection is not tested for validity.

    The -p flag will display the current connection parameters.

    The -c flag will silently check if the connection parameters have diff --git a/db/db.execute/db.execute.html b/db/db.execute/db.execute.html index b8fcce41d7b..08d5b10ae54 100644 --- a/db/db.execute/db.execute.html +++ b/db/db.execute/db.execute.html @@ -76,7 +76,7 @@

    EXAMPLES

    Update attribute with multiple SQL instructions in file -(e.g., file.sql, instruction line must end with a semicolon): +(e.g., file.sql, instruction line must end with a semicolon): 
     UPDATE roads SET travelcost=5 WHERE cat=1;
 UPDATE roads SET travelcost=2 WHERE cat=2;
diff --git a/db/db.login/db.login.html b/db/db.login/db.login.html
index 7173f2c044c..6f2eb652e4b 100644
--- a/db/db.login/db.login.html
+++ b/db/db.login/db.login.html
@@ -15,8 +15,8 @@ 
    NOTE
    
 file in the user account, specifically
 
 
      
-
    •  in the 'home' directory, i.e. $HOME/.grass8/dblogin (Unix-like systems)
      • 
-
    •  %APPDATA%\Roaming\GRASS8\dblogin (MS-Windows)
      • 
+
    •  in the 'home' directory, i.e. $HOME/.grass8/dblogin (Unix-like systems)
      • 
+
    •  %APPDATA%\Roaming\GRASS8\dblogin (MS-Windows)
      • 
 
    
 
 Only the file owner can access this file.
diff --git a/db/drivers/ogr/README b/db/drivers/ogr/README
index b5fa80bb25e..fde41d85722 100644
--- a/db/drivers/ogr/README
+++ b/db/drivers/ogr/README
@@ -5,4 +5,4 @@ SQL DB support via OGR
 
 -----------------------------------------------------
 General Documentation
-  http://www.remotesensing.org/gdal/ogr/ogr_sql.html
+  https://gdal.org/en/stable/user/ogr_sql_dialect.html
diff --git a/db/drivers/postgres/README b/db/drivers/postgres/README
index a2959739f6e..76d44e6bf6b 100644
--- a/db/drivers/postgres/README
+++ b/db/drivers/postgres/README
@@ -10,7 +10,7 @@ by G_warning().
 
 FIELD TYPES:
 Field type code may change. See for example
-http://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/include/catalog/pg_type.h;hb=refs/heads/master
+https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/include/catalog/pg_type.h;hb=refs/heads/master
 
 Because of this, type codes must be read from server when database is opened.
 
@@ -19,7 +19,7 @@ Check also for PostgreSQL data types for defining them in GRASS:
 
 
 Supported types in ./globals.h:
-(See https://www.postgresql.org/docs/9.4/interactive/datatype.html)
+(See https://www.postgresql.org/docs/current/datatype.html)
 
 DB_C_TYPE_INT:
 bit, int2, smallint, int4, int, integer, int8, bigint, serial, oid
diff --git a/db/drivers/postgres/grass-pg.html b/db/drivers/postgres/grass-pg.html
index 3950c0dd315..721d9a035b0 100644
--- a/db/drivers/postgres/grass-pg.html
+++ b/db/drivers/postgres/grass-pg.html
@@ -5,7 +5,7 @@
 
 
    Creating a PostgreSQL database
    
 
-A new database is created with createdb, see
+A new database is created with createdb, see
 the PostgreSQL
 manual for details.
 
@@ -76,7 +76,7 @@ 
    Geometry import from PostgreSQL table into GRASS
    
 
 
    PostGIS: PostgreSQL with vector geometry
    
 
-PostGIS:
+PostGIS:
 adds geographic object support to PostgreSQL.
 
 
    Example: Import from PostGIS
    
@@ -114,15 +114,15 @@ 
    Example: Import from PostGIS
    
 
 
    Geometry Converters
    
 
      
-
    • PostGIS with shp2pgsql:
      
- shp2pgsql -D lakespy2 lakespy2 test > lakespy2.sql
+
    • PostGIS with shp2pgsql:
      
+ shp2pgsql -D lakespy2 lakespy2 test > lakespy2.sql
 
      • 
-
    • e00pg: E00 to PostGIS filter,
+
    • e00pg: E00 to PostGIS filter,
 see also v.in.e00.
 
      • 
 
    • GDAL/OGR ogrinfo and ogr2ogr:
 GIS vector format converter and library, e.g. ArcInfo or SHAPE to PostGIS.
      
-  ogr2ogr -f "PostgreSQL" shapefile ??
+  ogr2ogr -f "PostgreSQL" shapefile ??
 
      • 
 
    
 
@@ -143,6 +143,6 @@ 
    REFERENCES
    
 
diff --git a/db/drivers/sqlite/grass-sqlite.html b/db/drivers/sqlite/grass-sqlite.html
index ea2f9526506..57808ccb79c 100644
--- a/db/drivers/sqlite/grass-sqlite.html
+++ b/db/drivers/sqlite/grass-sqlite.html
@@ -34,7 +34,7 @@ 
    Operators available in conditions
    
 
 
    Browsing table data in DB
    
 
-A convenient SQLite front-end is sqlitebrowser.
+A convenient SQLite front-end is sqlitebrowser.
 To open a DB file stored within the current mapset,
 the following way is suggested (corresponds to above database connection):
 
@@ -78,5 +78,5 @@ 
    SEE ALSO
    
 
   SQLite web site,
   SQLite manual,
-  sqlite - Management Tools
+  sqlite - Management Tools
 
diff --git a/display/d.extract/d.extract.html b/display/d.extract/d.extract.html
index 39c37915ade..9e09ddadc03 100644
--- a/display/d.extract/d.extract.html
+++ b/display/d.extract/d.extract.html
@@ -6,7 +6,7 @@ 
    DESCRIPTION
    
 
 
    EXAMPLE
    
 
-
    Graphically extract roads from a roads map:
    
+
    Graphically extract roads from a roads map
    
 
     d.mon x0
 d.vect roads
diff --git a/display/d.graph/d.graph.html b/display/d.graph/d.graph.html
index d70530f5da1..34017d34bc7 100644
--- a/display/d.graph/d.graph.html
+++ b/display/d.graph/d.graph.html
@@ -132,10 +132,10 @@ 
    COMMANDS
    
 
    symbol type size xper yper [line_color [fill_color]]
    
 
    A symbol is drawn at the given size on the display monitor. The
 xper and yper options define the center of the icon and
-are given as a percentage of the display frame (0,0 is lower left).
-The symbol can be any of those stored in $GISBASE/etc/symbol/
+are given as a percentage of the display frame (0,0 is lower left).
+The symbol can be any of those stored in $GISBASE/etc/symbol/
 (e.g. basic/circle) or stored in the user's mapset directory in the
-form $MAPSET/symbol/type/name.
+form $MAPSET/symbol/type/name.
 The colors may be either a standard color name, an R:G:B triplet,
 or "none". If using an R:G:B triplet, each color value can range from 0-255.
 If not specified the default line_color is black and the default
diff --git a/display/d.grid/d.grid.html b/display/d.grid/d.grid.html
index 7d775d71bc7..412a6a413ca 100644
--- a/display/d.grid/d.grid.html
+++ b/display/d.grid/d.grid.html
@@ -9,7 +9,7 @@ 
    DESCRIPTION
    
 If the user provides a -g flag a geographic (projected) grid
 will be drawn. With the -g flag the size
 argument accepts both decimal degrees and colon separated
-ddd:mm:ss coordinates (eg. 00:30:00 for half of a degree).
+ddd:mm:ss coordinates (eg. 00:30:00 for half of a degree).
 A geographic grid cannot be drawn for a latitude/longitude
 or XY projection.
 
diff --git a/display/d.his/d.his.html b/display/d.his/d.his.html
index 56f7d99bebc..49909d20d04 100644
--- a/display/d.his/d.his.html
+++ b/display/d.his/d.his.html
@@ -1,5 +1,9 @@
 
    DESCRIPTION
    
 
+d.his displays the result obtained by combining hue,
+intensity, and saturation (HIS) values from user-specified input
+raster map layers.
+
    
 HIS stands for hue, intensity, and saturation.
 This program produces a raster map layer providing a
 visually pleasing combination of hue, intensity, and
diff --git a/display/d.labels/d.labels.html b/display/d.labels/d.labels.html
index 61a9f94052e..0bcf9b07c57 100644
--- a/display/d.labels/d.labels.html
+++ b/display/d.labels/d.labels.html
@@ -7,7 +7,7 @@ 
    DESCRIPTION
    
 the v.label program or simply created
 by the user as an ASCII file (using a text editor) and placed in the
 appropriate directory under the user's current mapset and project
-(i.e. $MAPSET/paint/labels/).
+(i.e. $MAPSET/paint/labels/).
 
 
    NOTES
    
 
diff --git a/display/d.legend.vect/d.legend.vect.html b/display/d.legend.vect/d.legend.vect.html
index 43602b0e936..36a2e4e6533 100644
--- a/display/d.legend.vect/d.legend.vect.html
+++ b/display/d.legend.vect/d.legend.vect.html
@@ -1,6 +1,6 @@
 
    DESCRIPTION
    
 
-Module d.legend.vect draws vector legend of currently displayed vector maps.
+d.legend.vect draws vector legend of currently displayed vector maps.
 
    
 Parameter at defines the screen position of upper-left legend corner.
 Parameter columns defines the number of legend columns.
diff --git a/display/d.linegraph/d.linegraph.html b/display/d.linegraph/d.linegraph.html
index 23a11463df9..a9782c98c2c 100644
--- a/display/d.linegraph/d.linegraph.html
+++ b/display/d.linegraph/d.linegraph.html
@@ -24,7 +24,7 @@ 
    File inputs
    
 should) be only relative paths to these files. While this is not recommended
 for scripting, it can be advantageous when typing the paths
 manually. For example when all files are stored in the directory
-/home/john/data, the user can provide the following in the command
+/home/john/data, the user can provide the following in the command
 line:
 
 
    @@ -145,7 +145,7 @@ 
    EXAMPLE
    
 -->
 
 
    
-The next command sequence creates a file plot.png in the current
+The next command sequence creates a file plot.png in the current
 directory which is the drawing made by d.linegraph.
 
 
    diff --git a/display/d.mon/d.mon.html b/display/d.mon/d.mon.html
index ed1e6cb2344..9f76cff9880 100644
--- a/display/d.mon/d.mon.html
+++ b/display/d.mon/d.mon.html
@@ -52,8 +52,8 @@ 
    Releasing (unselecting) a monitor
    
 
    NOTES
    
 
 d.mon is designed for interactive use. If non-interactive use
-is needed (e.g., in a script) set GRASS_RENDER_IMMEDIATE=png
-(or =cairo) and use the related environment
+is needed (e.g., in a script) set GRASS_RENDER_IMMEDIATE=png
+(or =cairo) and use the related environment
 variables to control output size etc.
 
 
    EXAMPLES
    
@@ -73,7 +73,7 @@ 
    wx0 monitor
    
 Figure: The initialization of display monitor wx0
 
    
 
-All subsequently displayed data will be rendered on monitor wx0.
+All subsequently displayed data will be rendered on monitor wx0.
 
 
     g.region raster=elevation -p
@@ -95,7 +95,7 @@ 
    CAIRO file renderer monitor
    
 
    
 
 From this moment on all displayed data will be rendered into
-file output.pdf.
+file output.pdf.
 
 
    List running monitors
    
 
diff --git a/display/d.path/d.path.html b/display/d.path/d.path.html
index b98e5d90dde..922e0582f75 100644
--- a/display/d.path/d.path.html
+++ b/display/d.path/d.path.html
@@ -10,7 +10,7 @@ 
    NOTE
    
 
 
 The user needs to display a vector map before using d.path. If no graphics monitor
-is open, a file map.png is generated in the current directory.
+is open, a file map.png is generated in the current directory.
 
 
    
 The 'from' and 'to' points are entered by mouse into the map displayed in the GRASS monitor,
diff --git a/display/d.profile/d.profile.html b/display/d.profile/d.profile.html
index 1f4e789639a..cb17088d4de 100644
--- a/display/d.profile/d.profile.html
+++ b/display/d.profile/d.profile.html
@@ -1,6 +1,6 @@
 
    DESCRIPTION
    
 
-This command displays the profile for a specified transect.
+d.profile displays the profile for a specified transect.
 
 
    SEE ALSO
    
 
diff --git a/display/d.rast.arrow/d.rast.arrow.html b/display/d.rast.arrow/d.rast.arrow.html
index 5face5ec59c..912daad0edf 100644
--- a/display/d.rast.arrow/d.rast.arrow.html
+++ b/display/d.rast.arrow/d.rast.arrow.html
@@ -17,7 +17,7 @@ 
    DESCRIPTION
    
 of that category.
 Cells containing null data will be marked with an "X".
 You can disable drawing of null data and unknown aspect values by
-setting its color to "none".
+setting its color to "none".
 
 
    When specifying the magnitude_map option, arrow lengths
 denoting magnitude will be extracted from the cell values of the specified
@@ -35,7 +35,7 @@ 
    DESCRIPTION
    
 the raster map is relatively close in scale. You can use the skip
 option to draw arrows every n-th cell in both directions if you are working
 with relatively high resolutions. It may be useful to disable the grid in
-this case, which is accomplished by setting its color to "none".
+this case, which is accomplished by setting its color to "none".
 
    For GRASS and Compass type aspect maps, the cell values of the aspect map
 will determine the corresponding direction in 360 degrees. ANSWERS type aspect
 maps will be plotted in multiples of 15 degrees counterclockwise from east, and
diff --git a/display/d.rast.num/d.rast.num.html b/display/d.rast.num/d.rast.num.html
index 28d30b75bfc..f35c1c5abf9 100644
--- a/display/d.rast.num/d.rast.num.html
+++ b/display/d.rast.num/d.rast.num.html
@@ -24,7 +24,8 @@ 
    NOTES
    
 
 
    EXAMPLE
    
 
-A) Distance from the streams network (North Carolina sample dataset):
+Distance from the streams network (North Carolina sample dataset):
+
 
     g.region raster=streams_derived -p
 r.grow.distance input=streams_derived distance=dist_from_streams
diff --git a/display/d.rgb/d.rgb.html b/display/d.rgb/d.rgb.html
index 9b706f2b3ce..deae068cb19 100644
--- a/display/d.rgb/d.rgb.html
+++ b/display/d.rgb/d.rgb.html
@@ -1,5 +1,8 @@
 
    DESCRIPTION
    
 
+d.rgb displays three user-specified raster maps as red, green,
+and blue overlays in the active graphics frame.
+
    
 RGB stands for red, green,
 and blue. d.rgb visually combines three raster maps to
 form a color image. For each map, the corresponding component from the
diff --git a/display/d.title/d.title.html b/display/d.title/d.title.html
index 15a0d8e75cd..be02c674f60 100644
--- a/display/d.title/d.title.html
+++ b/display/d.title/d.title.html
@@ -25,17 +25,18 @@ 
    EXAMPLES
    
 For example, a user wishing to create a suitable TITLE for the
 Spearfish, SD soils map layer and to display this TITLE in the
 active display frame on the graphics monitor might type the following:
-
    
-
     d.title map=soils color=red size=5 > TITLE.file
-
     d.text < TITLE.file
-
    
+
+
    +d.title map=soils color=red size=5 > TITLE.file
+d.text < TITLE.file
+
    
+
 Alternately, the user might pipe d.title output directly
 into d.text:
-
    
-
    
-d.title map=soils color=red size=5 |
-d.text
-
    
+
+
    +d.title map=soils color=red size=5 | d.text
+
    
 
 
    A file created by d.title can be displayed
 with d.text.
@@ -45,8 +46,10 @@ 
    EXAMPLES
    
 
 
    SEE ALSO
    
 
-d.font
    
-d.text
    
+
+d.font,
+d.text
+
 
 
    AUTHOR
    
 
diff --git a/display/d.vect.thematic/d.vect.thematic.html b/display/d.vect.thematic/d.vect.thematic.html
index 52ce4908d38..a40a31005b4 100644
--- a/display/d.vect.thematic/d.vect.thematic.html
+++ b/display/d.vect.thematic/d.vect.thematic.html
@@ -40,8 +40,8 @@ 
    Thematic map with classes
    
 
 
    Thematic map with calculated class breaks
    
 
-The following example uses a calculated attribute (density =
-pop/area) and the standard deviation algorithm to calculate class
+The following example uses a calculated attribute (density =
+pop/area) and the standard deviation algorithm to calculate class
 breaks for 5 classes:
 
 
    diff --git a/display/d.vect/d.vect.html b/display/d.vect/d.vect.html
index 4ba8494c41f..38341d0afcb 100644
--- a/display/d.vect/d.vect.html
+++ b/display/d.vect/d.vect.html
@@ -5,14 +5,14 @@ 
    DESCRIPTION
    
 
 
    NOTES
    
 
-d.vect can simply be used typing d.vect
-map=vector_map. There are a large variety of optional parameters
+d.vect can simply be used typing d.vect
+map=vector_map. There are a large variety of optional parameters
 which allow the user to specify vector type, colors, data fields, SQL
 queries, label size and justification, etc.
 
 
    When d.vect is used with where parameter on MS Windows
-Command Prompt, it is important to use ˆ
-carret symbol for escaping special characters < > ( ) & | , ; ".
+Command Prompt, it is important to use ˆ
+carret symbol for escaping special characters < > ( ) & | , ; ".
 
     d.vect map=vector_map where="cat ˆ> 10 AND cat ˆ< 20"
 
    
@@ -32,7 +32,7 @@ 
    NOTES
    
 
 
    Feature colors may be specified
 by v.colors in a form of color
-table or in an attribute table column containing RRR:GGG:BBB
+table or in an attribute table column containing RRR:GGG:BBB
 values.
 
 
    A table for a vector map might look like this:
diff --git a/display/displaydrivers.html b/display/displaydrivers.html
index 2a8f4f71213..2caab56be77 100644
--- a/display/displaydrivers.html
+++ b/display/displaydrivers.html
@@ -3,7 +3,7 @@
 
 The current command line rendering mechanism is direct rendering into
 a file. The driver is selected by setting
-the GRASS_RENDER_IMMEDIATE variable or by
+the GRASS_RENDER_IMMEDIATE variable or by
 running d.mon module.
 
 
    
diff --git a/doc/development/rfc/legal_aspects_of_code_contributions.md b/doc/development/rfc/legal_aspects_of_code_contributions.md
index 596cf301183..9607569c45e 100644
--- a/doc/development/rfc/legal_aspects_of_code_contributions.md
+++ b/doc/development/rfc/legal_aspects_of_code_contributions.md
@@ -66,4 +66,4 @@ source repository:
 Questions regarding GRASS GIS should be directed to the
 GRASS Development Team at the following address:
 
-Internet: 
+Internet: 
diff --git a/doc/projectionintro.html b/doc/projectionintro.html
index 33bc964e3d7..c51c9efc761 100644
--- a/doc/projectionintro.html
+++ b/doc/projectionintro.html
@@ -63,8 +63,8 @@ 
    References
    
 
  •  ASPRS Grids and Datum
    • 
 
  •  Projections Transform List (PROJ)
    • 
 
  •  Coordinate operations by PROJ (projections, conversions, transformations, pipeline operator)
    • 
-
  •  MapRef - The Collection of Map Projections and Reference Systems for Europe
    • 
-
  •  Information and Service System for European Coordinate Reference Systems - CRS
    • 
+
  •  MapRef - The Collection of Map Projections and Reference Systems for Europe
    • 
+
  •  Information and Service System for European Coordinate Reference Systems - CRS
    •

See also

diff --git a/general/g.filename/g.filename.html b/general/g.filename/g.filename.html index 0f6c89357e3..5462f5cb48e 100644 --- a/general/g.filename/g.filename.html +++ b/general/g.filename/g.filename.html @@ -6,7 +6,7 @@

DESCRIPTION

The list of element names to search for is not fixed; any subdirectory of the mapset directory is a valid element name.

However, the user can find the list of standard GRASS GIS element names in -the file $GISBASE/etc/element_list. This is the file which +the file $GISBASE/etc/element_list. This is the file which g.remove/g.rename/g.copy use to determine which files need to be deleted/renamed/copied for a given entity type. diff --git a/general/g.findfile/g.findfile.html b/general/g.findfile/g.findfile.html index 140495691d9..5746759fbd9 100644 --- a/general/g.findfile/g.findfile.html +++ b/general/g.findfile/g.findfile.html @@ -7,7 +7,7 @@

DESCRIPTION

The list of element names to search for is not fixed; any subdirectory of the mapset directory is a valid element name.

However, the user can find the list of standard GRASS element -names in the file $GISBASE/etc/element_list. This is the file +names in the file $GISBASE/etc/element_list. This is the file which g.remove, g.rename and g.copy use to determine which files need to be deleted/renamed/copied for a given entity type. diff --git a/general/g.gisenv/g.gisenv.html b/general/g.gisenv/g.gisenv.html index 4eb2a88ed13..bf95770390c 100644 --- a/general/g.gisenv/g.gisenv.html +++ b/general/g.gisenv/g.gisenv.html @@ -1,5 +1,8 @@

DESCRIPTION

+g.gisenv outputs and modifies the user's current GRASS GIS +variable settings. + When a user runs GRASS, certain variables are set specifying the GRASS data base, project, mapset, peripheral device drivers, etc., being used in the current GRASS session. These variable name settings are @@ -46,7 +49,7 @@

OPTIONS

"project" directory itself contains subdirectories called "mapsets"; each "mapset" stores "data base elements" - the directories (e.g., -the cell, cellhd, vector, etc., directories) +the cell, cellhd, vector, etc., directories) in which GRASS data files are actually stored.
LOCATION_NAME @@ -118,7 +121,7 @@

OPTIONS

The full path to the current mapset is determined from GISDBASE, LOCATION_NAME, MAPSET variables, in the example -above: /opt/grassdata/spearfish/PERMANENT. The full path can +above: /opt/grassdata/spearfish/PERMANENT. The full path can be printed using g.gisenv by providing multiple variables: 
@@ -146,7 +149,7 @@ 
NOTES

 By default the GRASS variables are stored in gisrc file
 (defined by environmental
 variable GISRC). If store=mapset is given then the
-variables are stored in <gisdbase>/<project>/<mapset>/VAR
+variables are stored in <gisdbase>/<project>/<mapset>/VAR
 after the current GRASS session is closed.
 
 
EXAMPLES

diff --git a/general/g.gui/g.gui.html b/general/g.gui/g.gui.html
index 4c8b162b6b1..3988edb68e3 100644
--- a/general/g.gui/g.gui.html
+++ b/general/g.gui/g.gui.html
@@ -11,18 +11,18 @@ 
DESCRIPTION

 
 
NOTES

 
-If the -d update flag is given or the GRASS_GUI
+If the -d update flag is given or the GRASS_GUI
 environmental variable is unset, then
-the GRASS internal variable GUI is permanently changed and
+the GRASS internal variable GUI is permanently changed and
 the selected ui will be used as the default UI from then on.
 
 

 All GRASS internal variables (see g.gisenv)
 are stored in the user's home directory in a hidden file called
-$HOME/.grass8/rc on Unix-based operating systems
-and %APPDATA%\GRASS8\rc on MS Windows. Note that these GRASS
+$HOME/.grass8/rc on Unix-based operating systems
+and %APPDATA%\GRASS8\rc on MS Windows. Note that these GRASS
 internal variables are not the shell environment variables and the
-rc file is not a classic UNIX run command file, it just
+rc file is not a classic UNIX run command file, it just
 contains persistent GRASS variables.
 
 
EXAMPLES

diff --git a/general/g.list/g.list.html b/general/g.list/g.list.html
index b99b46cde61..cc646c6ad7b 100644
--- a/general/g.list/g.list.html
+++ b/general/g.list/g.list.html
@@ -42,7 +42,7 @@ 
Mapset search path

 If mapset is not specified, then g.list searches for
 data files in the mapsets that are included in the search path
 (defined by g.mapsets).
-See g.mapsets -p.
+See g.mapsets -p.
 
 
 g.list rast -p
@@ -66,7 +66,7 @@ 
Mapset search path

 
 Similarly, mapset=* (one asterisk) prints data files from all
 available mapsets also including those that are not listed in the
-current search path (see g.mapsets -l).
+current search path (see g.mapsets -l).
 
 
 g.list rast mapset=* -p
@@ -177,7 +177,7 @@ 
Maps whose region overlaps with a saved region

 g.list type=rast,vect region=*
 

 
-Note that, without region=*, g.list type=rast,vect simply
+Note that, without region=*, g.list type=rast,vect simply
 lists all available raster and vector maps from the current search path
 regardless of their region.
 
diff --git a/general/g.mapset/g.mapset.html b/general/g.mapset/g.mapset.html
index d8838b59a26..dd32c1d00d8 100644
--- a/general/g.mapset/g.mapset.html
+++ b/general/g.mapset/g.mapset.html
@@ -4,7 +4,7 @@ 
DESCRIPTION

 as location), or GISDBASE (directory with one or more projects).
 
 

-With g.mapset, the shell history (i.e. .bash_history file
+With g.mapset, the shell history (i.e. .bash_history file
 of the initial project will be used to record the command history.
 
 
NOTES

diff --git a/general/g.mapsets/g.mapsets.html b/general/g.mapsets/g.mapsets.html
index 3fe1a52df73..8fa75baaf2f 100644
--- a/general/g.mapsets/g.mapsets.html
+++ b/general/g.mapsets/g.mapsets.html
@@ -1,5 +1,8 @@
 
DESCRIPTION

 
+g.mapsets modifies/prints the user's current mapset search
+path.
+
 For basic information about GRASS mapset, project
 and data base refer to GRASS
 Quickstart.
@@ -23,7 +26,7 @@ 
DESCRIPTION

 their current mapset. Although the user can
 also access (i.e., use) data that are stored under
 other mapsets in the same GRASS project using the
-mapname@mapsetname notation or mapset search path, the user
+mapname@mapsetname notation or mapset search path, the user
 can only make permanent changes (create or modify data)
 located in the current mapset.  The user's
 mapset search path lists the order in which other mapsets in
@@ -33,7 +36,7 @@ 
DESCRIPTION

 using the g.mapsets command. This program allows the user to
 use other's relevant map data without altering the original data
 layer, and without taking up disk space with a copy of the original
-map. The mapname@mapsetname notation may be used irrespective
+map. The mapname@mapsetname notation may be used irrespective
 of the mapset search path, i.e., any map found in another mapset with
 sufficient g.access privileges
 may be called in such a manner.
@@ -60,8 +63,8 @@ 
DESCRIPTION

 g.copy raster=soils@PERMANENT,my_soils
 

 
-ensures that a new file named my_soils is to be a copy of
-the file soils from the mapset PERMANENT.
+ensures that a new file named my_soils is to be a copy of
+the file soils from the mapset PERMANENT.
 
 

 In each project there is the special mapset PERMANENT included
diff --git a/general/g.message/g.message.html b/general/g.message/g.message.html
index 07bf643c97b..67587eaf002 100644
--- a/general/g.message/g.message.html
+++ b/general/g.message/g.message.html
@@ -1,10 +1,13 @@
 
DESCRIPTION

 
-
This program is to be used in Shell/Perl/Python scripts, so the author does not
-need to use the echo program. The advantage of g.message is
+g.message prints a message, warning, progress info, or fatal error
+in the GRASS GIS way.
+
+This program is to be used in Shell/Perl/Python scripts, so the author does not
+need to use the echo program. The advantage of g.message is
 that it formats messages just like other GRASS modules do and that its
-functionality is influenced by the GRASS_VERBOSE and
-GRASS_MESSAGE_FORMAT environment variables.
+functionality is influenced by the GRASS_VERBOSE and
+GRASS_MESSAGE_FORMAT environment variables.
 
 

 The program can be used for standard informative messages as well as warnings
@@ -14,7 +17,7 @@ 
DESCRIPTION

 
 
NOTES

 
-Messages containing "=" must use the full message= syntax so
+Messages containing "=" must use the full message= syntax so
 the parser doesn't get confused.
 

 If you want a long message (multi-line) to be dealt with as a single
@@ -31,18 +34,18 @@ 
NOTES

 

 It's advisable to single quote the messages that are to be printed literally.
 It prevents a number of characters (most notably, space and the dollar sign
-'$') from being treated specifically by the shell.
+'$') from being treated specifically by the shell.
 

 When it is necessary to include, for example, a variable's value as part of
 the message, the double quotes may be used, which do not deprive the
 dollar sign of its special variable-expansion powers.
 

 While it is known that the interactive Bash instances may treat the
-exclamation mark '!' character specifically (making single quoting
+exclamation mark '!' character specifically (making single quoting
 of it necessary), it shouldn't be the case for the non-interactive
 instances of Bash. Nonetheless, to avoid context-based confusion later on
 you are encouraged to single-quote messages that do not require
-$VARIABLE expansion.
+$VARIABLE expansion.
 
 
Usage in Python scripts

 
@@ -51,13 +54,13 @@ 
Usage in Python scripts

 for g.message.
 
 
    
-  
  • debug() for g.message -d
    • 
-  
  • error() for g.message -e
    • 
-  
  • fatal() for g.message -e + exit()
    • 
-  
  • info() for g.message -i
    • 
-  
  • message() for g.message
    • 
-  
  • verbose() for g.message -v
    • 
-  
  • warning() for g.message -w
    • 
+  
  • debug() for g.message -d
    • 
+  
  • error() for g.message -e
    • 
+  
  • fatal() for g.message -e + exit()
    • 
+  
  • info() for g.message -i
    • 
+  
  • message() for g.message
    • 
+  
  • verbose() for g.message -v
    • 
+  
  • warning() for g.message -w
    • 
 

 
 

@@ -78,7 +81,7 @@ 
Usage in Python scripts

VERBOSITY LEVELS

-Controlled by the "GRASS_VERBOSE" environment variable. Typically this +Controlled by the "GRASS_VERBOSE" environment variable. Typically this is set using the --quiet or --verbose command line options.
  • 0 - only errors and warnings are printed
    • @@ -88,7 +91,7 @@

    VERBOSITY LEVELS

DEBUG LEVELS

-Controlled by the "DEBUG" GRASS gisenv variable (set with +Controlled by the "DEBUG" GRASS gisenv variable (set with g.gisenv).
Recommended levels: diff --git a/general/g.mkfontcap/g.mkfontcap.html b/general/g.mkfontcap/g.mkfontcap.html index b1ddeb0663b..2854d808a3b 100644 --- a/general/g.mkfontcap/g.mkfontcap.html +++ b/general/g.mkfontcap/g.mkfontcap.html @@ -2,7 +2,7 @@

DESCRIPTION

g.mkfontcap is a utility to generate a GRASS font configuration file ("fontcap") containing details of the fonts available on the current system. -If Freetype is not installed, +If Freetype is not installed, the font list will be limited to the set of Hershey stroke fonts supplied with GRASS. With Freetype enabled however, the module will recursively scan all files within a predefined hierarchy to find Freetype-compatible scalable @@ -24,10 +24,10 @@

DESCRIPTION

of the string, if enclosed in ${xxx} syntax (see examples above).

The module will normally write to the standard fontcap file location, -$GISBASE/etc/fontcap. If the environment variable -GRASS_FONT_CAP is set, the output will instead be written +$GISBASE/etc/fontcap. If the environment variable +GRASS_FONT_CAP is set, the output will instead be written to the file specified by that variable. This is useful if you don't have -permission to modify $GISBASE/etc/fontcap: in this case you can +permission to modify $GISBASE/etc/fontcap: in this case you can use e.g. 

diff --git a/general/g.parser/g.parser.html b/general/g.parser/g.parser.html
index 224049b46bb..c438a675454 100644
--- a/general/g.parser/g.parser.html
+++ b/general/g.parser/g.parser.html
@@ -75,8 +75,8 @@ 
OPTIONS

 # %end
-With {NULL} it is possible to suppress a predefined description -or label. +With {NULL} it is possible to suppress a predefined description +or label.

The parsers allows using predefined standardized options and @@ -150,9 +150,9 @@

NOTES

-A "guisection" field may be added to each option and flag to +A "guisection" field may be added to each option and flag to specify that the options should appear in multiple tabs in the -auto-generated GUI. Any options without a guisection field +auto-generated GUI. Any options without a guisection field go into the "Required" or "Options" tab. For example: 

 # % guisection: tabname
@@ -160,23 +160,23 @@ 
NOTES

 would put that option in a tab named tabname.
 
 

-A "key_desc" field may be added to each option to specify the text that
+A "key_desc" field may be added to each option to specify the text that
 appears in the module's usage help section. For example:
 
 # % key_desc: filename
 

 added to an input option would create the usage summary
-[input=filename].
+[input=filename].
 
 

 If a script is run with --o, the parser will
-set GRASS_OVERWRITE=1, which has the same effect as passing
+set GRASS_OVERWRITE=1, which has the same effect as passing
 --o to every module which is run from the script. Similarly, passing
---q or --v will set GRASS_VERBOSE to 0 or 3 respectively,
+--q or --v will set GRASS_VERBOSE to 0 or 3 respectively,
 which has the same effect as passing --q or --v to every module which
 is run from the script.  Rather than checking whether --o, --q or --v
-were used, you should be checking GRASS_OVERWRITE and/or
-GRASS_VERBOSE instead. If those variables are set, the script
+were used, you should be checking GRASS_OVERWRITE and/or
+GRASS_VERBOSE instead. If those variables are set, the script
 should behave the same way regardless of whether they were set
 by --o, --q or --v being passed to the script or
 set by other means.
@@ -191,13 +191,13 @@ 
Conditional parameters

 
 Marking an option as "required" will result in the parser raising a
 fatal error if the option is not given, with one exception: if a flag
-has the suppress_required option, and that flag is given, all
+has the suppress_required option, and that flag is given, all
 requirements are ignored. This feature is intended for flags which
 abandon "normal operation" for the module; e.g. r.in.gdal's
 -f flag (list supported formats) uses it.
 

 But in general, an option cannot be marked as required if it is
-optional except for the special case of a suppress_required flag.
+optional except for the special case of a suppress_required flag.
 The parser has the ability to specify option relationships.
 
 

@@ -219,15 +219,15 @@ 
Conditional parameters

 The available rule types are:
 
 
    
-
  •  exclusive: at most one of the options may be given
    • 
-
  •  required: at least one of the options must be given
    • 
-
  •  requires: if the first option is given, at least one of the
+
  •  exclusive: at most one of the options may be given
    • 
+
  •  required: at least one of the options must be given
    • 
+
  •  requires: if the first option is given, at least one of the
       subsequent options must also be given
    • 
-
  •  requires_all: if the first option is given, all of the
+
  •  requires_all: if the first option is given, all of the
       subsequent options must also be given
    • 
-
  •  excludes: if the first option is given, none of the
+
  •  excludes: if the first option is given, none of the
       subsequent options may be given
    • 
-
  •  collective: all or nothing; if any option is given, all
+
  •  collective: all or nothing; if any option is given, all
       must be given
    • 
 

 
@@ -305,7 +305,7 @@ 
reStructuredText
reStructuredText is sometimes abbreviated as reST, ReST, or RST. -The commonly used file extension is .rst. +The commonly used file extension is .rst. Don't be confused with Representational State Transfer (REST) technology.

TRANSLATION

@@ -334,7 +334,7 @@

EXAMPLES

To run properly, the script needs to be copied into a directory listed -in $GRASS_ADDON_PATH environmental variable with the +in $GRASS_ADDON_PATH environmental variable with the executable flag being set.

diff --git a/general/g.proj/g.proj.html b/general/g.proj/g.proj.html index b7f4f185af3..89a44c93622 100644 --- a/general/g.proj/g.proj.html +++ b/general/g.proj/g.proj.html @@ -11,9 +11,9 @@

DESCRIPTION

If compiled without OGR present, the functionality is limited to:
    -
  • Reporting the CRS information for the current project -(previously called location), -either in conventional GRASS (-p flag) or PROJ (-j flag) format
    • +
  • Reporting the CRS information for the current project (previously called +location), either in conventional GRASS (-p flag) or PROJ (-j +flag) format
  • Changing the datum, or reporting and modifying the datum transformation parameters, for the current project
@@ -32,25 +32,25 @@

DESCRIPTION

read from this file. If the file is not georeferenced or cannot be read, XY (unprojected) will be used. -
wkt=filename or -
+
wkt=filename or -
The file filename should contain a CRS description in WKT -format with or without line-breaks (e.g. a '.prj' file). If - is given +format with or without line-breaks (e.g. a '.prj' file). If - is given for the filename, the WKT description will be read from stdin rather than a file.
-
proj4=description or -
+
proj4=description or -
description should be a CRS description in PROJ format, enclosed in -quotation marks if there are any spaces. If - is given for +quotation marks if there are any spaces. If - is given for description, the PROJ description will be read from stdin rather than as a directly-supplied command-line parameter.
epsg=number
number should correspond to the index number of a valid -co-ordinate system in the EPSG +co-ordinate system in the EPSG database. EPSG code support is based upon a local copy of the GDAL CSV co-ordinate system and datum information files, stored in the directory -$GISBASE/etc/proj/ogr_csv. These can be updated if necessary +$GISBASE/etc/proj/ogr_csv. These can be updated if necessary to support future revisions of the EPSG database.
@@ -65,22 +65,22 @@

DESCRIPTION

datumtrans parameter should in general always be used in conjunction with datum. -

The -p, -j, -w, etc. flags are all functional when importing CRS -information from an external source, meaning that g.proj can be -used to convert between representations of the information. It is +

The -p, -j, -w, etc. flags are all functional when +importing CRS information from an external source, meaning that g.proj +can be used to convert between representations of the information. It is not required that either the input or output be in GRASS format. -

In addition however, if the -c flag is specified, g.proj will +

In addition however, if the -c flag is specified, g.proj will create new GRASS CRS files (PROJ_INFO, PROJ_UNITS, WIND and DEFAULT_WIND) based on the imported information. If the project -parameter is specified in addition to -c, then a new project will be created. +parameter is specified in addition to -c, then a new project will be created. Otherwise the CRS information files in the current project will be overwritten. The program will not warn before doing this. -

The final mode of operation of g.proj is to report on the datum +

The final mode of operation of g.proj is to report on the datum information and datum transformation parameters associated with the -co-ordinate system. The -d flag will report a human-readable summary of +co-ordinate system. The -d flag will report a human-readable summary of this.

NOTES

@@ -88,17 +88,21 @@

NOTES

If the input co-ordinate system contains a datum name but no transformation parameters, and there is more than one suitable parameter set available (according to the files datum.table and datumtransform.table in -$GISBASE/etc/proj), g.proj will check the value of -the datumtrans option and act according to the following:
--1: List available parameter sets in a GUI-parsable (but also -human-readable) format and exit.
-0 (default): Continue without specifying parameters - if +$GISBASE/etc/proj), g.proj will check the value of +the datumtrans option and act according to the following: + +

+ +If the -t flag is specified, the module will attempt to change the datum transformation parameters using one of the above two methods even if a valid parameter set is already specified in the input co-ordinate system. This can be useful to change the datum information @@ -167,10 +171,10 @@

Create new project

Create a new project with the coordinate system referred to by EPSG code -900913 (Google Mercator Projection)
+3857 (Pseudo-Mercator Projection)

-g.proj -c epsg=900913 project=google
+g.proj -c epsg=3857 project=google

Create a new project with the coordinate system referred to by EPSG code @@ -229,7 +233,7 @@

REFERENCES

Further reading

diff --git a/general/g.region/g.region.html b/general/g.region/g.region.html index 85d75a058df..2eb4e58aa08 100644 --- a/general/g.region/g.region.html +++ b/general/g.region/g.region.html @@ -4,7 +4,7 @@

DESCRIPTION

settings of the current geographic region. These regional boundaries can be set by the user directly and/or set from a region definition file (stored under the -windows directory in the user's current +windows directory in the user's current mapset). The user can create, modify, and store as many geographic region definitions as desired for any given mapset. However, only one of these geographic region @@ -50,8 +50,8 @@

DEFINITIONS

Each GRASS project (previously called location) has a fixed geographic region, called the default geographic region -(stored in the region file DEFAULT_WIND under -the special mapset PERMANENT), that defines the +(stored in the region file DEFAULT_WIND under +the special mapset PERMANENT), that defines the extent of the data base. While this provides a starting point for defining new geographic regions, user-defined geographic regions need not fall within this geographic @@ -73,14 +73,14 @@

DEFINITIONS

Each GRASS MAPSET may contain any number of pre-defined, and named, geographic regions. These region definitions are stored in the user's current mapset -location under the windows directory (also +location under the windows directory (also referred to as the user's saved region definitions). Any of these pre-defined geographic regions may be selected, by name, to become the current geographic region. Users may also access saved region definitions stored under other mapsets in the current project, if these mapsets are included in the user's mapset search -path or the '@' operator is used (region_name@mapset). +path or the '@' operator is used (region_name@mapset).

NOTES

@@ -118,7 +118,7 @@

NOTES

The -g flag prints the current region settings in shell script style. This format can be given back to g.region on its command line. This may also be used to save region settings as shell environment variables -with the UNIX eval command, "eval `g.region -g`". +with the UNIX eval command, "eval `g.region -g`".

With -u flag current region is not updated even if one or more options for changing region is used (res=, raster=, etc). @@ -163,9 +163,9 @@

EXAMPLES

Printing extent and raster resolution in 2D and 3D

-
+
g.region -p - +
This will print the current region in the format: @@ -185,9 +185,9 @@

Printing extent and raster resolution in 2D and 3D

-

+
g.region -p3 - +
This will print the current region and the 3D region (used for voxels) in the format: @@ -216,9 +216,9 @@

Printing extent and raster resolution in 2D and 3D

-

+
g.region -g - +
The -g option prints the region in the following script style (key=value) format: @@ -235,9 +235,9 @@

Printing extent and raster resolution in 2D and 3D

-

+
g.region -bg - +
The -bg option prints the region in the following script style (key=value) format plus the @@ -259,9 +259,9 @@

Printing extent and raster resolution in 2D and 3D

-

+
g.region -l - +
The -l option prints the region in the following format: @@ -278,9 +278,9 @@

Printing extent and raster resolution in 2D and 3D

-

+
g.region -pm - +
This will print the current region in the format (latitude-longitude project): @@ -303,36 +303,36 @@

Printing extent and raster resolution in 2D and 3D

Changing extent and raster resolution using values

-
+
g.region n=7360100 e=699000 - +
will reset the northing and easting for the current region, but leave the south edge, west edge, and the region cell resolutions unchanged.

-

+
g.region n=51:36:05N e=10:10:05E s=51:29:55N w=9:59:55E res=0:00:01 - +
will reset the northing, easting, southing, westing and resolution for the current region, here in DMS latitude-longitude style (decimal degrees and degrees with decimal minutes can also be used).

-

+
g.region -dp s=698000 - +
will set the current region from the default region for the GRASS project, reset the south edge to 698000, and then print the result.

-

+
g.region n=n+1000 w=w-500 - +
The n=value may also be specified as a function of its current value: n=n+value @@ -344,9 +344,9 @@

Changing extent and raster resolution using values

decreased by 500 units.

-

+
g.region n=s+1000 e=w+1000 - +
This form allows the user to set the region boundary values relative to one another. Here, the northern @@ -364,19 +364,18 @@

Changing extent and raster resolution using values

Changing extent and raster resolution using maps

-
+
g.region raster=soils - +
This form will make the current region settings exactly the same as those given in the cell header file for the raster map layer soils.

- -

+
g.region raster=soils zoom=soils - +
This form will first look up the cell header file for the raster map layer soils, use this as the @@ -385,14 +384,13 @@

Changing extent and raster resolution using maps

data in the map layer soils. Note that if the parameter raster=soils were not specified, the zoom would shrink to encompass all non-NULL data values in -the soils map that were located within the current region +the soils map that were located within the current region settings.

- -

+
g.region -up raster=soils - +
The -u option suppresses the re-setting of the current region definition. This can be useful when it is @@ -401,24 +399,24 @@

Changing extent and raster resolution using maps

without changing the current region settings.

-

+
g.region -up zoom=soils save=soils - +
This will zoom into the smallest region which encompasses all non-NULL soils data values, and save the new region settings in a file to be called soils -and stored under the windows directory in the +and stored under the windows directory in the user's current mapset. The current region settings are not changed.

Changing extent and raster resolution in 3D

-
+
g.region b=0 t=3000 tbres=200 res3=100 g.region -p3 - +
This will define the 3D region for voxel computations. In this example a volume with bottom (0m) to top (3000m) @@ -430,7 +428,7 @@

Using g.region in a shell in combination with OGR

Extracting a spatial subset of the external vector map -soils.shp into new external vector map soils_cut.shp +soils.shp into new external vector map soils_cut.shp using the OGR ogr2ogr tool:
@@ -443,8 +441,8 @@ 
Using g.region in a shell in combination with OGR

 
Using g.region in a shell in combination with GDAL

 
 Extracting a spatial subset of the external raster map
-p016r035_7t20020524_z17_nn30.tif into new external raster
-map p016r035_7t20020524_nc_spm_wake_nn30.tif using the GDAL
+p016r035_7t20020524_z17_nn30.tif into new external raster
+map p016r035_7t20020524_nc_spm_wake_nn30.tif using the GDAL
 gdalwarp tool:

 
 
diff --git a/general/g.remove/g.remove.html b/general/g.remove/g.remove.html
index b6554a398db..974a5d7c40e 100644
--- a/general/g.remove/g.remove.html
+++ b/general/g.remove/g.remove.html
@@ -3,16 +3,16 @@ 
DESCRIPTION

 g.remove removes data files matching a pattern given by wildcards or
 POSIX Extended Regular Expressions. If the -f force flag is not given
 then nothing is removed, instead the list of selected file names is printed to
-stdout as a preview of the files to be deleted.
+stdout as a preview of the files to be deleted.
 
 
EXAMPLES

 
-Delete map1 and map2 raster maps in the current mapset:
+Delete map1 and map2 raster maps in the current mapset:
 
 g.remove -f type=raster name=tmp1,tmp2
 

 
-Delete all raster and vector maps starting with "tmp_" in the current
+Delete all raster and vector maps starting with "tmp_" in the current
 mapset:
 
 # show matching raster and vector maps but do not delete yet (as verification)
@@ -22,8 +22,8 @@ 
EXAMPLES

 g.remove -f type=raster,vector pattern="tmp_*"
 

 
-Delete all vector maps starting with "stream_" in the current mapset,
-but exclude those ending with "_final":
+Delete all vector maps starting with "stream_" in the current mapset,
+but exclude those ending with "_final":
 
 g.remove -f type=vector pattern="stream_*" exclude="*_final"
 

diff --git a/general/g.setproj/g.setproj.html b/general/g.setproj/g.setproj.html
index f59d8331ced..eb39ccb4010 100644
--- a/general/g.setproj/g.setproj.html
+++ b/general/g.setproj/g.setproj.html
@@ -52,7 +52,7 @@ 
NOTES

 
If the datum or ellipsoid required are not
 listed within this program, the user/administrator may add the definition
 to the files datum.table, datumtransform.table and ellipse.table in the
-$GISBASE/etc/proj directory.
+$GISBASE/etc/proj directory.
 
 
Depending on the projection selected, the user will then be prompted for
 the various other parameters required to define it.
@@ -74,9 +74,9 @@ 
SEE ALSO

 
 
Further reading
 

 
diff --git a/general/g.tempfile/g.tempfile.html b/general/g.tempfile/g.tempfile.html
index 8952e531b78..224db92106e 100644
--- a/general/g.tempfile/g.tempfile.html
+++ b/general/g.tempfile/g.tempfile.html
@@ -3,7 +3,7 @@ 
DESCRIPTION

 g.tempfile
 is designed for shell scripts that need to use large temporary files.
 GRASS provides a mechanism for temporary files that does not depend on
-/tmp. GRASS temporary files are created in the data base with the assumption
+/tmp/. GRASS temporary files are created in the data base with the assumption
 that there will be enough space under the data base for large files.
 GRASS periodically removes temporary files that have been left behind
 by programs that failed to remove them before terminating.
@@ -13,18 +13,21 @@ 
DESCRIPTION

 creates an unique file and prints the name. The user is required to provide
 a process-id which will be used as part of the name of the file.
 Most Unix shells provide a way to get the process id of the current shell.
-For /bin/sh and /bin/csh this is $$.
-It is recommended that $$ be specified as the process-id for
+For /bin/sh and /bin/csh this is $$.
+It is recommended that $$ be specified as the process-id for
 g.tempfile.
 
 
EXAMPLE

 
-For /bin/sh scripts the following syntax should be used:
+For /bin/sh scripts the following syntax should be used:
+
 
 temp1=`g.tempfile pid=$$`
 temp2=`g.tempfile pid=$$`
 

-For /bin/csh scripts, the following can be used:
+
+For /bin/csh scripts, the following can be used:
+
 
 set temp1=`g.tempfile pid=$$`
 set temp2=`g.tempfile pid=$$`
@@ -38,10 +41,10 @@ 
NOTES

 Although GRASS does eventually get around to removing
 tempfiles that have been left behind, the programmer should
 make every effort to remove these files. They often get
-large and take up disk space. If you write /bin/sh scripts,
-learn to use the /bin/sh trap command. If you
-write /bin/csh scripts, learn to use the /bin/csh
-onintr command.
+large and take up disk space. If you write /bin/sh scripts,
+learn to use the /bin/sh related trap command. If you
+write /bin/csh scripts, learn to use the /bin/csh
+related onintr command.
 
 
AUTHOR

 
diff --git a/general/g.version/g.version.html b/general/g.version/g.version.html
index f5d2f63043c..abb3867c9d5 100644
--- a/general/g.version/g.version.html
+++ b/general/g.version/g.version.html
@@ -22,7 +22,7 @@ 
NOTES

 by -e flag.
 
 

-See also function version()
+See also function version()
 from Python
 Scripting Library.
 
@@ -69,10 +69,10 @@ 
Full info in shell script style

 sqlite=3.36.0
 

 
-Note: if revision=exported is reported instead of the git hash then the
-git program was not available during compilation of GRASS GIS and the
-source code did not contain the .git/ subdirectory (requires e.g. to
-git clone the GRASS GIS software repository.)
+Note: if revision=exported is reported instead of the git hash then the
+git program was not available during compilation of GRASS GIS and the
+source code did not contain the .git/ subdirectory (requires e.g. to
+git clone the GRASS GIS software repository.)
 
 
Citing GRASS GIS

 
diff --git a/gui/wxpython/dbmgr/g.gui.dbmgr.html b/gui/wxpython/dbmgr/g.gui.dbmgr.html
index 0416843d43b..114e36fd46a 100644
--- a/gui/wxpython/dbmgr/g.gui.dbmgr.html
+++ b/gui/wxpython/dbmgr/g.gui.dbmgr.html
@@ -74,7 +74,7 @@ 
SEE ALSO

 
 
AUTHORS

 
-Martin Landa, FBK-irst (2007-2008),
+Martin Landa, FBK-irst (2007-2008),
 Trento, Italy, and OSGeoREL at the Czech Technical
 University in Prague, Czech Republic

 Michael Barton, Arizona State University, USA

diff --git a/gui/wxpython/docs/wxGUI.components.html b/gui/wxpython/docs/wxGUI.components.html
index 5dd0cb3b657..b1be3d092f5 100644
--- a/gui/wxpython/docs/wxGUI.components.html
+++ b/gui/wxpython/docs/wxGUI.components.html
@@ -1,6 +1,13 @@
 
 
 
+
KEYWORDS

+
+
+general, GUI
+
+
DESCRIPTION

+
 List of available wxGUI components:
 
 
+
+
SEE ALSO

+
+
+  wxGUI
+
diff --git a/gui/wxpython/docs/wxGUI.html b/gui/wxpython/docs/wxGUI.html
index fec5ced8c22..70643d6b24f 100644
--- a/gui/wxpython/docs/wxGUI.html
+++ b/gui/wxpython/docs/wxGUI.html
@@ -441,7 +441,7 @@ 
Map Display Toolbar

       
  • Zoom to saved region. Zooms to previously
       saved named region.
    • 
       
  • Set computational region extent from display.
-      The computational region (the mapset's WIND file)
+      The computational region (the mapset's WIND file)
       is set to match the current display extent (does not change
       the resolution), see g.region.
    • 
       
  • Set computational region extent interactively.
@@ -657,9 +657,9 @@ 
    Starting the GUI from command line
    
 
    • 
 
 Alternatively, it may be defined in the main configuration file
-($HOME/.grass8/rc on GNU/Linux and macOS, %APPDATA%\Roaming\GRASS8\rc
-on MS Windows) using the GUI variable set to wxpython
-(GUI: wxpython) or by the environmental variable GRASS_GUI.
+($HOME/.grass8/rc on GNU/Linux and macOS, %APPDATA%\Roaming\GRASS8\rc
+on MS Windows) using the GUI variable set to wxpython
+(GUI: wxpython) or by the environmental variable GRASS_GUI.
 
 
 To start with a previously saved workspace file:
@@ -670,7 +670,7 @@ 
    Starting the GUI from command line
    
 
 
    
 The user can also start GRASS from the shell command line with the wxGUI
-specifying the --gui switch:
+specifying the --gui switch:
 
 
     grass --gui
@@ -680,14 +680,14 @@ 
    Starting the GUI from command line
    
 The GUI can be quit by selecting the 'File > Quit GRASS GIS' menu item
 which gives options to close only GUI or to quit GRASS GIS entirely
 if GRASS GIS is running with a command line (a shell in a terminal application).
-Exiting the shell (typically by the exit command) ends the GRASS session
+Exiting the shell (typically by the exit command) ends the GRASS session
 including any running GUIs.
 
 
    Background information
    
 
 wxGUI is a native Graphical User Interface (GUI) for
 GRASS GIS written in Python
-using wxPython library.
+using wxPython library.
 
 
    SEE ALSO
    
 
diff --git a/gui/wxpython/docs/wxGUI.iscatt.html b/gui/wxpython/docs/wxGUI.iscatt.html
index d1601eb1c0d..6e263d2d1fb 100644
--- a/gui/wxpython/docs/wxGUI.iscatt.html
+++ b/gui/wxpython/docs/wxGUI.iscatt.html
@@ -10,8 +10,8 @@ 
    DESCRIPTION
    
 Interactive Scatter Plot Tool allows analyzing group of raster
 maps. The tool is integrated into 
 Supervised Classification Tool (see the screen shot below).
-Also it is possible to launch it from Map Display Window (Analyze map
-→ Interactive Scatter Plot Tool).
+Also it is possible to launch it from Map Display Window (Analyze map
+→ Interactive Scatter Plot Tool).
 
 The main idea of the tool is that everything is linked together
 (scatter plots together and mapwindow with the scatter plots).
@@ -39,7 +39,7 @@ 
    TOOL CONTROLS LAYOUT
    
 
 
 If editing mode is activated (the green polygon tool in toolbar), the areas which were selected
-in the scatter plots are highlighted. In the image you can see this area for scatter plot of bands B_6, B_7 inside the ellipse.
+in the scatter plots are highlighted. In the image you can see this area for scatter plot of bands B_6, B_7 inside the ellipse.
 Opacity and color of the selected area can be set in settings. The area corresponds to the active class (in this case clouds).
 Selected areas are subset of areas, which belongs to the category.
 
    
@@ -71,7 +71,7 @@ 
    SEE ALSO
    
 
   wxGUI,
   wxGUI components,
-  r.rescale
    
+  r.rescale
     
 
 
    
diff --git a/gui/wxpython/docs/wxGUI.modules.html b/gui/wxpython/docs/wxGUI.modules.html
index 44aeedace61..7e8125f7443 100644
--- a/gui/wxpython/docs/wxGUI.modules.html
+++ b/gui/wxpython/docs/wxGUI.modules.html
@@ -1,5 +1,10 @@
 
 
+
+
    KEYWORDS
    
+
+general, GUI
+
 
    DESCRIPTION
    
 
 GRASS GIS functionality is organized into modules, which are standalone programs
@@ -76,7 +81,7 @@ 
    Current working directory
    
 It can be changed in wxGUI menu
 Settings - GRASS working environment -
 Change working directory,
-or by typing cd and pressing Enter in the wxGUI Command console.
+or by typing cd and pressing Enter in the wxGUI Command console.
 If the working directory is changed to a directory where the input files are,
 then it is enough to specify just the name of the file instead of the full path.
 
diff --git a/gui/wxpython/docs/wxGUI.nviz.html b/gui/wxpython/docs/wxGUI.nviz.html
index 3c0767f9598..df62a7a8d23 100644
--- a/gui/wxpython/docs/wxGUI.nviz.html
+++ b/gui/wxpython/docs/wxGUI.nviz.html
@@ -395,10 +395,8 @@ 
    SEE ALSO
    
 (especially various video
 tutorials).
 
-

    
-
+
    
 Command-line module m.nviz.image.
-

    
 
 
    AUTHORS
    
 
diff --git a/gui/wxpython/docs/wxGUI.toolboxes.html b/gui/wxpython/docs/wxGUI.toolboxes.html
index ccbf4f6415c..8679a8eab31 100644
--- a/gui/wxpython/docs/wxGUI.toolboxes.html
+++ b/gui/wxpython/docs/wxGUI.toolboxes.html
@@ -1,5 +1,10 @@
 
 
+
+
    KEYWORDS
    
+
+general, GUI
+
 
    DESCRIPTION
    
 
 The Toolboxes is a way to customize items in wxGUI
@@ -15,22 +20,22 @@ 
    DESCRIPTION
    
 
 
 
    
-Toolboxes are configured through two XML files (main_menu.xml and
-toolboxes.xml) located in your user home
-GRASS directory, subdirectory toolboxes
- ($HOME/.grass8/toolboxes/ on UNIX).
+Toolboxes are configured through two XML files (main_menu.xml and
+toolboxes.xml) located in your user home
+GRASS directory, subdirectory toolboxes
+ ($HOME/.grass8/toolboxes/ on UNIX).
 Currently, there is no GUI front-end for toolboxes,
 however only simple editing of text files is needed.
    
 
-
    Brief description of file main_menu.xml
    
+
    Brief description of file main_menu.xml
    
 
 
    This file represents the main menu (File, Settings, Raster, ...).
 By modifying this file you show and hide menu items which are
-represented by subtoolbox tag.
    
+represented by subtoolbox tag.
    
 
-
    Tag user-toolboxes-list is interpreted as a menu containing a list of all user-defined toolboxes. If not needed it can be removed.
    
+
    Tag user-toolboxes-list is interpreted as a menu containing a list of all user-defined toolboxes. If not needed it can be removed.
    
 
-
    Following lines can be copied to .grass8/toolboxes/main_menu.xml
+
    Following lines can be copied to .grass8/toolboxes/main_menu.xml
 and by removing, adding or reordering lines users can change the main menu items. See further examples.
    
 
 
@@ -52,16 +57,16 @@ 
    Brief description of file main_menu.xml
    
 </toolbox>
 
    
 
-
    Brief description of file toolboxes.xml
    
+
    Brief description of file toolboxes.xml
    
 
 
    This file contains structure and description of individual toolboxes.
 Note that both Raster and e.g. Query raster maps
 are individual toolboxes although one contains the other.
-Tag toolbox contains subtoolbox tags
+Tag toolbox contains subtoolbox tags
 which are defined later in the file. These nested toolboxes are linked
-through name attribute.
    
+through name attribute.
    
 
-
    Apart from subtoolbox tag, tag toolbox can contain individual items (modules)
+
    Apart from subtoolbox tag, tag toolbox can contain individual items (modules)
 and separators (for visual separation in the menu tree).
    
 
 
    @@ -94,9 +99,9 @@ 
    Brief description of file toolboxes.xml
    
 
    
 
 
    To redefine a toolbox (or use it as a template),
-copy specific part of file grass7/gui/wxpython/xml/toolboxes.xml
+copy specific part of file grass7/gui/wxpython/xml/toolboxes.xml
 from GRASS installation to a new file in user home
-(.grass8/toolboxes/toolboxes.xml) and edit it.
+(.grass8/toolboxes/toolboxes.xml) and edit it.
 Rename this new toolbox.
    
 
 
    EXAMPLES
    
@@ -104,7 +109,7 @@ 
    EXAMPLES
    
 
    Hiding menu items
    
 
    If we are for example working only with raster data,
 we can hide menu items Vector and Database.
-The file main_menu.xml then contains the following lines
+The file main_menu.xml then contains the following lines
 where we omitted the two toolboxes:
    
 
 
@@ -129,7 +134,7 @@ 
    Creating custom toolbox
    
 
    In this example we create a new toolbox Favorites containing
 existing GRASS module and toolbox, custom module
 created by the user and addon module.
-The toolboxes.xml file contains following lines:
    
+The toolboxes.xml file contains following lines:
    
 
 
     <?xml version="1.0" encoding="UTF-8"?>
@@ -157,7 +162,7 @@ 
    Creating custom toolbox
    
 
    
 
 
    Optionally, we can add this toolbox to the main menu items.
-The main_menu.xml file contains following lines:
    
+The main_menu.xml file contains following lines:
    
 
 
     <?xml version="1.0" encoding="UTF-8"?>
@@ -178,7 +183,7 @@ 
    Creating custom toolbox
    
 </toolbox>
 
    
 
-
    If we have user-toolboxes-list tag in the main_menu.xml file,
+
    If we have user-toolboxes-list tag in the main_menu.xml file,
 our custom toolbox will be listed in the automatically added Toolboxes main menu item. The screenshot shows the resulting menu:
    
 
 
    
@@ -188,8 +193,8 @@ 
    Creating custom toolbox
    
 
    NOTES
    
 
 
    After the first start of wxGUI with custom toolboxes,
-.grass/toolboxes directory will contain file
-menudata.xml which is auto-generated and should not be edited.
    
+.grass/toolboxes directory will contain file
+menudata.xml which is auto-generated and should not be edited.
    
 
 
    SEE ALSO
    
 
diff --git a/gui/wxpython/docs/wxGUI.vnet.html b/gui/wxpython/docs/wxGUI.vnet.html
index c1b8a51831b..f6be4446e3f 100644
--- a/gui/wxpython/docs/wxGUI.vnet.html
+++ b/gui/wxpython/docs/wxGUI.vnet.html
@@ -8,7 +8,7 @@ 
    KEYWORDS
    
 
    DESCRIPTION
    
 
 Vector Network Analysis Tool is graphical front-end
-for v.net* modules. It allows perform network analysis
+for v.net* modules. It allows perform network analysis
 directly in wxGUI without need to
 use command line. The tool can be launched from Layer Manager
 menu Vector → Network analysis → Vector network analysis
diff --git a/gui/wxpython/gmodeler/g.gui.gmodeler.html b/gui/wxpython/gmodeler/g.gui.gmodeler.html
index dae5aefea52..9a31c63c85c 100644
--- a/gui/wxpython/gmodeler/g.gui.gmodeler.html
+++ b/gui/wxpython/gmodeler/g.gui.gmodeler.html
@@ -46,7 +46,7 @@ 
    DESCRIPTION
    
 
    Main dialog
    
 
 The Graphical Modeler can be launched from the Layer Manager menu
-File -> Graphical modeler or from the main
+File -> Graphical modeler or from the main
 toolbar icon. It's also
 available as stand-alone module g.gui.gmodeler.
 
@@ -152,8 +152,8 @@ 
    Components of models
    
 
 
    EXAMPLE
    
 
-In this example the zipcodes_wake vector data and the
-elev_state_500m raster data from the North Carolina
+In this example the zipcodes_wake vector data and the
+elev_state_500m raster data from the North Carolina
 sample dataset (original raster and
 vector
 data) are used to calculate average elevation for every
@@ -209,7 +209,7 @@ 
    Defining the workflow in the Graphical Modeler
    
 
    Managing model parameters
    
 All used modules can be parameterized in the model. That causes launching the
 dialog with input options for model after the model is run. In this example,
-input layers (zipcodes_wake vector map and elev_state_500m
+input layers (zipcodes_wake vector map and elev_state_500m
 raster map) are parameterized. Parameterized elements show their diagram border
 slightly thicker than those of unparameterized elements.
 
@@ -260,7 +260,7 @@ 
    Managing model parameters
    
 
 
    Managing model properties
    
 When the user wants to run the model again with the same data or the same names, it is
-necessary to use --overwrite option. It will cause maps with identical
+necessary to use --overwrite option. It will cause maps with identical
 names to be overwritten. Instead of setting it for every
 module separately it is handy to change the Model Property settings globally.
 This dialog includes also metadata settings, where model name, model description
@@ -283,9 +283,9 @@ 
    Defining variables
    
 Then it is not
 necessary to set any parameters for input data. The dialog with variable settings
 is automatically displayed after the model is run. So, instead of model parameters
-(e.g. r.import a v.import, see the Figure
+(e.g. r.import a v.import, see the Figure
 Run model dialog above)
-there are Variables.
+there are Variables.
 
 
    
 
@@ -295,13 +295,13 @@ 
    Defining variables
    
 
    
 
 
    
-The key point is the usage of % before the substituting variable and
-settings in the Variables dialog. For example, in the case of a model variable
-raster that points to an input file path and which value is required to be
+The key point is the usage of % before the substituting variable and
+settings in the Variables dialog. For example, in the case of a model variable
+raster that points to an input file path and which value is required to be
 used as one of inputs for a particular model, it should be specified in the
-Variables dialog with its respective name (raster), data type,
+Variables dialog with its respective name (raster), data type,
 default value and description. Then it should be set in the module dialog as
-input called %raster.
+input called %raster.
 
 
    
 
@@ -320,13 +320,13 @@ 
    Defining variables
    
 
 
    Saving the model file
    
 Finally, the model settings can be stored as a GRASS GIS Model file with
-*.gxm extension. The advantage is that it can be shared as a
+*.gxm extension. The advantage is that it can be shared as a
 reusable workflow that may be run also by other users with different data.
 
 
    
 
 For example, this model can later be used to calculate the average precipitation
-for every administrative region in Slovakia using the precip raster data from
+for every administrative region in Slovakia using the precip raster data from
 
 Slovakia precipitation dataset and administration boundaries of Slovakia from
 Slovak Geoportal
@@ -335,7 +335,7 @@ 
    Saving the model file
    
 
    Handling intermediate data
    
 There can be some data in a model that did not exist before the process and
 that it is not worth it to maintain after the process executes. They can
-be described as being Intermediate by single clicking using the right
+be described as being Intermediate by single clicking using the right
 mouse button, see figure below. All such data should be deleted following
 model completion. The boundary of intermediate component is dotted line.
 
@@ -348,7 +348,7 @@ 
    Handling intermediate data
    
 
 
    Using the Script editor
    
 By using the Script editor in the Graphical Modeler, the user can add Python code and then
-run it with Run button or just save it as a Python script *.py.
+run it with Run button or just save it as a Python script *.py.
 The result is shown in the Figure below:
 
 
    
@@ -388,21 +388,21 @@ 
    Using the Script editor
    
 
 
    
 By default GRASS script package API is used
-(grass.script.core.run_command()). This can be changed in the
+(grass.script.core.run_command()). This can be changed in the
 settings. Alternatively also PyGRASS API is supported
-(grass.pygrass.modules.Module).
+(grass.pygrass.modules.Module).
 
 
    Defining loops
    
 In the example below the MODIS MOD13Q1
 (NDVI) satellite data products are used in a loop. The original data are
 stored as coded integer values that need to be multiplied by the
-value 0.0001 to represent real ndvi values. Moreover, GRASS GIS
-provides a predefined color table called ndvi to represent ndvi data.
+value 0.0001 to represent real ndvi values. Moreover, GRASS GIS
+provides a predefined color table called ndvi to represent ndvi data.
 In this case it is not necessary to work with every image separately.
 
    
 The Graphical Modeler is an appropriate tool to
-process data in an effective way using loop and variables (%map for a
-particular MODIS image in mapset and %ndvi for original data name suffix).
+process data in an effective way using loop and variables (%map for a
+particular MODIS image in mapset and %ndvi for original data name suffix).
 After the loop component is added to model, it is necessary to define series of maps
 with required settings of map type, mapset, etc.
 
diff --git a/gui/wxpython/mapswipe/g.gui.mapswipe.html b/gui/wxpython/mapswipe/g.gui.mapswipe.html
index ae4fe135a0f..105cf612c74 100644
--- a/gui/wxpython/mapswipe/g.gui.mapswipe.html
+++ b/gui/wxpython/mapswipe/g.gui.mapswipe.html
@@ -6,7 +6,7 @@ 
    DESCRIPTION
    
 which allows the user to interactively compare two raster maps of the same
 area by revealing different parts of the raster maps.
 It is useful e.g. for comparing raster maps from different time periods.
-Map Swipe can be launched from the menu File -> Map Swipe.
+Map Swipe can be launched from the menu File -> Map Swipe.
 
 
    
 Map Swipe allows you to:
@@ -32,7 +32,7 @@ 
    DESCRIPTION
    
 MODIS image on March 13, 2011, shows a clear view of tsunami flooding along the coastline.
 Water, black and dark blue in these false-color images, still covers the ground as much
 as five kilometers (three miles) from the coast.
-Source: Earth Observatory/NASA
+Source: Earth Observatory/NASA
 
    
 
    
 
diff --git a/gui/wxpython/rlisetup/g.gui.rlisetup.html b/gui/wxpython/rlisetup/g.gui.rlisetup.html
index ae5663bb7d6..cda5d236ccd 100644
--- a/gui/wxpython/rlisetup/g.gui.rlisetup.html
+++ b/gui/wxpython/rlisetup/g.gui.rlisetup.html
@@ -61,14 +61,14 @@ 
    Usage details
    
  and other notes (disposition of sample areas etc).
 -->
  Configuration files are saved in the folder
- C:\Users\userxy\AppData\Roaming\GRASS8\r.li\ (MS-Windows) or
- $HOME/.r.li/ (GNU/Linux) (the file name can be
+ C:\Users\userxy\AppData\Roaming\GRASS8\r.li\ (MS-Windows) or
+ $HOME/.r.li/ (GNU/Linux) (the file name can be
  defined by the user). The output or an analysis can either be a new raster
  map (in case of using a "moving window" analysis) or be an ASCII text file
  (when not performing a "moving window" analysis) containing the result.
  Such text file will be saved in the folder
- C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\
- (MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).
+ C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\
+ (MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).
  
    
  
  All dimensions are percentages of raster rows or columns.
@@ -315,7 +315,7 @@ 
    Whole region analysis
    
 r.li.shannon input=lsat7_2000_40 conf=whole_region output=lsat7_2000_40_shannon
    -The result is the new text file "forests_p_dens7" (stored in folder $HOME/.r.li/output/. +The result is the new text file "forests_p_dens7" (stored in folder $HOME/.r.li/output/.
    See the respective modules for further examples. @@ -323,7 +323,7 @@

    REFERENCES

    McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

    SEE ALSO

    diff --git a/gui/wxpython/vdigit/g.gui.vdigit.html b/gui/wxpython/vdigit/g.gui.vdigit.html index d02064b997f..766c0209270 100644 --- a/gui/wxpython/vdigit/g.gui.vdigit.html +++ b/gui/wxpython/vdigit/g.gui.vdigit.html @@ -161,7 +161,7 @@

    DIGITIZER TOOLBAR

  • Break selected lines/boundaries at intersection
    Split given vector line or boundary into two lines on given position (based on v.clean, - tool=break).
    • + tool=break).
  • Connect two selected lines/boundaries
    Connect selected lines or boundaries, the first given line is connected to the diff --git a/imagery/i.aster.toar/i.aster.toar.html b/imagery/i.aster.toar/i.aster.toar.html index 793d0834447..aaaf287e200 100644 --- a/imagery/i.aster.toar/i.aster.toar.html +++ b/imagery/i.aster.toar/i.aster.toar.html @@ -38,7 +38,7 @@

    SEE ALSO

    ASTER sensor data download: -ASTER: Advanced Spaceborne Thermal Emission and Reflection Radiometer +ASTER: Advanced Spaceborne Thermal Emission and Reflection Radiometer

    AUTHOR

    diff --git a/imagery/i.atcorr/i.atcorr.html b/imagery/i.atcorr/i.atcorr.html index bf122963aba..8365c6294cf 100644 --- a/imagery/i.atcorr/i.atcorr.html +++ b/imagery/i.atcorr/i.atcorr.html @@ -849,14 +849,14 @@

    Atmospheric correction of a Sentinel-2 band

    1. Geometrical conditions -

      For Sentinel-2A, the geometrical conditions take the value 25 and for -Sentinel-2B, the geometrical conditions value is 26 (See table A). +

      For Sentinel-2A, the geometrical conditions take the value 25 and for +Sentinel-2B, the geometrical conditions value is 26 (See table A). Our scene comes from the Sentinel-2A mission (the file name begins with S2A_...).

    2. Day, time, longitude and latitude of measurement

      Day and time of the measurement are hidden in the filename (i.e., the -second datum in the file name with format YYYYMMDDTHHMMSS), +second datum in the file name with format YYYYMMDDTHHMMSS), and are also noted in the metadata file, which is included in the downloaded scene (file with .xml extension). Our sample scene was taken on October 28th (20161028) at 15:54:02 (155402). Note @@ -873,20 +873,20 @@

      Atmospheric correction of a Sentinel-2 band

      The longitude and latitude of the centre are stored in ll_clon -and ll_clat. In our case, ll_clon=-78.691 and -ll_clat=35.749. +and ll_clat. In our case, ll_clon=-78.691 and +ll_clat=35.749.

    3. Atmospheric model

      We can choose between various atmospheric models as defined at the -beginning of this manual. For North Carolina, we can choose 2 - -midlatitude summer. +beginning of this manual. For North Carolina, we can choose 2 - +midlatitude summer.

    4. Aerosol model

      We can also choose between various aerosol models as defined at the -beginning of this manual. For North Carolina, we can choose 1 - -continental model. +beginning of this manual. For North Carolina, we can choose 1 - +continental model.

    5. Visibility or Aerosol Optical Depth @@ -909,13 +909,13 @@

      Atmospheric correction of a Sentinel-2 band

      The mean elevation is stored in mean. In our case, -mean=110. In the 6S file it will be displayed in [-km], -i.e., -0.110. +mean=110. In the 6S file it will be displayed in [-km], +i.e., -0.110.

    6. Sensor height

      Since the sensor is on board a satellite, the sensor height will be -set to -1000. +set to -1000.

    7. Sensor band @@ -926,7 +926,7 @@

      Atmospheric correction of a Sentinel-2 band

      Finally, here is what the 6S file would look like for Band 02 of our scene. In order to use it in the i.atcorr module, we can save -it in a text file, for example params_B02.txt. +it in a text file, for example params_B02.txt. 

       25
 10 28 15.901 -78.691 35.749
@@ -947,7 +947,7 @@ 
      Atmospheric correction of a Sentinel-2 band
      
     
    8. input = raster band to be processed,
      9. 
     
    9. parameters = path to 6S file created in the previous step (we could also enter the values directly),
      10. 
     
    10. output = name for the output corrected raster band,
      11. 
-    
    11. range = from 1 to the QUANTIFICATION_VALUE stored in the metadata file. It is 10000 for both Sentinel-2A and Sentinel-2B.
      12. 
+    
    12. range = from 1 to the QUANTIFICATION_VALUE stored in the metadata file. It is 10000 for both Sentinel-2A and Sentinel-2B.
      13. 
     
    13. rescale = the output range of values for the corrected bands. This is up to the user to choose, for example: 0-255, 0-1, 1-10000.
      14. 
 
 
      If the data is available, the following parameters can be specified
@@ -1007,7 +1007,7 @@ 
      Atmospheric correction of a Landsat-7 band
      If the overpass time is unknown, use the -NASA LaRC Satellite Overpass Predictor. +NASA LaRC Satellite Overpass Predictor.

      Convert digital numbers (DN) to radiance at top-of-atmosphere (TOA)

      @@ -1039,7 +1039,7 @@

      Convert digital numbers (DN) to radiance at top-of-atmosphere (TOA)

      and maximal DN value, and they are reported in the metadata file of each image. High gain or low gain is also reported in the metadata file of each satellite image. For Landsat ETM+, the minimal DN value (QCALMIN) is 1 -(see Landsat handbook, chapter 11), +(see Landsat handbook, chapter 11), and the maximal DN value (QCALMAX) is 255. QCAL is the DN value for every separate pixel in the Landsat image.

      We extract the coefficients and apply them in order to obtain the @@ -1072,7 +1072,7 @@

      Create the parameters file for i.atcorr

      defining geometrical and atmospherical conditions of the satellite overpass. -Here we create a control file icnd_lsat4.txt for band 4 (NIR), +Here we create a control file icnd_lsat4.txt for band 4 (NIR), based on metadata. For the overpass time, we need to define decimal hours: 10:42:07 NC local time = 10.70 decimal hours (decimal minutes: 42 * 100 / 60) which is 15.70 GMT. @@ -1098,7 +1098,7 @@

      Create the parameters file for i.atcorr

      Note that the altitude value from 'icnd_lsat4.txt' file is read at the beginning to compute the initial transform. Therefore, it is necessary to provide a value that might be the mean value of the elevation model -(r.univar elevation). For the atmospheric correction per se, the +(r.univar elevation). For the atmospheric correction per se, the elevation values from the raster map are used.

      Note that the process is computationally intensive. Note also, that i.atcorr reports solar elevation angle above horizon rather @@ -1125,7 +1125,7 @@

      REFERENCES

    14. 6S Manual: PDF1, PDF2, and PDF3
      15. -
    15. RapidEye sensors have been provided by RapidEye AG, Germany
      16. +
    16. RapidEye sensors have been provided by RapidEye AG, Germany
    17. Barsi, J.A., Markham, B.L. and Pedelty, J.A., 2011, The operational land imager: spectral response and spectral uniformity., Proc. SPIE 8153, 81530G; doi:10.1117/12.895438
      18. @@ -1164,10 +1164,10 @@

      AUTHORS

      RapidEye sensors addition 11/2010:
      Peter Löwe, Anne Ghisla -

      VGT1 and VGT2 sensors addition from 6SV-1.1 sources, addition 07/2011: +

      VGT1 and VGT2 sensors addition from 6SV-1.1 sources, addition 07/2011:
      Alfredo Alessandrini, Anne Ghisla -

      Added Landsat 8 from NASA sources, addition 05/2014: +

      Added Landsat 8 from NASA sources, addition 05/2014:
      Nikolaos Ves

      Geoeye1 addition 7/2015: diff --git a/imagery/i.eb.netrad/i.eb.netrad.html b/imagery/i.eb.netrad/i.eb.netrad.html index c6cba3ad484..d4d96b7d966 100644 --- a/imagery/i.eb.netrad/i.eb.netrad.html +++ b/imagery/i.eb.netrad/i.eb.netrad.html @@ -14,7 +14,7 @@

      NOTES

      In the old methods, dT was taken as flat images (dT=5.0), if you don't have a dT map from ground data, you would want to try something in this line, this is to calculate atmospherical energy balance. In the same way, a standard tsw is used -in those equations. Refer to r_net.c for that and for other non-used equations, +in those equations. Refer to r_net.c for that and for other non-used equations, but stored in there for further research convenience.

      TODO

      diff --git a/imagery/i.landsat.acca/i.landsat.acca.html b/imagery/i.landsat.acca/i.landsat.acca.html index 5e594389762..41f69905706 100644 --- a/imagery/i.landsat.acca/i.landsat.acca.html +++ b/imagery/i.landsat.acca/i.landsat.acca.html @@ -22,9 +22,9 @@

      EXAMPLES

      Run the standard ACCA algorithm with filling of small cloud holes (the -f flag): With per-band reflectance raster maps -named 226_62.toar.1, 226_62.toar.2, [...] and LANDSAT-7 -thermal band 226_62.toar.61, outputting to a new raster map -named 226_62.acca: +named 226_62.toar.1, 226_62.toar.2, ... and LANDSAT-7 +thermal band 226_62.toar.61, outputting to a new raster map +named 226_62.acca: 
       i.landsat.toar sensor=7 gain=HHHLHLHHL date=2003-04-07 \
@@ -35,7 +35,7 @@ 
      EXAMPLES
      
 
 
      REFERENCES
      
 
-
        
+
          
   
        • Irish R.R., Barker J.L., Goward S.N., and Arvidson T., 2006.
     Characterization of the Landsat-7 ETM+ Automated Cloud-Cover
     Assessment (ACCA) Algorithm. Photogrammetric Engineering and Remote
@@ -45,7 +45,7 @@ 
          REFERENCES
          
     S.S. Shen and M.R. Descour (Eds.): Algorithms for Multispectral,
     Hyperspectral, and Ultraspectral Imagery VI. Proceedings of SPIE,
     4049: 348-355.
          • 
-
      
+
 
 
      SEE ALSO
      
 
diff --git a/imagery/i.landsat.toar/i.landsat.toar.html b/imagery/i.landsat.toar/i.landsat.toar.html
index 4a792c26274..3305c80b7de 100644
--- a/imagery/i.landsat.toar/i.landsat.toar.html
+++ b/imagery/i.landsat.toar/i.landsat.toar.html
@@ -243,7 +243,7 @@ 
      DOS1 example
      
   product_date=2004-02-12 gain=HHHLHLHHL
      -The resulting Landsat channels are named lsat7_2002_toar.1 .. lsat7_2002_toar.8. +The resulting Landsat channels are named lsat7_2002_toar.1 .. lsat7_2002_toar.8.

      REFERENCES

      diff --git a/imagery/i.modis.qc/i.modis.qc.html b/imagery/i.modis.qc/i.modis.qc.html index 3147a006bd1..8f96364a937 100644 --- a/imagery/i.modis.qc/i.modis.qc.html +++ b/imagery/i.modis.qc/i.modis.qc.html @@ -498,12 +498,12 @@

      NOTES

      MOD11A2 quality control (QC) bands do not have a FillValue (No-data) according to MODIS Land Products site. -However, the metadata of the QC bands (i.e.: gdalinfo QC_band) shows No-data=0. +However, the metadata of the QC bands (i.e.: gdalinfo QC_band) shows No-data=0. This value is then transformed into GRASS NULLs when data is imported through r.in.gdal. Applying i.modis.qc on those QC bands will not give the expected range of values in the different QC bits. Therefore, before using i.modis.qc, the user needs to set the NULL value in QC bands -back to zero (i.e.: r.null map=QC_band null=0) or just edit the metadata with GDAL +back to zero (i.e.: r.null map=QC_band null=0) or just edit the metadata with GDAL utilities before importing into GRASS GIS. This is a known issue for MOD11A2 (8-day LST product), but other MODIS products might be affected as well. diff --git a/imagery/i.ortho.photo/i.ortho.elev/i.ortho.elev.html b/imagery/i.ortho.photo/i.ortho.elev/i.ortho.elev.html index ab5b66eaa38..21fedea7e7f 100644 --- a/imagery/i.ortho.photo/i.ortho.elev/i.ortho.elev.html +++ b/imagery/i.ortho.photo/i.ortho.elev/i.ortho.elev.html @@ -1,6 +1,14 @@

      DESCRIPTION

      -i.ortho.elev is used to select or modify the target elevation model. +i.ortho.elev is used to select or modify the target elevation +model for orthorectification of imagery. +This elevation model is essential for both the computation of photo-to-target +parameters and for the actual orthorectification of imagery group files. +The elevation model selected should cover the entire area of the image +group to be orthorectified. + +Optionally, scaled elevation data can be converted to real elevation values +specifying a mathematical expression.

      SEE ALSO

      diff --git a/imagery/i.ortho.photo/i.ortho.transform/i.ortho.transform.html b/imagery/i.ortho.photo/i.ortho.transform/i.ortho.transform.html index 4bb60a9c633..83c7f32f65c 100644 --- a/imagery/i.ortho.photo/i.ortho.transform/i.ortho.transform.html +++ b/imagery/i.ortho.photo/i.ortho.transform/i.ortho.transform.html @@ -5,7 +5,7 @@

      DESCRIPTION

      If coordinates are given with the input file option or fed from -stdin, both the input and the output format is "x y z" with one +stdin, both the input and the output format is "x y z" with one coordinate pair per line. Reverse transform is performed with the -r flag. diff --git a/imagery/i.rectify/i.rectify.html b/imagery/i.rectify/i.rectify.html index b8c21b0b7ef..6bfc49dd4c1 100644 --- a/imagery/i.rectify/i.rectify.html +++ b/imagery/i.rectify/i.rectify.html @@ -11,8 +11,8 @@

      DESCRIPTION

      are first, second, and third order polynomial and thin plate spline. Thin plate spline is recommended for ungeoreferenced satellite imagery where ground control points (GCPs) are included. Examples are -NOAA/AVHRR -and ENVISAT +NOAA/AVHRR +and ENVISAT imagery which include throusands of GCPs.

      @@ -161,9 +161,9 @@

      Resampling method

      NOTES

      If i.rectify starts normally but after some time the following text is seen: -
      +
      ERROR: Error writing segment file -
      +
      the user may try the -c flag or the module needs more free space on the hard drive. diff --git a/imagery/i.segment/i.segment.html b/imagery/i.segment/i.segment.html index 43d5e5fde68..74de8f9177a 100644 --- a/imagery/i.segment/i.segment.html +++ b/imagery/i.segment/i.segment.html @@ -1,5 +1,8 @@

      DESCRIPTION

      +i.segment identifies segments (objects) from +imagery data. +

      Image segmentation or object recognition is the process of grouping similar pixels into unique segments, also referred to as objects. Boundary and region based algorithms are described in the literature, @@ -64,10 +67,10 @@

      Calculation Formulas

      In future, the distance calculation will also take into account the shape characteristics of the segments. The normal distances are then multiplied by the input radiometric weight. Next an additional -contribution is added: (1-radioweight) * {smoothness * smoothness -weight + compactness * (1-smoothness weight)}, -where compactness = Perimeter Length / sqrt( Area ) -and smoothness = Perimeter Length / Bounding Box. The +contribution is added: (1-radioweight) * {smoothness * smoothness +weight + compactness * (1-smoothness weight)}, +where compactness = Perimeter Length / sqrt( Area ) +and smoothness = Perimeter Length / Bounding Box. The perimeter length is estimated as the number of pixel sides the segment has. @@ -175,7 +178,7 @@

      Segmentation of RGB orthophoto

      -The output ortho_segs_l4 with threshold=0.2 still has +The output ortho_segs_l4 with threshold=0.2 still has too many segments, but the output with threshold=0.3 has too few segments. A threshold value of 0.25 seems to be a good choice. There is also some noise in the image, lets next force all segments smaller diff --git a/imagery/i.svm.predict/i.svm.predict.html b/imagery/i.svm.predict/i.svm.predict.html index 3ddf4f33879..f0dbcf511cb 100644 --- a/imagery/i.svm.predict/i.svm.predict.html +++ b/imagery/i.svm.predict/i.svm.predict.html @@ -72,11 +72,6 @@

      REFERENCES

      -

      AUTHORS

      +

      AUTHOR

      Maris Nartiss, University of Latvia. - - diff --git a/imagery/i.svm.train/i.svm.train.html b/imagery/i.svm.train/i.svm.train.html index e25397d7ca6..d0ea9b8ba83 100644 --- a/imagery/i.svm.train/i.svm.train.html +++ b/imagery/i.svm.train/i.svm.train.html @@ -101,11 +101,6 @@

      REFERENCES

      -

      AUTHORS

      +

      AUTHOR

      Maris Nartiss, University of Latvia. - - diff --git a/imagery/i.vi/i.vi.html b/imagery/i.vi/i.vi.html index 38786a22abc..0ed45b41d2d 100644 --- a/imagery/i.vi/i.vi.html +++ b/imagery/i.vi/i.vi.html @@ -517,7 +517,7 @@

      Preparation: DN to reflectance

      product_date=2004-02-12 gain=HHHLHLHHL -The resulting Landsat channels are names lsat7_2002_toar.1 .. lsat7_2002_toar.8. +The resulting Landsat channels are names lsat7_2002_toar.1 .. lsat7_2002_toar.8.

      Calculation of NDVI

      @@ -578,7 +578,7 @@

      Calculation of GARI

      NOTES

      -Originally from kepler.gps.caltech.edu (FAQ): +Originally from kepler.gps.caltech.edu (FAQ):

      A FAQ on Vegetation in Remote Sensing
      Written by Terrill W. Ray, Div. of Geological and Planetary Sciences, diff --git a/imagery/imageryintro.html b/imagery/imageryintro.html index a9c93696632..deda9a28a11 100644 --- a/imagery/imageryintro.html +++ b/imagery/imageryintro.html @@ -30,9 +30,9 @@

      Image processing in general

      by the sensor of the satellite platform is encoded in 8 or more bits. This energy is called radiance-at-sensor. To obtain physical values from DNs, satellite image providers use a linear transform -equation (y = a * x + b) to encode the radiance-at-sensor +equation (y = a * x + b) to encode the radiance-at-sensor in 8 to 16 bits. DNs can be turned back into physical values by -applying the reverse formula (x = (y - b) / a). +applying the reverse formula (x = (y - b) / a).

      The GRASS GIS module i.landsat.toar easily transforms Landsat DN to radiance-at-sensor (top of atmosphere, @@ -171,7 +171,7 @@

      Calculation of vegetation indices

      status with NDVI, the Red and the Near Infrared channels (NIR) are taken as used as input for simple map algebra in the GRASS command r.mapcalc -(ndvi = 1.0 * (nir - red)/(nir + red)). With +(ndvi = 1.0 * (nir - red)/(nir + red)). With r.colors an optimized "ndvi" color table can be assigned afterward. Also other vegetation indices can be generated likewise. diff --git a/lib/cairodriver/cairodriver.html b/lib/cairodriver/cairodriver.html index 22f8e1264c8..2e294af5edd 100644 --- a/lib/cairodriver/cairodriver.html +++ b/lib/cairodriver/cairodriver.html @@ -7,7 +7,7 @@

      DESCRIPTION

      The Cairo driver generates PNG, BMP, PPM, PS, PDF or SVG images by GRASS display commands, using the -Cairo graphics library. +Cairo graphics library. The image format is selected from the extension of the output file. The Cairo driver is used for GRASS display commands by default if @@ -44,11 +44,11 @@

      Environment variables

    18. GRASS_RENDER_ANTIALIAS
      can be default, none, gray, or subpixel, corresponding to - cairo_antialias_t + cairo_antialias_t
    19. GRASS_RENDER_FILE=filename
      the name and format of the resulting image file, default is - map.png.
      + map.png.
      The image format is determined from the file extension.
      Supported bitmap formats:
        @@ -67,12 +67,12 @@

        Environment variables

        the Cairo library that GRASS was built with.)
      • GRASS_RENDER_FILE_READ
        - if TRUE, the Cairo driver will initialize the image from + if TRUE, the Cairo driver will initialize the image from the contents of GRASS_RENDER_FILE.
        (Note: This is only supported for bitmap formats)
      • GRASS_RENDER_FILE_MAPPED
        - if TRUE, the Cairo driver will map GRASS_RENDER_FILE as its framebuffer, + if TRUE, the Cairo driver will map GRASS_RENDER_FILE as its framebuffer, rather than using memory.
        (Note: This only works with BMP files.)
        • @@ -152,13 +152,13 @@

        NOTES

        The driver is still in development. Enable it by specifying --with-cairo when configuring GRASS. This requires a reasonably recent version of the Cairo libraries -and a working pkg-config. +and a working pkg-config.

        Antialiasing is enabled by default for bitmap formats. There is currently no way of disabling this.

        The resolution of the output images is defined by current region -extents. Use g.region -p to get the number of rows and cols +extents. Use g.region -p to get the number of rows and cols and use the environment variables to set the image size. If you would like a larger image, multiply both rows and cols by the same whole number to preserve the aspect ratio. diff --git a/lib/db/sqlp/sql.html b/lib/db/sqlp/sql.html index a2dc32da2a5..1fd070b7d3c 100644 --- a/lib/db/sqlp/sql.html +++ b/lib/db/sqlp/sql.html @@ -38,10 +38,10 @@

        Database drivers

        https://postgresql.org/ mysqlData storage in MySQL RDBMS -https://www.mysql.org/ +https://www.mysql.com/ odbcData storage via UnixODBC (PostgreSQL, Oracle, etc.) https://www.unixodbc.org/ @@ -69,8 +69,8 @@

        Database table name restrictions

      • Attempts to use a reserved SQL word (depends on database backend) as column or table name will cause a "SQL syntax error".
        • -
      • An error message such as "dbmi: Protocol - error" either indicates an invalid column name or an +
      • An error message such as "dbmi: Protocol + error" either indicates an invalid column name or an unsupported column type (then the GRASS SQL parser needs to be extended).
      • DBF column names are limited to 10 characters (DBF API definition).
        • @@ -151,7 +151,7 @@

        Example of null handling

        Update of attributes

        -Examples of complex expressions in updates (using v.db.* +Examples of complex expressions in updates (using v.db.* modules): 
        @@ -164,7 +164,7 @@ 
        Update of attributes

        -Examples of more complex expressions in updates (using db.* +Examples of more complex expressions in updates (using db.* modules): 

        diff --git a/lib/htmldriver/htmldriver.html b/lib/htmldriver/htmldriver.html
index 81036978dc2..a8ff2f07b43 100644
--- a/lib/htmldriver/htmldriver.html
+++ b/lib/htmldriver/htmldriver.html
@@ -53,11 +53,11 @@ 
        Environment variables
        
   
      • GRASS_RENDER_HTMLTYPE=type
         type of image map to create
     (default is CLIENT):
     
        
-      
        CLIENT    Netscape/IE client-side
+      
        CLIENT    Netscape/IE client-side
         image map (NAME="map").
        
-      
        APACHE    Apache/NCSA server-side image
+      
        APACHE    Apache/NCSA server-side image
         map.
        
-      
        RAW
+      
        RAW
                 Raw url and polygon
         vertices (url  x1  y1  x2  y2 
         .....), suitable for conversion to CERN server format, or
@@ -66,7 +66,7 @@ 
        Environment variables
        
   
        • 
   
      • GRASS_RENDER_FILE=filename
        
     specifies the resulting file to store the html image map, default
-    is htmlmap. Files without absolute path names are written
+    is htmlmap. Files without absolute path names are written
     in the current directory where the driver was started.
     
        
     Any existing file of the same name is overwritten without
@@ -75,21 +75,21 @@ 
        Environment variables
        
   
      • GRASS_RENDER_HTMLMINDIST=n
        
     specifies the minimum distance in pixels that a point must change
     from the previous point to keep in the list of vertices for a
-    polygon.  The default is 2, which means that a point's x
+    polygon.  The default is 2, which means that a point's x
     and y difference from the previous point must change by a number
     of pixels greater than this value.  This parameter helps to
     eliminate closely spaced points.
   
        • 
   
      • GRASS_RENDER_HTMLMINBBOX=n
        
     specifies the minimum bounding box dimensions to record a polygon
-    as a clickable area.  The default is 2, which means that a
+    as a clickable area.  The default is 2, which means that a
     polygon with a bounding box of less than this value is not
     included. This parameter helps to eliminate polygons than are a
     point or line.
   
        • 
   
      • GRASS_RENDER_HTMLMAXPOINTS=n
        
     specifies the maximum number of vertices included in a polygon's
-    clickable area.  The default is 99. Some browsers can only
+    clickable area.  The default is 99. 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.
        • 
@@ -172,7 +172,7 @@ 
        NOTES
        
 
        If you create an HTML file with two or more images and image maps, you
 will need to edit the map names. The HTML driver creates its map
 with the name
-map. A small sed script can easily change the map name:
+map. A small sed script can easily change the map name:
 
 
         sed -e 's/NAME="map"/NAME="foomap"/' < htmlmap > foomap.html
diff --git a/lib/init/grass.html b/lib/init/grass.html
index 736be547716..18747b196ae 100644
--- a/lib/init/grass.html
+++ b/lib/init/grass.html
@@ -72,7 +72,7 @@ 
        Parameters:
        
 
        
 
        GISDBASE
 
         Initial database directory which should be a fully qualified path
-    (e.g., /usr/local/share/grassdata)
+    (e.g., /usr/local/share/grassdata)
 
 
        PROJECT
 
         Initial project directory which is a subdirectory of GISDBASE
@@ -128,15 +128,15 @@ 
        Config flag
        
 version parameters, with the options:
 
 
          
-
        • arch: system architecture (e.g., x86_64-pc-linux-gnu)
          • 
-
        • build: (e.g., ./configure --with-cxx --enable-largefile --with-proj [...])
          • 
-
        • compiler: (e.g., gcc)
          • 
-
        • date: (e.g., 2024-04-10T11:44:54+00:00)
          • 
-
        • path: (e.g., /usr/lib64/grass)
          • 
-
        • python_path: (e.g., /usr/lib64/grass/etc/python)
          • 
-
        • revision: (e.g., 745ee7ec9)
          • 
-
        • svn_revision: (e.g., 062bffc8)
          • 
-
        • version: (e.g., 8.4.0)
          • 
+
        • arch: system architecture (e.g., x86_64-pc-linux-gnu)
          • 
+
        • build: (e.g., ./configure --with-cxx --enable-largefile --with-proj [...])
          • 
+
        • compiler: (e.g., gcc)
          • 
+
        • date: (e.g., 2024-04-10T11:44:54+00:00)
          • 
+
        • path: (e.g., /usr/lib64/grass)
          • 
+
        • python_path: (e.g., /usr/lib64/grass/etc/python)
          • 
+
        • revision: (e.g., 745ee7ec9)
          • 
+
        • svn_revision: (e.g., 062bffc8)
          • 
+
        • version: (e.g., 8.4.0)
          • 
 
        
 
 
        SAMPLE DATA
        
@@ -157,7 +157,7 @@ 
        ENVIRONMENT VARIABLES
        
 bother with these.
 
 
        In addition to these shell environment variables GRASS maintains a
-number of GIS environment variables in the $HOME/.grass8/rc
+number of GIS environment variables in the $HOME/.grass8/rc
 file. User changes to this file will be read during the next startup
 of GRASS. If this file becomes corrupted the user may edit it by hand
 or remove it to start afresh.  See the list
@@ -167,7 +167,7 @@ 
        ENVIRONMENT VARIABLES
        
 
 
        Note that you will need to set these variables using the
 appropriate method required for the UNIX shell that you use (e.g. in a
-Bash shell you must export the variables for them to
+Bash shell you must export the variables for them to
 propagate).
 
 
        User Interface Environment Variable
        
@@ -176,8 +176,8 @@ 
        User Interface Environment Variable
        
 environment variable called GRASS_GUI which indicates the type of user
 interface for GRASS to use. If this variable is not set
 when grass is run, then it will be created and then saved
-in the $HOME/.grass8/rc file for the next time GRASS is
-run. It can be set to text, gtext or gui.
+in the $HOME/.grass8/rc file for the next time GRASS is
+run. It can be set to text, gtext or gui.
 
 
        There is an order of precedence in the way grass
 determines the user interface to use. The following is the hierarchy
@@ -185,19 +185,19 @@ 
        User Interface Environment Variable
        
 
          
   
        1. Command line argument
          2. 
   
        2. Environment variable GRASS_GUI
          3. 
-  
        3. Value set in $HOME/.grass8/rc (GUI)
          4. 
-  
        4. Default value - gui
          5. 
+  
        5. Value set in $HOME/.grass8/rc (GUI)
          6. 
+  
        6. Default value - gui
          7. 
 
        
 
 
        Python Environment Variables
        
 
 
        If you choose to use wxGUI
 interface, then the GRASS_PYTHON environment variable can be used to
-override your system default python command.
+override your system default python command.
 
 
        Suppose for example your system has Python 3.6 installed and you
 install a personal version of the Python 3.8 binaries
-under $HOME/bin. You can use the above variables to have
+under $HOME/bin. You can use the above variables to have
 GRASS use the Python 3.8 binaries instead.
 
 
        @@ -233,8 +233,8 @@ 
        Addon Base for Extra Local GRASS Addon Modules
        
 path environment.
 
 
        If not defined by user, this variable is set by GRASS startup program
-to $HOME/.grass8/addons on GNU/Linux
-and %APPDATA%\Roaming\GRASS8\addons on MS Windows.
+to $HOME/.grass8/addons on GNU/Linux
+and %APPDATA%\Roaming\GRASS8\addons on MS Windows.
 
 
        HTML Browser Variable
        
 
@@ -455,20 +455,20 @@ 
        Using temporary mapset
        
 
 
 
        Troubleshooting
        
-Importantly, to avoid an "[Errno 8] Exec format error" there must be a
+Importantly, to avoid an "[Errno 8] Exec format error" there must be a
 shebang line at the top of
-the script (like #!/bin/sh, #!/bin/bash, or #!/usr/bin/env python3)
+the script (like #!/bin/sh, #!/bin/bash, or #!/usr/bin/env python3)
 indicating which interpreter to be used for the script. The script file must
 have its executable bit set.
 
 
        CAVEAT
        
 
 If you start GRASS using the wxGUI
-interface you must have a python command in your $PATH
+interface you must have a python command in your $PATH
 variable. That is, the command must be named
-python and not something like python3.6. Rarely some
-Python installations do not create a python command. In these
-cases you can override python by GRASS_PYTHON environmental
+python and not something like python3.6. Rarely some
+Python installations do not create a python command. In these
+cases you can override python by GRASS_PYTHON environmental
 variable.
 
 
        Furthermore, if you have more than one version of Python installed,
diff --git a/lib/init/variables.html b/lib/init/variables.html
index b7704c5537b..4bd369abf4b 100644
--- a/lib/init/variables.html
+++ b/lib/init/variables.html
@@ -1,5 +1,11 @@
 
-There are two types of variables:
+
+A variable in scripting is a symbolic name that holds data which can be
+used and modified during script execution. Variables allow scripts to
+store and manipulate values dynamically, making them more flexible and
+reusable.
+
+In GRASS GIS, there are two types of variables:
 
          
 
        • shell
 environment variables,
          • 
@@ -42,18 +48,18 @@ 
          Setting shell environment variables
          
 
        • 
 To get personal BASH shell definitions (aliases, color listing option, ...)
 into GRASS, store them in:
          
-$HOME/.grass8/bashrc
          • 
+$HOME/.grass8/bashrc
 
        • 
 To get personal CSH shell definitions (aliases, color listing option, ...)
 into GRASS, store them in:
          
-$HOME/.grass8/cshrc
          • 
+$HOME/.grass8/cshrc
 
        
 
 
        Setting GRASS gisenv variables
        
 
 Use g.gisenv within GRASS. This permanently
-predefines GRASS variables in the $HOME/.grass8/rc file (Linux, Mac, BSD, ...)
-or in the %APPDATA%\Roaming\GRASS8\rc file (Windows) after the
+predefines GRASS variables in the $HOME/.grass8/rc file (Linux, Mac, BSD, ...)
+or in the %APPDATA%\Roaming\GRASS8\rc file (Windows) after the
 current GRASS session is closed.
 

        
 Usage:
@@ -83,7 +89,7 @@ 
        List of selected (GRASS related) shell environment variables
        
     startup script.
        
 
   
        GISRC
        
-  
        name of $HOME/.grass8/rc file. Defines the system wide value
+  
        name of $HOME/.grass8/rc file. Defines the system wide value
     when starting a GRASS session. Within a GRASS session, a temporary copy
     of this file will be used.
        
 
@@ -95,10 +101,10 @@ 
        List of selected (GRASS related) shell environment variables
        
   
        GRASS_ADDON_BASE
        
   
        [grass startup script]
         allows specifying additional GISBASE
     for local GRASS modules (normally installed as GRASS Addons
-    by g.extension module) extra to standard
+    by g.extension module) extra to standard
     distribution. The default on GNU/Linux
-    is $HOME/.grass8/addons, on MS
-    Windows %APPDATA%\Roaming\GRASS8\addons.
        
+    is $HOME/.grass8/addons, on MS
+    Windows %APPDATA%\Roaming\GRASS8\addons.
    • GRASS_ADDON_ETC
    [libgis, g.findetc]
    @@ -108,9 +114,9 @@

    List of selected (GRASS related) shell environment variables

    GRASS_COMPATIBILITY_TEST
    [libgis]
    By default it is not possible to run C modules with a libgis that has a - different GIS_H_VERSION, the compatibility test will exit with a + different GIS_H_VERSION, the compatibility test will exit with a fatal error. Setting this variable to 0 (zero) with - GRASS_COMPATIBILITY_TEST=0 allows the test to be passed with a + GRASS_COMPATIBILITY_TEST=0 allows the test to be passed with a warning.
    GRASS_COMPRESSOR
    @@ -119,7 +125,7 @@

    List of selected (GRASS related) shell environment variables

    environment variable GRASS_COMPRESSOR. Supported methods are RLE, ZLIB, LZ4, BZIP2, and ZSTD. The default is ZSTD if available, otherwise ZLIB, which can be changed with e.g. - GRASS_COMPRESSOR=ZSTD, granted that GRASS has been + GRASS_COMPRESSOR=ZSTD, granted that GRASS has been compiled with the requested compressor. Compressors that are always available are RLE, ZLIB, and LZ4. The compressors BZIP2 and ZSTD must be enabled when configuring GRASS for compilation.
    @@ -128,8 +134,8 @@

    List of selected (GRASS related) shell environment variables

    [grass startup script]
    specifies root path for GRASS configuration directory. If not specified, the default placement of the - configuration directory is used: $HOME on GNU/Linux, - $HOME/Library on Mac OS X, and %APPDATA% on MS Windows.
    + configuration directory is used: $HOME on GNU/Linux, + $HOME/Library on Mac OS X, and %APPDATA% on MS Windows.
    GRASS_DB_ENCODING
    [various modules, wxGUI]
    @@ -139,7 +145,7 @@

    List of selected (GRASS related) shell environment variables

    If set, GIS_ERROR_LOG should be the absolute path to the log file (a relative path will be interpreted relative to the process' cwd, not the cwd at the point the user set the variable). If not - set, $HOME/GIS_ERROR_LOG is used instead. The file will + set, $HOME/GIS_ERROR_LOG is used instead. The file will only be used if it already exists.
    GRASS_ERROR_MAIL
    @@ -149,7 +155,7 @@

    List of selected (GRASS related) shell environment variables

    GRASS_FONT
    [display drivers]
    specifies the font as either the name of a font from - $GISBASE/etc/fontcap (or alternative fontcap file + $GISBASE/etc/fontcap (or alternative fontcap file specified by GRASS_FONT_CAP), or alternatively the full path to a FreeType font file.
    @@ -160,7 +166,7 @@

    List of selected (GRASS related) shell environment variables

    GRASS_FONT_CAP
    [g.mkfontcap, d.font, display drivers]
    - specifies an alternative location (to $GISBASE/etc/fontcap) for + specifies an alternative location (to $GISBASE/etc/fontcap) for the font configuration file.
    GRASS_FULL_OPTION_NAMES
    @@ -169,10 +175,10 @@

    List of selected (GRASS related) shell environment variables

    a found string is not an exact match for the given string.
    GRASS_GUI
    -
    either text (text user interface), gtext (text - user interface with GUI welcome screen), or gui (graphical +
    either text (text user interface), gtext (text + user interface with GUI welcome screen), or gui (graphical user interface) to define non-/graphical startup. Can also specify - the name of the GUI to use, e.g. wxpython + the name of the GUI to use, e.g. wxpython (wxGUI). Also exists as a GRASS gisenv variable (see below). If this shell variable exists at GRASS startup, it will determine the GUI used. If it is not defined @@ -198,11 +204,11 @@

    List of selected (GRASS related) shell environment variables

    using RLE compression.

    If the variable doesn't exist, or the value is non-zero, zlib compression - will be used instead. Such rasters will have a compressed + will be used instead. Such rasters will have a compressed value of 2 in the cellhd file.

    Obviously, decompression is controlled by the - raster's compressed value, not the environment variable.
    + raster's compressed value, not the environment variable.
    GRASS_ZLIB_LEVEL
    [libgis]
    if the environment variable GRASS_ZLIB_LEVEL exists and its value can @@ -210,9 +216,9 @@

    List of selected (GRASS related) shell environment variables

    raster maps are compressed using zlib compression. This applies to all raster map types (CELL, FCELL, DCELL).

    - Valid zlib compression levels are -1 to 9. The GRASS_ZLIB_LEVEL=-1 corresponds - to the zlib default value (equivalent to GRASS_ZLIB_LEVEL=6). Often - GRASS_ZLIB_LEVEL=1 gives the best compromise between speed and compression. + Valid zlib compression levels are -1 to 9. The GRASS_ZLIB_LEVEL=-1 corresponds + to the zlib default value (equivalent to GRASS_ZLIB_LEVEL=6). Often + GRASS_ZLIB_LEVEL=1 gives the best compromise between speed and compression.

    If the variable doesn't exist, or the value cannot be parsed as an integer, zlib's default compression level 6 will be used.
    @@ -221,13 +227,13 @@

    List of selected (GRASS related) shell environment variables

    [various modules, wxGUI]
    it may be set to either
      -
    • standard - sets percentage output and message +
    • standard - sets percentage output and message formatting style to standard formatting,
      • -
    • gui - sets percentage output and message formatting +
    • gui - sets percentage output and message formatting style to GUI formatting,
      • -
    • silent - disables percentage output and error +
    • silent - disables percentage output and error messages,
      • -
    • plain - sets percentage output and message +
    • plain - sets percentage output and message formatting style to ASCII output without rewinding control characters.
    @@ -236,14 +242,14 @@

    List of selected (GRASS related) shell environment variables

    [various modules]
    swaps mouse buttons for two-button or left-handed mice. Its value has three digits 1, 2, and 3, which represent default left, middle, and right buttons - respectively. Setting to 132 will swap middle and right + respectively. Setting to 132 will swap middle and right buttons. Note that this variable should be set before a display driver is initialized (e.g., - d.mon x0).
    + d.mon x0).
    GRASS_PAGER
    [various modules]
    - it may be set to either less, more, or cat.
    + it may be set to either less, more, or cat.
    GRASS_PERL
    [used during install process for generating man pages]
    @@ -252,7 +258,7 @@

    List of selected (GRASS related) shell environment variables

    GRASS_PROXY
    [used during addon install/reinstall process for generating man pages (download commit from GitHub API server and remote modules.xml file)]
    - set the proxy with: GRASS_PROXY="http=<value>,ftp=<value>".
    + set the proxy with: GRASS_PROXY="http=<value>,ftp=<value>".
    GRASS_SKIP_MAPSET_OWNER_CHECK
    By default it is not possible to work with MAPSETs that are @@ -272,7 +278,7 @@

    List of selected (GRASS related) shell environment variables

    GRASS_PYTHON
    [wxGUI, Python Ctypes]
    set to override Python executable.
    - On Mac OS X this should be the pythonw executable for the + On Mac OS X this should be the pythonw executable for the wxGUI to work.
    GRASS_VECTOR_LOWMEM
    @@ -315,14 +321,14 @@

    List of selected (GRASS related) shell environment variables

    vector maps will be read (if found) also from this directory. It may be set to either:
      -
    • keep - the temporary vector map is not deleted when +
    • keep - the temporary vector map is not deleted when closing the map.
      • -
    • move - the temporary vector map is moved to the +
    • move - the temporary vector map is moved to the current mapset when closing the map.
      • -
    • delete - the temporary vector map is deleted when +
    • delete - the temporary vector map is deleted when closing the map.
    - Default value is keep. + Default value is keep. Note that temporary vector maps are not visible to the user via g.list @@ -332,7 +338,7 @@

    List of selected (GRASS related) shell environment variables

    GRASS_VECTOR_TMPDIR_MAPSET
    [vectorlib]
    By default GRASS temporary directory is located in - $LOCATION/$MAPSET/.tmp/$HOSTNAME. If GRASS_VECTOR_TMPDIR_MAPSET is + $LOCATION/$MAPSET/.tmp/$HOSTNAME. If GRASS_VECTOR_TMPDIR_MAPSET is set to '0', the temporary directory is located in TMPDIR (environmental variable defined by the user or GRASS initialization script if not given).
    @@ -473,7 +479,7 @@

    List of selected internal GRASS environment variables

    This variable is automatically created by g.parser so that the - --overwrite option will + --overwrite option will 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.
    @@ -489,7 +495,7 @@

    List of selected internal GRASS environment variables

  • 3 - additional verbose messages are printed
    • This variable is automatically created by g.parser - so that the --verbose or --quiet flags will be inherited + so that the --verbose or --quiet flags will be inherited by dependent modules as the script runs.
    GRASS_REGION
    @@ -501,7 +507,7 @@

    List of selected internal GRASS environment variables

    WIND_OVERRIDE
    [libgis]
    it causes programs to use the specified named region (created with - e.g. g.region save=...) to be used as the current region, instead of + e.g. g.region save=...) to be used as the current region, instead of the region from the WIND file.

    This allows programs such as the GUI to run external commands on an alternate region without having to modify the WIND file then change it @@ -535,7 +541,7 @@

    List of selected GRASS gisenv variables


    process id of the start-up shell script
    GUI
    -
    See GRASS_GUI environmental variable for details.
    +
    See GRASS_GUI environmental variable for details.
    LOCATION
    full path to project (previously called location) directory
    @@ -570,7 +576,7 @@

    List of selected GRASS gisenv variables

    This variable is automatically created by g.parser so that the - --overwrite option will + --overwrite option will 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. @@ -579,27 +585,27 @@

    List of selected GRASS gisenv variables

    GRASS-related Files

    -
    $HOME/.grass8/rc
    +
    $HOME/.grass8/rc
    stores the GRASS gisenv variables (not shell environment variables)
    -
    $HOME/.grass8/bashrc
    +
    $HOME/.grass8/bashrc
    stores the shell environment variables (Bash only)
    -
    $HOME/.grass8/env.bat
    +
    $HOME/.grass8/env.bat
    stores the shell environment variables (MS Windows only)
    -
    $HOME/.grass8/login
    +
    $HOME/.grass8/login
    stores the DBMI passwords in this hidden file. Only the file owner can access this file.
    -
    $HOME/GIS_ERROR_LOG
    +
    $HOME/GIS_ERROR_LOG
    if this file exists then all GRASS error and warning messages are logged here. Applies to current user. To generate the file, use: - touch $HOME/GIS_ERROR_LOG
    + touch $HOME/GIS_ERROR_LOG
    See also GIS_ERROR_LOG variable.
    -Note: On MS Windows the files are stored in %APPDATA%. +Note: On MS Windows the files are stored in %APPDATA%.

    SEE ALSO

    diff --git a/lib/pngdriver/pngdriver.html b/lib/pngdriver/pngdriver.html index 1b1f6b2a2cb..f22834c0c2e 100644 --- a/lib/pngdriver/pngdriver.html +++ b/lib/pngdriver/pngdriver.html @@ -41,7 +41,7 @@

    Environment variables

    sets true-color support. Default is TRUE.
  • GRASS_RENDER_FILE=filename
    - the filename to put the resulting image in, default is map.png. + the filename to put the resulting image in, default is map.png. If you set GRASS_RENDER_FILE to a filename which ends in ".ppm", a PPM file will be created (with alpha channel stored in a PGM image, if applicable). If you set GRASS_RENDER_FILE to a filename which ends in ".bmp", a 32-bpp @@ -51,11 +51,11 @@

    Environment variables

    compression level of PNG files (0 = none, 1 = fastest, 9 = best, default is 6)
  • GRASS_RENDER_FILE_READ
    - if TRUE, the PNG driver will initialize the image from + if TRUE, the PNG driver will initialize the image from the contents of GRASS_RENDER_FILE.
  • GRASS_RENDER_FILE_MAPPED
    - if TRUE, the PNG driver + if TRUE, the PNG driver will map GRASS_RENDER_FILE as its framebuffer, rather than using memory. This only works with BMP files.
    • @@ -72,7 +72,7 @@

    Example

    d.vect roadsmajor color=red -This writes a file named map.png in your current directory. +This writes a file named map.png in your current directory.

    NOTES

    @@ -83,14 +83,14 @@

    NOTES

    be installed for the PNG driver to work (it's worth it).

    The resolution of the output images is defined by current region -extents. Use g.region -p to get the number of rows and cols +extents. Use g.region -p to get the number of rows and cols and use the environment variables to set the image size. If you would like a larger image, multiply both rows and cols by the same whole number to preserve the aspect ratio.

    Further PNG file processing (e.g. quantization to 1 bit for monochrome -images) can be done with pnmquant of -the netpbm tools. +images) can be done with pnmquant of +the netpbm tools.

    SEE ALSO

    diff --git a/lib/psdriver/psdriver.html b/lib/psdriver/psdriver.html index 31af82fae88..da593702444 100644 --- a/lib/psdriver/psdriver.html +++ b/lib/psdriver/psdriver.html @@ -38,16 +38,16 @@

    Environment variables

    fit a standard paper size, see also GRASS_RENDER_WIDTH, GRASS_RENDER_HEIGHT.
  • GRASS_RENDER_PS_LANDSCAPE
    - if TRUE, the screen is rotated 90 degrees + if TRUE, the screen is rotated 90 degrees counter-clockwise so that a "landscape" screen fits better on "portrait" paper.
  • GRASS_RENDER_PS_HEADER
    - if FALSE, the output is appended to any existing file, + if FALSE, the output is appended to any existing file, and no prolog or setup sections are generated.
  • GRASS_RENDER_PS_TRAILER
    - if FALSE, no trailer section is generated. + if FALSE, no trailer section is generated.
    • @@ -61,12 +61,12 @@

    Example

    d.rast elevation d.vect roadsmajor color=red -This writes a file named map.ps in your current directory. +This writes a file named map.ps in your current directory.

    NOTES

    The resolution of the output files is defined by current region -extents. Use g.region -p to get the number of rows and cols +extents. Use g.region -p to get the number of rows and cols and use the environment variables to set the image size. If you would like a larger image, multiply both rows and cols by the same whole number to preserve the aspect ratio. @@ -75,7 +75,7 @@

    NOTES

    colorimage and setrgbcolor operators (this is the case for colour printers which pre-date level 2 PostScript). -

    Masked images (d.rast, d.rgb, d.his -n) +

    Masked images (d.rast, d.rgb, d.his -n) require PostScript level 3.

    SEE ALSO

    diff --git a/lib/vector/rtree/docs/sources.htm b/lib/vector/rtree/docs/sources.htm index 31e076775ff..7e597c4dba7 100644 --- a/lib/vector/rtree/docs/sources.htm +++ b/lib/vector/rtree/docs/sources.htm @@ -103,7 +103,7 @@

    Implementation of a simple C++ quaternion class called "Squat". Popularized by a seminal paper by Ken Shoemake, a quaternion represents a rotation about an axis.  Squats can be concatenated together via -the * and *= +the * and *= operators and converted back and forth between transformation matrices. Implementation also includes a wonderful 3D vector macro library by Don Hatch. diff --git a/lib/vector/vectorascii.html b/lib/vector/vectorascii.html index cae0ecef5a6..ed22e4e2200 100644 --- a/lib/vector/vectorascii.html +++ b/lib/vector/vectorascii.html @@ -43,7 +43,7 @@ [ LAYER CATEGORY] -Everything above in [ ] is optional. +Everything above in [ ] is optional.

    The primitive codes are as follows:

      @@ -76,18 +76,18 @@

      Latitude/Longitude data may be given in a number of ways. Decimal degrees must be positive or negative instead of using a hemisphere letter. Mixed coordinates must use a hemisphere letter. Whole minutes and -seconds must always contain two digits (example: use 167:03:04.567; -and not 167:3:4.567). +seconds must always contain two digits (example: use 167:03:04.567; +and not 167:3:4.567).

      Acceptable formats:
      key: D=Degrees; M=Minutes; S=Seconds; h=Hemisphere (N,S,E,W)

        -
      • (+/-)DDD.DDDDD
        • -
      • DDDh
        • -
      • DDD:MMh
        • -
      • DDD:MM.MMMMMh
        • -
      • DDD:MM:SSh
        • -
      • DDD:MM:SS.SSSSSh
        • +
      • (+/-)DDD.DDDDD
        • +
      • DDDh
        • +
      • DDD:MMh
        • +
      • DDD:MM.MMMMMh
        • +
      • DDD:MM:SSh
        • +
      • DDD:MM:SS.SSSSSh

      EXAMPLES

      @@ -132,5 +132,6 @@

      SEE ALSO

      v.in.ascii, v.out.ascii, - v.edit + v.edit, + v.support diff --git a/macosx/ReadMe.md b/macosx/ReadMe.md index fa9c13b1aff..2e9e05e4620 100644 --- a/macosx/ReadMe.md +++ b/macosx/ReadMe.md @@ -374,7 +374,7 @@ sudo ln -sf /Library/Frameworks/Tk.framework/Versions/8.5/libtkstub8.5.a \ ### Universal GPSBabel A universal GPSBabel CLI executable is now included in the OSX binary -from [www.gpsbabel.org](http://www.gpsbabel.org/). This does not need to +from [www.gpsbabel.org](https://www.gpsbabel.org/). This does not need to be 64bit. ### Universal NetPBM @@ -700,4 +700,4 @@ This program is free software under the GNU General Public License (>=v2). - + diff --git a/macosx/pkg/resources/ReadMe.rtf b/macosx/pkg/resources/ReadMe.rtf index 38cd111f3b1..c18857bf849 100644 --- a/macosx/pkg/resources/ReadMe.rtf +++ b/macosx/pkg/resources/ReadMe.rtf @@ -253,6 +253,6 @@ This program is free software under the GNU General Public License (>=v2).} - William Kyngesburye} \par \pard\plain \s0\nowidctlpar{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\cf0\kerning1\dbch\af7\langfe2052\dbch\af8\afs24\alang1081\loch\f3\fs24\lang1033\ql\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640{{\field{\*\fldinst HYPERLINK "mailto:kyngchaos@kyngchaos.com" }{\fldrslt \cf2\ul\ulc0\langfe255\alang255\lang255\cf1\i0\ulnone\ulc0\b0\rtlch \ltrch\loch\fs28\loch\f5 kyngchaos@kyngchaos.com}}} -\par \pard\plain \s0\nowidctlpar{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\cf0\kerning1\dbch\af7\langfe2052\dbch\af8\afs24\alang1081\loch\f3\fs24\lang1033\ql\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640{{\field{\*\fldinst HYPERLINK "http://www.kyngchaos.com" }{\fldrslt \cf2\ul\ulc0\langfe255\alang255\lang255\cf1\i0\ulnone\ulc0\b0\rtlch \ltrch\loch\fs28\loch\f5 -http://www.kyngchaos.com/}}} +\par \pard\plain \s0\nowidctlpar{\*\hyphen2\hyphlead2\hyphtrail2\hyphmax0}\cf0\kerning1\dbch\af7\langfe2052\dbch\af8\afs24\alang1081\loch\f3\fs24\lang1033\ql\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640{{\field{\*\fldinst HYPERLINK "https://www.kyngchaos.com" }{\fldrslt \cf2\ul\ulc0\langfe255\alang255\lang255\cf1\i0\ulnone\ulc0\b0\rtlch \ltrch\loch\fs28\loch\f5 +https://www.kyngchaos.com/}}} \par } diff --git a/misc/m.cogo/m.cogo.html b/misc/m.cogo/m.cogo.html index 28fcc6e4703..4135ed91ecc 100644 --- a/misc/m.cogo/m.cogo.html +++ b/misc/m.cogo/m.cogo.html @@ -80,7 +80,7 @@

      EXAMPLES

      m.cogo -l in=cogo.dat -Where the cogo.dat input file looks like: +Where the cogo.dat input file looks like: 
       # Sample COGO input file -- This defines an area.
 # <label> <bearing> <distance>
@@ -135,7 +135,7 @@ 
      EXAMPLES
      If necessary, snap the boundary closed with the v.clean module. -Use tool=snap and thresh=0.0001, or some small value. +Use tool=snap and thresh=0.0001, or some small value.

      SEE ALSO

      diff --git a/misc/m.transform/m.transform.html b/misc/m.transform/m.transform.html index e2f237cc832..b80490b39e7 100644 --- a/misc/m.transform/m.transform.html +++ b/misc/m.transform/m.transform.html @@ -5,7 +5,7 @@

      DESCRIPTION

      If coordinates are given with the input file option or fed from -stdin, both the input and the output format is "x y" with one +stdin, both the input and the output format is "x y" with one coordinate pair per line. Reverse transform is performed with the -r flag. @@ -21,44 +21,46 @@

      NOTES

      The transformations are:

      order=1: 

      -    e = [E0 E1][1].[1]
+    e = [E0 E1][1]·[1]
         [E2  0][e] [n]
 
-    n = [N0 N1][1].[1]
+    n = [N0 N1][1]·[1]
         [N2  0][e] [n]
      order=2: 
           e = [E0 E1 E3][1 ] [1 ]
-        [E2 E4  0][e ].[n ]
+        [E2 E4  0][e ]·[n ]
         [E5  0  0][e²] [n²]
 
     n = [N0 N1 N3][1 ] [1 ]
-        [N2 N4  0][e ].[n ]
+        [N2 N4  0][e ]·[n ]
         [N5  0  0][e²] [n²]
      order=3: 
           e = [E0 E1 E3 E6][1 ] [1 ]
-        [E2 E4 E7  0][e ].[n ]
+        [E2 E4 E7  0][e ]·[n ]
         [E5 E8  0  0][e²] [n²]
         [E9  0  0  0][e³] [n³]
 
     n = [N0 N1 N3 N6][1 ] [1 ]
-        [N2 N4 N7  0][e ].[n ]
+        [N2 N4 N7  0][e ]·[n ]
         [N5 N8  0  0][e²] [n²]
         [N9  0  0  0][e³] [n³]
      -["." = dot-product, (AE).N = N'EA.] -

      In other words, order=1 and order=2 are equivalent to order=3 with -the higher coefficients equal to zero. +["·" = dot-product, (AE)·N = N'EA] + +

      In other words, order=1 and order=2 are equivalent +to order=3 with the higher coefficients equal to zero.

      SEE ALSO

      +i.ortho.transform, i.rectify, v.rectify, v.transform diff --git a/ps/ps.map/ps.map.html b/ps/ps.map/ps.map.html index 8245e909c21..c4d1c5a00b6 100644 --- a/ps/ps.map/ps.map.html +++ b/ps/ps.map/ps.map.html @@ -14,7 +14,7 @@

      NOTES

      vpoints entry first. Raster maps are always drawn first, and only a single raster map (or 3 if part of a RGB group) may be used. -

      The hash character ('#') may be used at the beginning of a line +

      The hash character ('#') may be used at the beginning of a line to indicate that the line is a comment. Blank lines will also be ignored.

      Be aware that some mapping instructions require the end command @@ -29,7 +29,7 @@

      NOTES

      US-Letter sized paper at 600dpi, with 1" margins and the raster filling the entire page, the usable area on the page will be 6.5" x 9", which at 600 dots/inch is equivalent to a region of 3900 columns x 5400 rows (see -"g.region -p"). Any higher resolution settings will make the +"g.region -p"). Any higher resolution settings will make the output file larger, but with a consumer printer you probably won't be able to resolve any better detail in the hardcopy. @@ -41,11 +41,11 @@

      NOTES

      One point ("pixel") is 1/72 of an inch.

      For users wanting to use special characters (such as accented characters) it -is important to note that ps.map uses ISO-8859-1 encoding. +is important to note that ps.map uses ISO-8859-1 encoding. This means that your instructions file will have to be encoded in this encoding. If you normally work in a different encoding environment (such as -UTF-8), you have to transform your file to the ISO-8859-1 -encoding, for example by using the iconv utility: +UTF-8), you have to transform your file to the ISO-8859-1 +encoding, for example by using the iconv utility: 

       iconv -f UTF-8 -t ISO_8859-1 utf_file > iso_file
@@ -116,7 +116,7 @@ 
      Common instructions
      
 
 
      The name of the PostScript font.
 Fonts present in all PostScript implementations are:
-
+
 Times-Roman,
 Times-Italic,
 Times-Bold,
@@ -129,7 +129,7 @@ 
      Common instructions
      
 Courier-Oblique,
 Courier-Bold,
 and
-Courier-BoldOblique      .
+Courier-BoldOblique.
 
      
 The default is Helvetica.
 
      
@@ -145,7 +145,7 @@ 
      Common instructions
      
 
      color name
 
 
      The following colors names are accepted by ps.map:
-
+
 aqua,
 black,
 blue,
@@ -162,10 +162,10 @@ 
      Common instructions
      
 violet,
 white,
 yellow
-      .
+.
 

      
 For vectors and some plotting commands you can also specify
-'none' or 'R:G:B' (e.g '255:0:0').
+'none' or 'R:G:B' (e.g '255:0:0').
 
      
 
 
      yes|no
@@ -197,7 +197,7 @@ 
      border
      
 in which case it is measured in inches.
 The default is a black border box of width 1 point.
 
      The border can be turned off completely with the
-"border n" instruction. In this case
+"border n" instruction. In this case
 the end command should not be given as the
 main command will be treated as a single line instruction.
 
      
@@ -245,7 +245,7 @@ 
      colortable
      
 The default text color is black.
 
      
 Omitting the colortable instruction would result in no color table.
-If the colortable is turned off with a "colortable N"
+If the colortable is turned off with a "colortable N"
 instruction the end command should not be given as the
 main command will be treated as a single line instruction.
 
      
@@ -321,7 +321,7 @@ 
      comments
      
 starting at the left margin. The default text color is black.
 
      If you wish to use parentheses spanning multiple lines you will need to
 quote them with a backslash to prevent the PostScript interpreter from
-getting confused. e.g. '\(' and '\)'
+getting confused. e.g. '\(' and '\)'
 
 
      
 This example prints in blue
@@ -527,17 +527,17 @@ 
      header
      
 of the text in the text file specified, with some special formatting keys:
 
 
        
-
      • %%  - a literal %
        • 
-
      • %n  - ? newline ?
        • 
-
      • %_  - horizontal bar
        • 
-
      • %c  - "<raster name> in mapset <mapset name>"
        • 
-
      • %d  - today's date
        • 
-
      • %l  - project name
        • 
-
      • %L  - project's text description
        • 
-
      • %m  - mapset name
        • 
-
      • %u  - user name
        • 
-
      • %x  - mask info
        • 
-
      • %-  - advance to this character column number (see example below)
        • 
+
      • %%  - a literal %
        • 
+
      • %n  - ? newline ?
        • 
+
      • %_  - horizontal bar
        • 
+
      • %c  - "<raster name> in mapset <mapset name>"
        • 
+
      • %d  - today's date
        • 
+
      • %l  - project name
        • 
+
      • %L  - project's text description
        • 
+
      • %m  - mapset name
        • 
+
      • %u  - user name
        • 
+
      • %x  - mask info
        • 
+
      • %-  - advance to this character column number (see example below)
        • 
 
      
 
 Example header file:
@@ -556,7 +556,7 @@ 
      header
      
 
 
      
 This example prints (in red) whatever is in the file soils.hdr above
-the map, using a 20/72 inch Courier font.
+the map, using a 20/72 inch Courier font.
 
       EXAMPLE:
     header
@@ -657,7 +657,7 @@ 
      mapinfo
      
 
      
 This example prints (in brown) the scale, grid and region information
 immediately below the map and starting 1.5 inches from the left edge
-of the page, using a 12/72 inch Courier font.
+of the page, using a 12/72 inch Courier font.
 
 
       EXAMPLE:
@@ -1097,8 +1097,8 @@ 
      setcolor
      
 can be requested more than once to override the default color for additional
 categories.  More than one category can be changed for each request by listing
 all the category values separated by commas (but with no spaces). Also ranges
-can be included, for example "1,2,6-10,12". Colors for "null" and the
-"default" (i.e. out-of-range) color may also be reassigned.
+can be included, for example "1,2,6-10,12". Colors for "null" and the
+"default" (i.e. out-of-range) color may also be reassigned.
 
      
 
 
@@ -1133,7 +1133,7 @@ 
      text
      
 
      The user can then specify various text features:
 
      font:
 the PostScript font. Common possibilities are listed at the start of this
-help page. The default is Helvetica.
+help page. The default is Helvetica.
 
      color
 (see NAMED COLORS);
 
      width
@@ -1227,7 +1227,7 @@ 
      vareas
      
 for more information on the mask)
 
      cats - which categories should be plotted (default is all);
 
      where - select features using a SQL where statement.
-For example: vlastnik = 'Cimrman';
+For example: vlastnik = 'Cimrman';
 
      label - for description in vlegend.
 Default is: map(mapset);
 
      lpos - position vector is plotted in legend. If lpos is
@@ -1242,7 +1242,7 @@ 
      vareas
      
 until overwritten in the pattern file -->. Color of the boundaries remain set
 by the color instruction.
 Pattern may be scaled with the scale command. Several standard hatching
-patterns are provided in $GISBASE/etc/paint/patterns/.
+patterns are provided in $GISBASE/etc/paint/patterns/.
 Demonstrative images can be found on the
 GRASS Wiki site.
 
diff --git a/python/grass/docs/src/gunittest_testing.rst b/python/grass/docs/src/gunittest_testing.rst
index 62f258f99c8..20df0245e7e 100644
--- a/python/grass/docs/src/gunittest_testing.rst
+++ b/python/grass/docs/src/gunittest_testing.rst
@@ -387,7 +387,7 @@ in different locations.
 .. todo::
     Add example of assertions of key-value results.
 
-Especially if a module module has a lot of different parameters allowed
+Especially if a module has a lot of different parameters allowed
 in different combinations, you should test the if the wrong ones are really
 disallowed and proper error messages are provided (in addition, you can
 test things such as creation and removal of maps in error states).
diff --git a/raster/r.buffer/r.buffer.html b/raster/r.buffer/r.buffer.html
index e0033f0345c..c8a3913b95a 100644
--- a/raster/r.buffer/r.buffer.html
+++ b/raster/r.buffer/r.buffer.html
@@ -32,10 +32,10 @@ 
      NOTES
      
 
 The user has the option of identifying up to 250 continuous zones.
 The zones are identified by specifying the upper limit of each desired
-zone (r.buffer assumes that 0 is the starting
+zone (r.buffer assumes that 0 is the starting
 point).  "Continuous" is used in the sense that each category zone's
 lower value is the previous zone's upper value. The first buffer zone
-always has distance 0 as its lower bound. Buffer distances
+always has distance 0 as its lower bound. Buffer distances
 can be specified using one of five units with the units parameter.
 
 
      
diff --git a/raster/r.buildvrt/r.buildvrt.html b/raster/r.buildvrt/r.buildvrt.html
index d5118ba5150..f69ebd1e8ef 100644
--- a/raster/r.buildvrt/r.buildvrt.html
+++ b/raster/r.buildvrt/r.buildvrt.html
@@ -22,7 +22,7 @@ 
      NOTES
      
 
 
      
 A GRASS virtual raster can be regarded as a simplified version of GDAL's
-virtual raster format.
+virtual raster format.
 The GRASS equivalent is simpler because issues like nodata, projection,
 resolution, resampling, masking are already handled by native GRASS
 raster routines.
@@ -72,7 +72,7 @@ 
      SEE ALSO
      
 
      
 The equivalent GDAL utility
 
-gdalbuildvrt
+gdalbuildvrt
 
 
 
      AUTHOR
      
diff --git a/raster/r.carve/r.carve.html b/raster/r.carve/r.carve.html
index f10fdcb6312..3d36aa45256 100644
--- a/raster/r.carve/r.carve.html
+++ b/raster/r.carve/r.carve.html
@@ -118,7 +118,7 @@ 
      KNOWN ISSUES
      
 
 
      REFERENCES
      
 
-Terrain
+Terrain
 modeling and Soil Erosion Simulations for Fort Hood and Fort Polk test
 areas, by Helena Mitasova, Lubos Mitas, William M. Brown, Douglas
 M.  Johnston, GMSL (Report for CERL 1999)
diff --git a/raster/r.category/r.category.html b/raster/r.category/r.category.html
index b0d5dc7c9bb..7c40974aa51 100644
--- a/raster/r.category/r.category.html
+++ b/raster/r.category/r.category.html
@@ -45,7 +45,7 @@ 
      Input from a file
      
 val1:val2:Label
 
      
 
-If the filename is given as "-", the category labels are read from stdin
+If the filename is given as "-", the category labels are read from stdin
 
 
      Default and dynamic category labels
      
 
@@ -68,26 +68,26 @@ 
      Default and dynamic category labels
      
 
      
 
      In the format line
 
        
-
      • $1 refers to the value num*5.0+1000 (ie, using the first 2 coefficients)
        • 
-
      • $2 refers to the value num*5.0+1005 (ie, using the last 2 coefficients)
        • 
+
      • $1 refers to the value num*5.0+1000 (ie, using the first 2 coefficients)
        • 
+
      • $2 refers to the value num*5.0+1005 (ie, using the last 2 coefficients)
        • 
 
      
-  $1.2 will print $1 with 2 decimal places.
-
      Also, the form $?xxx$yyy$ translates into yyy if the category is 1, xxx
-otherwise. The $yyy$ is optional. Thus
-
        $1 meter$?s
+  $1.2 will print $1 with 2 decimal places.
+
      Also, the form $?xxx$yyy$ translates into yyy if the category is 1, xxx
+otherwise. The $yyy$ is optional. Thus
+
        $1 meter$?s
 
      will become: 
      
-  1 meter (for category 1)
      
-  2 meters (for category 2), etc.
+  1 meter (for category 1)
      
+  2 meters (for category 2), etc.
 
 
      
-format='Elevation: $1.2 to $2.2 feet'   ## Format Statement
      
-coefficients="5.0,1000,5.0,1005"	## Coefficients
+format='Elevation: $1.2 to $2.2 feet'   ## Format Statement
      
+coefficients="5.0,1000,5.0,1005"	## Coefficients
 
 
      The format and coefficients above would be used to generate the
 following statement in creation of the format appropriate category
 string for category "num":
 
      
-sprintf(buff,"Elevation: %.2f to %.2f feet", num*5.0+1000, num*5.0*1005)
+sprintf(buff,"Elevation: %.2f to %.2f feet", num*5.0+1000, num*5.0*1005)
 
 
      Note: while both the format and coefficient lines must be present
       a blank line for the format string will effectively suppress
@@ -99,9 +99,9 @@ 
      Default and dynamic category labels
      
 know that i-th rule maps fp range to i, thus we know for sure
 that cats.labels[i] corresponds to i-th quant rule
 -->
-
      To use a "$" in the label without triggering the plural test,
-put "$$" in the format string.
-
      Use 'single quotes' when using a "$" on the command line to
+
      To use a "$" in the label without triggering the plural test,
+put "$$" in the format string.
+
      Use 'single quotes' when using a "$" on the command line to
 avoid unwanted shell substitution.
 
 
      EXAMPLES
      
@@ -133,7 +133,7 @@ 
      Printing categories
      prints only the category values and labels for landclass96 map layer -categories 2 and 5 through 7. +categories 2 and 5 through 7. 

      @@ -143,7 +143,7 @@ 
      Printing categories
      prints the values and labels for landclass96 map layer categories -3 and 4, but uses "," (instead of a tab) +3 and 4, but uses "," (instead of a tab) as the character separating the category values from the category values in the output. diff --git a/raster/r.circle/r.circle.html b/raster/r.circle/r.circle.html index b3ed725fc84..dc1b4c9d34f 100644 --- a/raster/r.circle/r.circle.html +++ b/raster/r.circle/r.circle.html @@ -1,6 +1,6 @@

      DESCRIPTION

      -This module creates an output raster map centered on the x,y values specified +r.circle creates an output raster map centered on the x,y values specified with the coordinate parameter, out to the edge of the current region. The output cell values increase linearly from the specified center. The min and max parameters control the inner and outer output raster map radii, respectively. diff --git a/raster/r.coin/r.coin.html b/raster/r.coin/r.coin.html index bbaf260df83..4b7dc3af0eb 100644 --- a/raster/r.coin/r.coin.html +++ b/raster/r.coin/r.coin.html @@ -18,17 +18,16 @@

      DESCRIPTION

      units of measure in which the report results can be given. These units are: -

      -

      -
      c
      cells -
      p
      percent cover of region -
      x
      percent of <map name> category (column) -
      y
      percent of <map name> category (row) -
      a
      acres -
      h
      hectares -
      k
      square kilometers -
      m
      square miles -
      +
        +
      • c: cells
        • +
      • p: percent cover of region
        • +
      • x: percent of <map name> category (column)
        • +
      • y: percent of <map name> category (row)
        • +
      • a: acres
        • +
      • h: hectares
        • +
      • k: square kilometers
        • +
      • m: square miles
        • +

      Note that three of these options give results as percentage @@ -188,7 +187,7 @@

      SEE ALSO

      g.region, - + r.category, r.describe, r.reclass, diff --git a/raster/r.colors/r.colors.html b/raster/r.colors/r.colors.html index 8fdf83d1313..3762adda465 100644 --- a/raster/r.colors/r.colors.html +++ b/raster/r.colors/r.colors.html @@ -71,7 +71,7 @@

      DESCRIPTION

      certain ranges. One can get a rough idea of the applicability of a colour table by reading the -corresponding rules file ($GISBASE/etc/colors/<name>). +corresponding rules file ($GISBASE/etc/colors/<name>). For example the slope rule is defined as: 
      @@ -231,14 +231,14 @@ 
      DESCRIPTION
      
 
 
      NOTES
      
 
-All color tables are stored in $GISBASE/etc/colors/. Further
+All color tables are stored in $GISBASE/etc/colors/. Further
 user-defined color tables can also be stored in this directory for
 access from the color parameter or in a user defined directory.
 See also r.colors.out for printing color tables easily to the
 terminal.
 
      
 The color table assigned to a raster map is stored in
-$GISDBASE/location/mapset/colr/.
+$GISDBASE/location/mapset/colr/.
 
 
      EXAMPLES
      
 
@@ -309,7 +309,7 @@ 
      SEE ALSO
      
 page Color
 tables (from GRASS User Wiki)
 
-
      ColorBrewer is an online tool designed to
+
      ColorBrewer is an online tool designed to
 help people select good color schemes for maps and other graphics.
 
 
      AUTHORS
      
diff --git a/raster/r.colors/r3.colors.html b/raster/r.colors/r3.colors.html
index c4e65a62bee..16b35b76b1d 100644
--- a/raster/r.colors/r3.colors.html
+++ b/raster/r.colors/r3.colors.html
@@ -24,7 +24,7 @@ 
      SEE ALSO
      
 page Color
 tables (from GRASS User Wiki)
 
-
      ColorBrewer is an online tool designed to
+
      ColorBrewer is an online tool designed to
 help people select good color schemes for maps and other graphics.
 
 
      AUTHORS
      
diff --git a/raster/r.compress/r.compress.html b/raster/r.compress/r.compress.html
index 5a95a970bbf..665015e2cc4 100644
--- a/raster/r.compress/r.compress.html
+++ b/raster/r.compress/r.compress.html
@@ -10,13 +10,13 @@ 
      DESCRIPTION
      
 method if available, otherwise ZLIB compression is used (see below).
 Related no data files (i.e.: NULL files), if present, are compressed by
 default unless a specific environment variable is set to explicitly
-disable NULL file compression (GRASS_COMPRESS_NULLS, see
+disable NULL file compression (GRASS_COMPRESS_NULLS, see
 below).
 
 
      
 During compression or re-compression, r.compress compresses
 raster maps using the method specified by means of the environment
-variable GRASS_COMPRESSOR. The default compression method is
+variable GRASS_COMPRESSOR. The default compression method is
 ZSTD if available, otherwise ZLIB's "deflate" algorithm (LZ77-based).
 Raster maps that contain very little information (such as boundary,
 geology, soils and land use maps) can be greatly reduced in size. Some
@@ -37,10 +37,10 @@ 
      DESCRIPTION
      
 
 
      
 Raster maps that are already compressed might be compressed again,
-either by setting a different method with GRASS_COMPRESSOR
+either by setting a different method with GRASS_COMPRESSOR
 (supported methods: RLE, ZLIB, LZ4, BZIP2, ZSTD) or, for the case of
 ZLIB compression, by changing the compression level with the
-environment variable GRASS_ZLIB_LEVEL.
+environment variable GRASS_ZLIB_LEVEL.
 
 
      
 Compressed raster maps may be decompressed using r.compress
@@ -51,7 +51,7 @@ 
      DESCRIPTION
      
 
      
 Information about the compression method and data type of the input
 raster map(s) can be printed in shell style with the -g flag. In
-this case, the module prints to stdout one line per input map
+this case, the module prints to stdout one line per input map
 with the fields "input map name", "data type",
 "name of data compression method", "NULL file
 compression" separated by the pipe character. NULL file
@@ -73,27 +73,27 @@ 
      TERMINOLOGY
      
 
      OVERVIEW OF AVAILABLE COMPRESSION ALGORITHMS
      
 
 The following compression methods are available (set by
-export GRASS_COMPRESSOR=method):
+export GRASS_COMPRESSOR=method):
 
 
        
-
      • NONE (uncompressed)
        • 
-
      • RLE  (generic Run-Length Encoding of single bytes; deprecated)
        • 
-
      • ZLIB (DEFLATE, good speed and compression)
+
      • NONE (uncompressed)
        • 
+
      • RLE  (generic Run-Length Encoding of single bytes; deprecated)
        • 
+
      • ZLIB (DEFLATE, good speed and compression)
 
          
-
        • with zlib compression levels (export GRASS_ZLIB_LEVEL=X): -1..9
+
        • with zlib compression levels (export GRASS_ZLIB_LEVEL=X): -1..9
    (-1 is default which corresponds to ZLIB level 6)
          • 
-
        • note: export GRASS_ZLIB_LEVEL=0 is equal to copying the data
+
        • note: export GRASS_ZLIB_LEVEL=0 is equal to copying the data
     as-is from source to destination
          • 
 
        
 
        • 
-
      • LZ4  (fastest, low compression)
        • 
-
      • BZIP2 (slowest, high compression)
        • 
-
      • ZSTD (compared to ZLIB, faster and higher compression,
+
      • LZ4  (fastest, low compression)
        • 
+
      • BZIP2 (slowest, high compression)
        • 
+
      • ZSTD (compared to ZLIB, faster and higher compression,
 much faster decompression - default compression)
        • 
 
      
 
 Important: the NULL file compression can be turned off with
-export GRASS_COMPRESS_NULLS=0. Raster maps with NULL file
+export GRASS_COMPRESS_NULLS=0. Raster maps with NULL file
 compression can only be opened with GRASS GIS 7.2.0 or later. NULL file
 compression for a particular raster map can be managed with r.null -z.
 The NULL file compression is using the LZ4 method as being the best compromise
@@ -104,11 +104,11 @@ 
      COMPRESSION ALGORITHM DETAILS
      
 
 All GRASS GIS raster map types are by default ZSTD compressed if
 available, otherwise ZLIB compressed. Through the environment variable
-GRASS_COMPRESSOR the compression method can be set to RLE,
+GRASS_COMPRESSOR the compression method can be set to RLE,
 ZLIB, LZ4, BZIP2, or ZSTD.
 
      
 Integer (CELL type) raster maps can be compressed with RLE if
-the environment variable GRASS_COMPRESSOR exists and is set to
+the environment variable GRASS_COMPRESSOR exists and is set to
 RLE. However, this is not recommended.
 
      
 Floating point (FCELL, DCELL) raster maps never use RLE compression;
@@ -133,7 +133,7 @@ 
      COMPRESSION ALGORITHM DETAILS
      
 compression level which is the best compromise between speed and
 compression ratio, also when compared to other available compression
 methods. Valid levels are in the range [1, 9] and can be set with the
-environment variable GRASS_ZLIB_LEVEL.
+environment variable GRASS_ZLIB_LEVEL.
 
      LZ4
      
 
      LZ4 is a very fast compression method, about as fast as no
 compression. Decompression is also very fast. The compression ratio is
@@ -160,7 +160,7 @@ 
      NOTES
      
 
      Compression method number scheme
      
 
 The used compression method is encoded with numbers. In the internal
-cellhd file, the value for "compressed" is 1 for RLE, 2
+cellhd file, the value for "compressed" is 1 for RLE, 2
 for ZLIB, 3 for LZ4, 4 for BZIP2, and 5 for ZSTD.
 
      
 Obviously, decompression is controlled by the raster map's compression,
@@ -185,7 +185,7 @@ 
      Formats
      
 
 
      ZLIB compression levels
      
 
-If the environment variable GRASS_ZLIB_LEVEL exists and
+If the environment variable GRASS_ZLIB_LEVEL exists and
 its value can be parsed as an integer, it determines the compression
 level used when newly generated raster maps are compressed using ZLIB
 compression. This applies to all raster map types (CELL, FCELL, DCELL).
@@ -273,9 +273,9 @@ 
      SEE ALSO
      
 
      
 Compression algorithms:
 bzip2,
-LZ4,
-zlib,
-zstd
+LZ4,
+zlib,
+zstd
 
 
      AUTHORS
      
 
diff --git a/raster/r.cost/r.cost.html b/raster/r.cost/r.cost.html
index e5118d98aea..db5343ec650 100644
--- a/raster/r.cost/r.cost.html
+++ b/raster/r.cost/r.cost.html
@@ -53,10 +53,10 @@ 
      OPTIONS
      
 use the --v verbose flag to track progress.
 
      
 The Knight's move (-k flag) may be used to improve the accuracy of
-the output. In the diagram below, the center location (O) represents a
+the output. In the diagram below, the center location (O) represents a
 grid cell from which cumulative distances are calculated. Those
-neighbors marked with an X are always considered for cumulative cost
-updates. With the -k option, the neighbors marked with a K are
+neighbors marked with an X are always considered for cumulative cost
+updates. With the -k option, the neighbors marked with a K are
 also considered.
 
 
      @@ -135,7 +135,7 @@ 
      NULL CELLS
      
 the algorithm, and thus retained in the output map.
 
      
 If one wants r.cost to transparently cross any region of null cells,
-the null_cost=0.0 option should be used. Then null cells just
+the null_cost=0.0 option should be used. Then null cells just
 propagate the adjacent costs. These cells can be retained as null cells in the
 output map by using the -n flag.
 
diff --git a/raster/r.covar/r.covar.html b/raster/r.covar/r.covar.html
index 87f1345d7e7..a510bb39c7a 100644
--- a/raster/r.covar/r.covar.html
+++ b/raster/r.covar/r.covar.html
@@ -17,9 +17,9 @@ 
      NOTES
      
 N real eigen values and N eigen vectors (each composed of N real numbers).
 
 
      
-The module m.eigensystem
+The module m.eigensystem
 in GRASS GIS Addons
-can be compiled and used to generate the eigen values and vectors.
+can be installed and used to generate the eigenvalues and vectors.
 
 
      EXAMPLE
      
 
diff --git a/raster/r.describe/r.describe.html b/raster/r.describe/r.describe.html
index d0f98692bad..a8627d4f329 100644
--- a/raster/r.describe/r.describe.html
+++ b/raster/r.describe/r.describe.html
@@ -12,7 +12,7 @@ 
      DESCRIPTION
      
 also ignore the current geographic region
 and mask.
 
-
      The nv parameter sets the string to be used to represent NULL
+
      The nv parameter sets the string to be used to represent NULL
 values in the module output; the default is '*'.
 
 
      The nsteps parameter sets the number of quantisation steps to divide into
@@ -36,33 +36,36 @@ 
      FLAGS
      
 
 
      If the -1 flag is specified, the output appears with one category value/range per line.
 
-
      The -n flag suppresses the reporting of NULL values.
+
      The -n flag suppresses the reporting of NULL values.
 
 
      EXAMPLES
      
 
 The following examples are from the Spearfish60 sample dataset:
 
-
      
-# Print the full list of raster map categories:
+
      Print the full list of raster map categories
      
+
 
       r.describe landcover.30m
 * 11 21-23 31 32 41-43 51 71 81-83 85 91 92
 
      
-
      
-# Print the raster range only:
+
+
      Print the raster range only
      
+
 
       r.describe -r landcover.30m
 11 thru 92
 *
 
      
 
-# Print raster map category range, suppressing nulls:
+
      Print raster map category range, suppressing nulls
      
+
 
       r.describe -n landcover.30m
 11 21-23 31 32 41-43 51 71 81-83 85 91 92
 
      
-
      
-# Print raster map categories, one category per line:
+
+
      Print raster map categories, one category per line
      
+
 
       r.describe -1 geology
 
@@ -77,7 +80,7 @@ 
      EXAMPLES
      
 8
 9
 
      
-
      
+
 
      SEE ALSO
      
 
 
diff --git a/raster/r.fill.stats/r.fill.stats.html b/raster/r.fill.stats/r.fill.stats.html
index bd966fa3f05..c8414796e73 100644
--- a/raster/r.fill.stats/r.fill.stats.html
+++ b/raster/r.fill.stats/r.fill.stats.html
@@ -77,7 +77,7 @@ 
      DESCRIPTION
      
 
 The images below show a gradiometer dataset with gaps and its
 interpolated equivalent, produced using the spatially weighted mean
-operator (mode="wmean").
+operator (mode="wmean").
 
 
      
 
@@ -132,7 +132,7 @@ 
      Usage
      
 increasing distance from the latter. Another way of explaining this
 effect is to state that larger "power" settings result in more
 localized interpolation, smaller ones in more globalized interpolation.
-The default setting is power=2.0.
+The default setting is power=2.0.
 
 
      
 
@@ -171,7 +171,7 @@ 
      Usage
      
 neighborhood (defined by the search radius distance) that
 contain a value in the input map, multiplied by their weights,
 and dividing the result by the sum of all weights in the neighborhood.
-For mode=wmean, this means that interpolated output cells that
+For mode=wmean, this means that interpolated output cells that
 were computed from many nearby input cells have very low uncertainty
 and vice versa. For all other modes, all weights in the neighborhood
 are constant "1" and the uncertainty measure is a simple measure of how
@@ -198,7 +198,7 @@ 
      Smoothing
      
 
 
      
 Effect of smoothing the original data: The top row shows a gap-filled surface computed from a rasterized Lidar point
-cloud (using mode=wmean and power=2), and the derived slope, aspect,
+cloud (using mode=wmean and power=2), and the derived slope, aspect,
 and profile curvature maps. The smoothing effect is clearly visible.
 The bottom row shows the effect of setting the -k flag: Preserving the original
 cell values in the interpolated output produces and unsmoothed, noisy surface, and likewise
@@ -292,11 +292,11 @@ 
      Spatial weighting scheme
      
 
      
 
 Note that the weights in such a small window drop rapidly for the
-default setting of power=2.
+default setting of power=2.
 
 
      
 
-If the distance is given in map units (flag -m), then the
+If the distance is given in map units (flag -m), then the
 search window can be modeled more accurately as a circle. The
 illustration below shows the precomputed weights for a distance in map
 units that is approximately equivalent to four cells from the center
diff --git a/raster/r.flow/r.flow.html b/raster/r.flow/r.flow.html
index 28ea66a6c23..da06e63bf5c 100644
--- a/raster/r.flow/r.flow.html
+++ b/raster/r.flow/r.flow.html
@@ -32,8 +32,8 @@ 
      NOTES
      
 or vice-versa), cross a barrier, or arrive at a cell with undefined
 elevation or aspect. Another option, skip, indicates that
 only the flowlines from every val-th cell are to be included
-in flowline.  The default skip is max(1, <rows
-in elevation>/50, <cols in elevation>/50).  A
+in flowline.  The default skip is max(1, <rows
+in elevation>/50, <cols in elevation>/50).  A
 high skip usually speeds up processing time and often improves
 the readability of a visualization of flowline.
 
      
diff --git a/raster/r.geomorphon/r.geomorphon.html b/raster/r.geomorphon/r.geomorphon.html
index 57f744392bd..80b75d1b241 100644
--- a/raster/r.geomorphon/r.geomorphon.html
+++ b/raster/r.geomorphon/r.geomorphon.html
@@ -1,5 +1,8 @@
 
      DESCRIPTION
      
 
+r.geomorphon calculates terrain forms using machine-vison
+technique called geomorphons.
+
 
      What is geomorphon:
      
 
      
 What is geomorphon
      
@@ -184,7 +187,7 @@ 
      REFERENCES
      
 
    • Stepinski, T., Jasiewicz, J., 2011, Geomorphons - a new approach to
 classification of landform, in :  Eds: Hengl, T., Evans, I.S., Wilson,
 J.P., and Gould, M., Proceedings of Geomorphometry 2011,  Redlands,
-109-112 (PDF)
      • 
+109-112 (PDF)
 
    • Jasiewicz, J., Stepinski, T.,  2013, Geomorphons - a pattern
 recognition approach to classification and mapping of landforms,
 Geomorphology, vol. 182, 147-156 (DOI: 10.1016/j.geomorph.2012.11.005)
      • 
diff --git a/raster/r.gwflow/r.gwflow.html b/raster/r.gwflow/r.gwflow.html
index 05dbe88d878..3edc76354eb 100644
--- a/raster/r.gwflow/r.gwflow.html
+++ b/raster/r.gwflow/r.gwflow.html
@@ -1,7 +1,7 @@
 
      DESCRIPTION
      
 
-This numerical program calculates implicit transient, confined and
-unconfined groundwater flow in two dimensions based on
+r.gwflow is a numerical program which calculates implicit transient,
+confined and unconfined groundwater flow in two dimensions based on
 raster maps and the current region settings.
 All initial and boundary conditions must be provided as
 raster maps. The unit of the current project's coordinate reference system must be meters.
diff --git a/raster/r.his/r.his.html b/raster/r.his/r.his.html
index 0dd2c429e04..964ac2d2273 100644
--- a/raster/r.his/r.his.html
+++ b/raster/r.his/r.his.html
@@ -1,7 +1,7 @@
 
      DESCRIPTION
      
 
 HIS stands for hue, intensity, and saturation.
-This program produces red, green and blue raster map layers
+r.his produces red, green and blue raster map layers
 providing a visually pleasing combination of hue,
 intensity, and saturation values from two or three
 user-specified raster map layers.
diff --git a/raster/r.horizon/r.horizon.html b/raster/r.horizon/r.horizon.html
index 71f8599dd70..e7ebcf68783 100644
--- a/raster/r.horizon/r.horizon.html
+++ b/raster/r.horizon/r.horizon.html
@@ -258,18 +258,18 @@ 
      REFERENCES
      
 
 
      Hofierka J., Huld T., Cebecauer T., Suri M., 2007. Open Source Solar
 Radiation Tools for Environmental and Renewable Energy Applications,
-International Symposium on
+International Symposium on
 Environmental Software Systems, Prague, 2007
 
      Neteler M., Mitasova H., 2004. Open Source GIS: A GRASS GIS
-Approach, Springer, New York.
+Approach, Springer, New York.
 ISBN: 1-4020-8064-6, 2nd Edition 2004 (reprinted 2005), 424 pages
 
-
      Project PVGIS, European
+
      Project PVGIS, European
 Commission, DG Joint Research Centre 2001-2007
 
      Suri M., Hofierka J., 2004.
 A New GIS-based Solar Radiation Model and Its Application for
-Photovoltaic Assessments. Transactions
-in GIS, 8(2), 175-190
+Photovoltaic Assessments. Transactions
+in GIS, 8(2), 175-190 (DOI: 10.1111/j.1467-9671.2004.00174.x)
 
 
      SEE ALSO
      
 
diff --git a/raster/r.in.ascii/r.in.ascii.html b/raster/r.in.ascii/r.in.ascii.html
index 0f450de5fd4..eacf22ef81e 100644
--- a/raster/r.in.ascii/r.in.ascii.html
+++ b/raster/r.in.ascii/r.in.ascii.html
@@ -52,7 +52,7 @@ 
      NOTES
      
 
 
      
 The data (which follows the header section) must contain
-r x c values, but it is not necessary
+r x c values, but it is not necessary
 that all the data for a row be on one line. A row may be
 split over many lines.
 
diff --git a/raster/r.in.bin/r.in.bin.html b/raster/r.in.bin/r.in.bin.html
index 9c57e38f98b..2d457b1680e 100644
--- a/raster/r.in.bin/r.in.bin.html
+++ b/raster/r.in.bin/r.in.bin.html
@@ -10,7 +10,7 @@ 
      DESCRIPTION
      
 
      The north, south, east, and west field values are the coordinates of the
 edges of the geographic region. The rows and cols values describe the dimensions
 of the matrix of data to follow. If the input is a
-GMT binary array
+GMT binary array
 (-h flag), the six dimension fields (north, south, east, west, rows and cols)
 are obtained from the GMT header. If the bytes field is entered incorrectly an
 error will be generated suggesting a closer bytes value.
diff --git a/raster/r.in.gdal/r.in.gdal.html b/raster/r.in.gdal/r.in.gdal.html
index 76de4e4eec5..7083a48410e 100644
--- a/raster/r.in.gdal/r.in.gdal.html
+++ b/raster/r.in.gdal/r.in.gdal.html
@@ -20,7 +20,7 @@ 
      GDAL supported raster formats
      
 
 Full details on all GDAL supported formats are available at:
 
      
-https://gdal.org/formats_list.html
+https://gdal.org/en/stable/drivers/raster/
 
      
 Selected formats out of the more than 140 supported formats:
 
@@ -132,8 +132,8 @@ 
      Project Creation
      
 information when importing datasets if the source format includes CRS information,
 and if the GDAL driver supports it. If the CRS of the source dataset does
 not match the CRS of the current project r.in.gdal will
-report an error message (Coordinate reference system of dataset does not appear to
-match current project) and then report the PROJ_INFO parameters of
+report an error message (Coordinate reference system of dataset does not appear to
+match current project) and then report the PROJ_INFO parameters of
 the source dataset.
 
 
      
@@ -177,8 +177,8 @@ 
      Map names: Management of offset and leading zeros
      
 across different input files.
 
      
 The num_digits parameter allows defining the number of  leading zeros
-(zero padding) in case of band numbers (e.g., to turn band.1 into
-band.001).
+(zero padding) in case of band numbers (e.g., to turn band.1 into
+band.001).
 
 
      NOTES
      
 
@@ -252,7 +252,7 @@ 
      Error Messages
      
 "ERROR: Input map is rotated - cannot import."
      
 In this case the image must be first externally rotated, applying the rotation info stored in
 the metadata field of the raster image file. For example, the
-gdalwarp  software can be used
+gdalwarp software can be used
 to transform the map to North-up (note, there are several gdalwarp parameters to select the
 resampling algorithm):
 
@@ -296,9 +296,8 @@ 
      EXAMPLES
      
 
 
      ECAD Data
      
 
-The European Climate Assessment and Dataset (ECAD) project
-provides climate data for Europe ranging from 1950 - 2015 or later
-(Terms of use).
+The European Climate Assessment and Dataset (ECAD) project
+provides climate data for Europe ranging from 1950 - 2015 or later.
 To import the different chunks of data provided by the project as netCDF files,
 the offset parameter can be used to properly assign numbers to the series
 of daily raster maps from 1st Jan 1950 (in case of importing the ECAD data
@@ -363,8 +362,8 @@ 
      GLOBE DEM
      
 
      Raster file import over network
      
 
 Since GDAL 2.x it is possible to import raster data over the network 
-(see GDAL Virtual File Systems)
-including Cloud Optimized GeoTIFF,
+(see GDAL Virtual File Systems)
+including Cloud Optimized GeoTIFF,
 i.e. access uncompressed and compressed raster data via a http(s) or ftp connection.
 As an example the import of the global SRTMGL1 V003 tiles at 1 arc second (about 30 meters)
 resolution, void-filled:
@@ -398,7 +397,7 @@ 
      HDF
      
 
 
      REFERENCES
      
 
-GDAL Pages: https://gdal.org/
+GDAL Pages: https://gdal.org
 
 
      SEE ALSO
      
 
@@ -416,5 +415,5 @@ 
      SEE ALSO
      
 
 
      AUTHOR
      
 
-Frank Warmerdam
+Frank Warmerdam
  (email).
diff --git a/raster/r.in.lidar/r.in.lidar.html b/raster/r.in.lidar/r.in.lidar.html
index f92ad0485a8..a3346047bec 100644
--- a/raster/r.in.lidar/r.in.lidar.html
+++ b/raster/r.in.lidar/r.in.lidar.html
@@ -125,7 +125,7 @@ 
      Statistics
      
 
      coeff_var
      
 
      This computes the coefficient of variance of point values for each
 cell. Coefficient of variance is given in percentage and defined as
-(stddev/mean)*100.
      
+(stddev/mean)*100.
      
 
      median
      
 
      This computes the median of point values for each cell
      
 
      percentile
      
@@ -210,7 +210,7 @@ 
      Filtering
      
 The user can use a combination of r.in.lidar output maps
 to create custom raster-based filters, for example, use
 r.mapcalc to create
-a mean-(2*stddev) map. (In this example the user may want to
+a mean-(2*stddev) map. (In this example the user may want to
 include a lower bound filter in r.mapcalc to remove highly
 variable points (small n) or run r.neighbors to
 smooth the stddev map before further use.)
@@ -332,10 +332,10 @@ 
      Memory consumption
      
 (> 10000x10000 pixels).
 If the module refuses to start complaining that there isn't enough memory,
 use the percent parameter to run the module in several passes.
-In addition using a less precise map format (CELL [integer] or
-FCELL [floating point]) will use less memory than a DCELL
+In addition using a less precise map format (CELL [integer] or
+FCELL [floating point]) will use less memory than a DCELL
 [double precision floating point] output map.
-For method=n, the CELL format is used
+For method=n, the CELL format is used
 automatically.
 
 
      
@@ -356,7 +356,7 @@ 
      Memory consumption
      
 the number of data points.
 
 
      
-The default map type=FCELL is intended as compromise between
+The default map type=FCELL is intended as compromise between
 preserving data precision and limiting system resource consumption.
 
 
      Trim option
      
@@ -454,28 +454,28 @@ 
      Serpent Mound dataset
      
 
 This example is analogous to the example used in the GRASS wiki page for
 importing LAS as raster DEM.
-
      The sample LAS data are in the file "Serpent Mound Model LAS Data.las",
+
      The sample LAS data are in the file "Serpent Mound Model LAS Data.laz",
 available at
-appliedimagery.com:
+Serpent Mound Model LAS Data.laz:
 
 
       # print LAS file info
-r.in.lidar -p input="Serpent Mound Model LAS Data.las"
+r.in.lidar -p input="Serpent Mound Model LAS Data.laz"
 
 # using v.in.lidar to create a new project
 # create project with CRS information of the LAS data
-v.in.lidar -i input="Serpent Mound Model LAS Data.las" project=Serpent_Mound
+v.in.lidar -i input="Serpent Mound Model LAS Data.laz" project=Serpent_Mound
 
 # quit and restart GRASS in the newly created project "Serpent_Mound"
 
 # scan the extents of the LAS data
-r.in.lidar -sg input="Serpent Mound Model LAS Data.las"
+r.in.lidar -sg input="Serpent Mound Model LAS Data.laz"
 
 # set the region to the extents of the LAS data, align to resolution
 g.region n=4323641.57 s=4320942.61 w=289020.90 e=290106.02 res=1 -ap
 
 # import as raster DEM
-r.in.lidar input="Serpent Mound Model LAS Data.las" \
+r.in.lidar input="Serpent Mound Model LAS Data.laz" \
            output=Serpent_Mound_Model_LAS_Data method=mean
 
      
 
@@ -488,7 +488,7 @@ 
      Height above ground
      
 
 The mean height above ground of the points can be computed for each
 raster cell (the ground elevation is given by the raster map
-elevation):
+elevation):
 
 
       g.region raster=elevation -p
@@ -551,14 +551,14 @@ 
      Multiple file input
      
 
      KNOWN ISSUES
      
 
 
        
-
      • The "nan" value (as defined in C language) can leak into
+
      • The "nan" value (as defined in C language) can leak into
     coeff_var raster maps. Cause is unknown. Possible
-    work-around is: r.null setnull=nan or
-    r.mapcalc 'no_nan = if(map == map, map, null())'.
        • 
+    work-around is: r.null setnull=nan or
+    r.mapcalc 'no_nan = if(map == map, map, null())'.
 
      • Only one method can be applied for a single run and multiple map
     output from a single run
-    (e.g. method=string[,string,...] output=name[,name,...]
-    or n=string mean=string) is no supported.
        • 
+    (e.g. method=string[,string,...] output=name[,name,...]
+    or n=string mean=string) is no supported.
 
@@ -597,14 +597,14 @@ 
        REFERENCES
        
 
      • 
 V. Petras, A. Petrasova, J. Jeziorska, H. Mitasova (2016):
 Processing UAV and lidar point clouds in GRASS GIS.
-XXIII ISPRS Congress 2016 [ISPRS Archives, ResearchGate]
        • 
+XXIII ISPRS Congress 2016 [ISPRS Archives, ResearchGate]
 
      • 
 
 ASPRS LAS format
        • 
 
      • 
-LAS library
        • 
+LAS library
 
      • 
-LAS library C API documentation
        • 
+LAS library C API documentation
 
      
 
 
      AUTHORS
      
diff --git a/raster/r.in.mat/r.in.mat.html b/raster/r.in.mat/r.in.mat.html
index be0f521dca2..d5613c1ed61 100644
--- a/raster/r.in.mat/r.in.mat.html
+++ b/raster/r.in.mat/r.in.mat.html
@@ -21,7 +21,7 @@ 
      DESCRIPTION
      
 The 'map_name' variable is optional, if it exists, and is valid, the
 new map will be thus named. If it doesn't exist or a name is specified with
 the output= option, the raster map's name will be set to
-"MatFile" or the name specified respectively.
+"MatFile" or the name specified respectively.
 (maximum 64 characters; normal GRASS naming rules apply)
 
      
 
      
@@ -43,9 +43,9 @@ 
      NOTES
      
 copied between different system architectures without binary translation
 (caveat: see "TODO" below).

      
 
-As there is no IEEE value for NaN in integer arrays, GRASS's null
+As there is no IEEE value for NaN in integer arrays, GRASS's null
 value may be used to represent it within these maps. Usually Matlab will save
-any integer based matrix with NaN values as a double-precision
+any integer based matrix with NaN values as a double-precision
 floating point array, so this usually isn't an issue. To save space, once the
 map is loaded into GRASS you can convert it back to an integer map with the
 following command:
@@ -53,7 +53,7 @@ 
      NOTES
      
 r.mapcalc "int_map = int(MATFile_map)"
 
      
 
-NaN values in either floating point or double-precision floating point
+NaN values in either floating point or double-precision floating point
 matrices should translate into null values as expected.

      
 
 
@@ -73,8 +73,8 @@ 
      NOTES

      -Remember Matlab arrays are referenced as (row,column), -i.e. (y,x). +Remember Matlab arrays are referenced as (row,column), +i.e. (y,x).

      In addition, r.in.mat and r.out.mat make for a nice binary container format for transferring georeferenced maps around, diff --git a/raster/r.in.pdal/r.in.pdal.html b/raster/r.in.pdal/r.in.pdal.html index cefc1984bef..61afe778c6a 100644 --- a/raster/r.in.pdal/r.in.pdal.html +++ b/raster/r.in.pdal/r.in.pdal.html @@ -123,7 +123,7 @@

      Statistics

      coeff_var
      This computes the coefficient of variance of point values for each cell. Coefficient of variance is given in percentage and defined as -100 * sqrt(variance) / mean.
      +100 * sqrt(variance) / mean.
      median
      This computes the median of point values for each cell
      mode
      @@ -238,7 +238,7 @@

      Filtering and selection

      The user can use a combination of r.in.pdal output maps to create custom raster-based filters, for example, use r.mapcalc to create -a mean-(2*stddev) map. (In this example the user may want to +a mean-(2*stddev) map. (In this example the user may want to include a lower bound filter in r.mapcalc to remove highly variable points (small n) or run r.neighbors to smooth the stddev map before further use.) @@ -394,10 +394,10 @@

      Memory consumption

      (> 10000x10000 pixels). If the module refuses to start complaining that there isn't enough memory, use the percent parameter to run the module in several passes. -In addition using a less precise map format (CELL [integer] or -FCELL [floating point]) will use less memory than a DCELL +In addition using a less precise map format (CELL [integer] or +FCELL [floating point]) will use less memory than a DCELL [double precision floating point] output map. -For methods=n, mode, sidnmin, sidnmax, the CELL +For methods=n, mode, sidnmin, sidnmax, the CELL format is used automatically.

      @@ -418,7 +418,7 @@

      Memory consumption

      the number of data points.

      -The default map type=FCELL is intended as compromise between +The default map type=FCELL is intended as compromise between preserving data precision and limiting system resource consumption.

      Trim option

      @@ -512,28 +512,28 @@

      Serpent Mound dataset

      This example is analogous to the example used in the GRASS wiki page for importing LAS as raster DEM. -

      The sample LAS data are in the file "Serpent Mound Model LAS Data.las", +

      The sample LAS data are in the file "Serpent Mound Model LAS Data.laz", available at -appliedimagery.com: +Serpent Mound Model LAS Data.laz: 

       # print LAS file info
-r.in.pdal -p input="Serpent Mound Model LAS Data.las"
+r.in.pdal -p input="Serpent Mound Model LAS Data.laz"
 
 # using v.in.lidar to create a new project
 # create a project with CRS information of the LAS data
-v.in.lidar -i input="Serpent Mound Model LAS Data.las" project=Serpent_Mound
+v.in.lidar -i input="Serpent Mound Model LAS Data.laz" project=Serpent_Mound
 
 # quit and restart GRASS in the newly created project "Serpent_Mound"
 
 # scan the extents of the LAS data
-r.in.pdal -g input="Serpent Mound Model LAS Data.las"
+r.in.pdal -g input="Serpent Mound Model LAS Data.laz"
 
 # set the region to the extents of the LAS data, align to resolution
 g.region n=4323641.57 s=4320942.61 w=289020.90 e=290106.02 res=1 -ap
 
 # import as raster DEM
-r.in.pdal input="Serpent Mound Model LAS Data.las" \
+r.in.pdal input="Serpent Mound Model LAS Data.laz" \
            output=Serpent_Mound_Model_LAS_Data method=mean
      @@ -546,7 +546,7 @@

      Height above ground

      The mean height above ground of the points can be computed for each raster cell (the ground elevation is given by the raster map -elevation): +elevation): 
       g.region raster=elevation -p
@@ -611,8 +611,8 @@ 
      KNOWN ISSUES
      
 
        
 
      • Only one method can be applied for a single run and multiple map
     output from a single run
-    (e.g. method=string[,string,...] output=name[,name,...]
-    or n=string mean=string) is no supported.
        • 
+    (e.g. method=string[,string,...] output=name[,name,...]
+    or n=string mean=string) is no supported.
 
      
 
 If you encounter any problems (or solutions!) please contact the GRASS
@@ -647,7 +647,7 @@ 
      REFERENCES
      
 
    • 
 V. Petras, A. Petrasova, J. Jeziorska, H. Mitasova (2016):
 Processing UAV and lidar point clouds in GRASS GIS.
-XXIII ISPRS Congress 2016 [ISPRS Archives, ResearchGate]
      • 
+XXIII ISPRS Congress 2016 [ISPRS Archives, ResearchGate]
 
    • 
 
 ASPRS LAS format
      • 
@@ -659,7 +659,7 @@ 
      AUTHORS
      
 
 Markus Metz
      
 Vaclav Petras,
-NCSU GeoForAll Lab
+NCSU GeoForAll Lab
 (base_raster option, documentation),
      
 Maris Nartiss, LU GZZF
 (refactoring, additional filters, custom dimension support)
diff --git a/raster/r.in.poly/r.in.poly.html b/raster/r.in.poly/r.in.poly.html
index d47212a162d..3860f414f7c 100644
--- a/raster/r.in.poly/r.in.poly.html
+++ b/raster/r.in.poly/r.in.poly.html
@@ -56,20 +56,20 @@ 
      Input Format
      -The A signals the beginning of a filled polygon. +The A signals the beginning of a filled polygon. It must appear in the first column. -The L signals the beginning of a linear feature. +The L signals the beginning of a linear feature. It also must appear in the first column. -The P signals the beginning of a single cell point feature. +The P signals the beginning of a single cell point feature. Again, it must appear in the first column. The coordinates of the vertices of the polygon, or the coordinates defining the linear or point feature follow and must have a space in the first column and at least one space between the easting and the northing. To give meaning to the features, the -"=" indicates that the feature currently being +"=" indicates that the feature currently being processed has category value cat# (which must be an integer) and a label (which may be more than one word, or which may be omitted). diff --git a/raster/r.in.xyz/r.in.xyz.html b/raster/r.in.xyz/r.in.xyz.html index 70103d8e778..55c04e74a2d 100644 --- a/raster/r.in.xyz/r.in.xyz.html +++ b/raster/r.in.xyz/r.in.xyz.html @@ -43,7 +43,7 @@

      DESCRIPTION

      • Variance and derivatives use the biased estimator (n). [subject to change]
      • Coefficient of variance is given in percentage and defined as -(stddev/mean)*100.
        • +(stddev/mean)*100.

      @@ -78,8 +78,8 @@

      Memory use

      will use a large amount of system memory for large raster regions (10000x10000). If the module refuses to start complaining that there isn't enough memory, use the percent parameter to run the module in several passes. -In addition using a less precise map format (CELL [integer] or -FCELL [floating point]) will use less memory than a DCELL +In addition using a less precise map format (CELL [integer] or +FCELL [floating point]) will use less memory than a DCELL [double precision floating point] output map. Methods such as n, min, max, sum will also use less memory, while stddev, variance, and coeff_var will use more. @@ -91,9 +91,9 @@

      Memory use

      but for the aggregate fns it will also depend on the number of data points. (?) -->

      -The default map type=FCELL is intended as compromise between +The default map type=FCELL is intended as compromise between preserving data precision and limiting system resource consumption. -If reading data from a stdin stream, the program can only run using +If reading data from a stdin stream, the program can only run using a single pass.

      Setting region bounds and resolution

      @@ -122,15 +122,15 @@

      Setting region bounds and resolution

      If you only intend to interpolate the data with r.to.vect and v.surf.rst, then there is little point to setting the region resolution so fine that you only catch one data point per cell -- you might -as well use "v.in.ascii -zbt" directly. +as well use "v.in.ascii -zbt" directly.

      Filtering

      Points falling outside the current region will be skipped. This includes points falling exactly on the southern region bound. -(to capture those adjust the region with "g.region s=s-0.000001"; +(to capture those adjust the region with "g.region s=s-0.000001"; see g.region) -

      Blank lines and comment lines starting with the hash symbol (#) +

      Blank lines and comment lines starting with the hash symbol (#) will be skipped.

      @@ -147,7 +147,7 @@

      Filtering

      The user can use a combination of r.in.xyz output maps to create -custom filters. e.g. use r.mapcalc to create a mean-(2*stddev) +custom filters. e.g. use r.mapcalc to create a mean-(2*stddev) map. [In this example the user may want to include a lower bound filter in r.mapcalc to remove highly variable points (small n) or run r.neighbors to smooth the stddev map before further use.] @@ -193,7 +193,7 @@

      Import of x,y,string data

      r.in.xyz is expecting numeric values as z column. In order to perform a occurrence count operation even on x,y data with non-numeric attribute(s), the data can be imported using either the x or y -coordinate as a fake z column for method=n (count +coordinate as a fake z column for method=n (count number of points per grid cell), the z values are ignored anyway.

      EXAMPLES

      @@ -287,7 +287,7 @@

      TODO

      • Support for multiple map output from a single run.
        - method=string[,string,...] output=name[,name,...]
        + method=string[,string,...] output=name[,name,...]
        This can be easily handled by a wrapper script, with the added benefit of it being very simple to parallelize that way.
      @@ -295,8 +295,8 @@

      TODO

      KNOWN ISSUES

        -
      • "nan" can leak into coeff_var maps. -
        Cause unknown. Possible work-around: "r.null setnull=nan"
        • +
      • "nan" can leak into coeff_var maps. +
        Cause unknown. Possible work-around: "r.null setnull=nan"
      diff --git a/raster/r.info/r.info.html b/raster/r.info/r.info.html index 8cc7b1a429f..b32f11ce6b1 100644 --- a/raster/r.info/r.info.html +++ b/raster/r.info/r.info.html @@ -69,7 +69,7 @@

      EXAMPLES

      | Comments: | | slope map elev = elev_ned10m | | zfactor = 1.00 format = degrees | - | min_slope = 0.000000 | + | min_slope = 0.000000 | | | +----------------------------------------------------------------------------+ @@ -78,7 +78,7 @@

      EXAMPLES

      subset of the available information by passing various flags to the module:

      -Output in shell script style, useful for eval (eval `r.info -g slope`): +Output in shell script style, useful for eval (eval `r.info -g slope`): 

       r.info -g slope
diff --git a/raster/r.lake/r.lake.html b/raster/r.lake/r.lake.html
index 4d12be899c6..d70d1297e6f 100644
--- a/raster/r.lake/r.lake.html
+++ b/raster/r.lake/r.lake.html
@@ -1,6 +1,6 @@
 
      DESCRIPTION
      
 
-
      The module fills a lake to a target water level from a given start point. The user
+r.lake fills a lake to a target water level from a given start point. The user
 can think of it as r.grow with additional
 checks for elevation. The resulting
 raster map contains cells with values representing lake depth and NULL for all other
@@ -66,8 +66,8 @@ 
      r.mapcalc equivalent - for GRASS hackers

      -The ${seedmap} variable is replaced by seed map names, ${dem} -with DEM map name, and ${wlevel} with target water level. To get +The ${seedmap} variable is replaced by seed map names, ${dem} +with DEM map name, and ${wlevel} with target water level. To get single water level, this code block is called with same level numerous times (in a loop) as the lake grows by single cells during single run. @@ -77,7 +77,7 @@

      KNOWN ISSUES

      • The entire map is loaded into RAM.
      • A completely negative seed map will not work! At least one cell must have - a value > 0. Output from r.lake -n cannot be used + a value > 0. Output from r.lake -n cannot be used as input in the next run.
      diff --git a/raster/r.li/r.li.cwed/r.li.cwed.html b/raster/r.li/r.li.cwed/r.li.cwed.html index 461eec731b6..88ac06f2ad7 100644 --- a/raster/r.li/r.li.cwed/r.li.cwed.html +++ b/raster/r.li/r.li.cwed/r.li.cwed.html @@ -26,8 +26,8 @@

      NOTES

      If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

      If the sample area contains only NULL values it is considered to @@ -68,10 +68,10 @@

      REFERENCES

      McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

      AUTHORS

      -Serena Pallecchi student of Computer Science University of Pisa (Italy).
      +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
      Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
      Markus Metz diff --git a/raster/r.li/r.li.daemon/r.li.daemon.html b/raster/r.li/r.li.daemon/r.li.daemon.html index 2d3cc5c4901..13f190df219 100644 --- a/raster/r.li/r.li.daemon/r.li.daemon.html +++ b/raster/r.li/r.li.daemon/r.li.daemon.html @@ -82,7 +82,7 @@

      REFERENCES

      McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

      AUTHORS

      diff --git a/raster/r.li/r.li.dominance/r.li.dominance.html b/raster/r.li/r.li.dominance/r.li.dominance.html index bccf6f01e04..15679874171 100644 --- a/raster/r.li/r.li.dominance/r.li.dominance.html +++ b/raster/r.li/r.li.dominance/r.li.dominance.html @@ -17,8 +17,8 @@

      NOTES

      If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

      If the input raster map contains only NULL values then @@ -68,10 +68,10 @@

      REFERENCES

      McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

      AUTHORS

      -Serena Pallecchi student of Computer Science University of Pisa (Italy).
      +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
      Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
      Markus Metz diff --git a/raster/r.li/r.li.edgedensity/r.li.edgedensity.html b/raster/r.li/r.li.edgedensity/r.li.edgedensity.html index e96f26e02b7..840a0cf9650 100644 --- a/raster/r.li/r.li.edgedensity/r.li.edgedensity.html +++ b/raster/r.li/r.li.edgedensity/r.li.edgedensity.html @@ -1,7 +1,7 @@

      DESCRIPTION

      -r.li.edgedensity calculates:
      -
      +r.li.edgedensity calculates: +
      • the density of all edges of patch type k r.li.edgedensity formula 1 @@ -29,8 +29,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.edgedensity @@ -89,10 +89,10 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        -Serena Pallecchi student of Computer Science University of Pisa (Italy).
        +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
        Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
        Markus Metz diff --git a/raster/r.li/r.li.html b/raster/r.li/r.li.html index a7685ca55ec..37e40d6cfc7 100644 --- a/raster/r.li/r.li.html +++ b/raster/r.li/r.li.html @@ -38,8 +38,8 @@

        NOTES

        1. run g.gui.rlisetup: create a configuration file selecting the parts of raster map to be analyzed. This file allows re-running - an analysis easily. It is stored on Windows in the directory C:\Users\userxy\AppData\Roaming\GRASS8\r.li\, on GNU/Linux in - $HOME/.grass8/r.li/.
          2. + an analysis easily. It is stored on Windows in the directory C:\Users\userxy\AppData\Roaming\GRASS8\r.li\, on GNU/Linux in + $HOME/.grass8/r.li/.
        2. run one or more of the r.li.[index] modules (e.g., r.li.patchdensity) to calculate the selected index @@ -85,7 +85,7 @@

          EXAMPLES

        3. CALCULATE PATCHDENSITY INDEX
            -
          1. set the region settings to the "geology" raster map: +
          2. set the region settings to the "geology" raster map: 
             g.region raster=geology -p
            @@ -98,7 +98,7 @@

            EXAMPLES

        -The resulting patch density is stored in "patchdens" raster map. +The resulting patch density is stored in "patchdens" raster map. You can verify the result for example with contour lines: 
        @@ -120,7 +120,7 @@ 
        SEE ALSO
        
 
 GUI tools:
 
          
-  
        •  g.gui.rlisetup: Configuration editor for the r.li.* module where * is name of the index
          • 
+  
        •  g.gui.rlisetup: Configuration editor for the r.li.* module where * is name of the index
          • 
 
        
 
 Patch indices:
@@ -190,7 +190,7 @@ 
        REFERENCES
        
 McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern
 analysis program for quantifying landscape structure. USDA For. Serv.
 Gen. Tech. Rep. PNW-351
- (PDF).
        • + (PDF).
      • Baker, W.L. and Y. Cai. 1992. The r.le programs for multiscale analysis of diff --git a/raster/r.li/r.li.mpa/r.li.mpa.html b/raster/r.li/r.li.mpa/r.li.mpa.html index d54eabcb925..1acc2908608 100644 --- a/raster/r.li/r.li.mpa/r.li.mpa.html +++ b/raster/r.li/r.li.mpa/r.li.mpa.html @@ -18,8 +18,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.mpa considers to @@ -76,10 +76,10 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        -Serena Pallecchi student of Computer Science University of Pisa (Italy).
        +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
        Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it)
        Markus Metz diff --git a/raster/r.li/r.li.mps/r.li.mps.html b/raster/r.li/r.li.mps/r.li.mps.html index e52f98ede78..e7548a9db76 100644 --- a/raster/r.li/r.li.mps/r.li.mps.html +++ b/raster/r.li/r.li.mps/r.li.mps.html @@ -28,8 +28,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the sample area contains only NULL value cells, r.li.mps returns 0 (zero).
        @@ -78,7 +78,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.padcv/r.li.padcv.html b/raster/r.li/r.li.padcv/r.li.padcv.html index bbc688975f2..23aed65eedd 100644 --- a/raster/r.li/r.li.padcv/r.li.padcv.html +++ b/raster/r.li/r.li.padcv/r.li.padcv.html @@ -19,8 +19,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        The result is NULL if the sample area contains only NULL values. @@ -68,7 +68,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.padrange/r.li.padrange.html b/raster/r.li/r.li.padrange/r.li.padrange.html index 36e0f78f61c..6502c137f1e 100644 --- a/raster/r.li/r.li.padrange/r.li.padrange.html +++ b/raster/r.li/r.li.padrange/r.li.padrange.html @@ -20,8 +20,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the sample area contains only NULL values then r.li.padrange returns NULL.
        @@ -70,7 +70,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.padsd/r.li.padsd.html b/raster/r.li/r.li.padsd/r.li.padsd.html index 344ce04d372..379049c9506 100644 --- a/raster/r.li/r.li.padsd/r.li.padsd.html +++ b/raster/r.li/r.li.padsd/r.li.padsd.html @@ -21,8 +21,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        The result is NULL if the sample area contains only NULL values. @@ -70,7 +70,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.patchdensity/r.li.patchdensity.html b/raster/r.li/r.li.patchdensity/r.li.patchdensity.html index f22a27caae7..168a45d9772 100644 --- a/raster/r.li/r.li.patchdensity/r.li.patchdensity.html +++ b/raster/r.li/r.li.patchdensity/r.li.patchdensity.html @@ -23,8 +23,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        A sample area of only NULL values is considered to have zero patches, that is, the result is always ≥ 0. @@ -81,7 +81,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.patchnum/r.li.patchnum.html b/raster/r.li/r.li.patchnum/r.li.patchnum.html index b0d282a4dee..743f965b5b8 100644 --- a/raster/r.li/r.li.patchnum/r.li.patchnum.html +++ b/raster/r.li/r.li.patchnum/r.li.patchnum.html @@ -14,8 +14,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the sample area contains only NULL values then it is considered to have zero patches.
        @@ -64,7 +64,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.pielou/r.li.pielou.html b/raster/r.li/r.li.pielou/r.li.pielou.html index 3af1aee78ea..f8f9e2730fb 100644 --- a/raster/r.li/r.li.pielou/r.li.pielou.html +++ b/raster/r.li/r.li.pielou/r.li.pielou.html @@ -16,8 +16,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster contains NULL value cells, r.li.pielou @@ -67,9 +67,9 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        Luca Delucchi and Duccio Rocchini, Fondazione E. Mach (Italy), based on the r.li.shannon code -developed by Serena Pallecchi student of Computer Science University of Pisa (Italy) +developed by Serena Pallecchi, student of Computer Science University of Pisa (Italy) diff --git a/raster/r.li/r.li.renyi/r.li.renyi.html b/raster/r.li/r.li.renyi/r.li.renyi.html index 62f3d0d5fae..3b866356765 100644 --- a/raster/r.li/r.li.renyi/r.li.renyi.html +++ b/raster/r.li/r.li.renyi/r.li.renyi.html @@ -19,8 +19,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.renyi @@ -70,10 +70,10 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        Luca Delucchi and Duccio Rocchini, Fondazione E. Mach (Italy), based on -the r.li.shannon code developed by Serena Pallecchi student of +the r.li.shannon code developed by Serena Pallecchi, student of Computer Science University of Pisa (Italy). diff --git a/raster/r.li/r.li.richness/r.li.richness.html b/raster/r.li/r.li.richness/r.li.richness.html index 33c10575607..32bc7f99b0c 100644 --- a/raster/r.li/r.li.richness/r.li.richness.html +++ b/raster/r.li/r.li.richness/r.li.richness.html @@ -16,8 +16,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.richness @@ -67,9 +67,9 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        -Serena Pallecchi student of Computer Science University of Pisa (Italy).
        +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
        Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) diff --git a/raster/r.li/r.li.shannon/r.li.shannon.html b/raster/r.li/r.li.shannon/r.li.shannon.html index 684c97b4540..76ef70ebc25 100644 --- a/raster/r.li/r.li.shannon/r.li.shannon.html +++ b/raster/r.li/r.li.shannon/r.li.shannon.html @@ -17,8 +17,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.shannon @@ -68,9 +68,9 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        -Serena Pallecchi student of Computer Science University of Pisa (Italy).
        +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
        Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) diff --git a/raster/r.li/r.li.shape/r.li.shape.html b/raster/r.li/r.li.shape/r.li.shape.html index e0d8f6e9ef7..5b7d7219588 100644 --- a/raster/r.li/r.li.shape/r.li.shape.html +++ b/raster/r.li/r.li.shape/r.li.shape.html @@ -18,8 +18,8 @@

        NOTES

        If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.shape @@ -69,7 +69,7 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        diff --git a/raster/r.li/r.li.simpson/r.li.simpson.html b/raster/r.li/r.li.simpson/r.li.simpson.html index 82f37920d49..fb33b7cad98 100644 --- a/raster/r.li/r.li.simpson/r.li.simpson.html +++ b/raster/r.li/r.li.simpson/r.li.simpson.html @@ -17,8 +17,8 @@

        NOTES

        file/map parameters. If the "moving window" method was selected in g.gui.rlisetup, then the output will be a raster map, otherwise an ASCII file will be generated in -the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ -(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux). +the folder C:\Users\userxy\AppData\Roaming\GRASS8\r.li\output\ +(MS-Windows) or $HOME/.grass8/r.li/output/ (GNU/Linux).

        If the input raster map contains only NULL values then r.li.simpson @@ -68,9 +68,9 @@

        REFERENCES

        McGarigal, K., and B. J. Marks. 1995. FRAGSTATS: spatial pattern analysis program for quantifying landscape structure. USDA For. Serv. -Gen. Tech. Rep. PNW-351. (PDF) +Gen. Tech. Rep. PNW-351. (PDF)

        AUTHORS

        -Serena Pallecchi student of Computer Science University of Pisa (Italy).
        +Serena Pallecchi, student of Computer Science University of Pisa (Italy).
        Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) diff --git a/raster/r.mapcalc/r.mapcalc.html b/raster/r.mapcalc/r.mapcalc.html index 6c88642d17f..5f943f2abae 100644 --- a/raster/r.mapcalc/r.mapcalc.html +++ b/raster/r.mapcalc/r.mapcalc.html @@ -414,8 +414,8 @@

        Data types and their precision

        Note that the value counter wraps around when the value overflows its range. -E.g., if your expression is a = int(2147483648), you will get NULL -value. For expression a = int(2147483649), you will reach the lowest +E.g., if your expression is a = int(2147483648), you will get NULL +value. For expression a = int(2147483649), you will reach the lowest value possible instead, i.e. -2147483647.

        Floating point values in the expression

        @@ -557,8 +557,8 @@

        Usage from command line

         'result = elevation * 2'
        -Without the quotes, the *, which has special meaning to the UNIX shell, -would be altered and r.mapcalc would see something other than the *. +Without the quotes, the *, which has special meaning to the UNIX shell, +would be altered and r.mapcalc would see something other than the *.

        Multiple computations

        @@ -583,7 +583,7 @@

        Backwards compatibility

        For the backwards compatibility with GRASS 6, -if no options are given, it manufactures file=- (which reads from +if no options are given, it manufactures file=- (which reads from stdin), so you can continue to use e.g.: 
         r.mapcalc < file
@@ -594,7 +594,7 @@ 
        Backwards compatibility
        
 foo = 1
 EOF
        -But unless you need compatibility with previous GRASS GIS versions, use file= +But unless you need compatibility with previous GRASS GIS versions, use file= explicitly, as stated above.

        When the map name contains uppercase letter(s) or a dot which are not @@ -653,7 +653,7 @@

        Raster MASK handling

        eval function

        If the output of the computation should be only one map but the expression is so complex that it is better to split it -to several expressions, the eval function can be used: +to several expressions, the eval function can be used: 
         r.mapcalc << EOF
 eval(elev_200 = elevation - 200, \
@@ -662,23 +662,23 @@ 
        eval function
        
 elevation_result = (0.5 * elev_200) + 0.8 * elev_p
 EOF
        -This example uses unix-like << EOF syntax to provide +This example uses unix-like << EOF syntax to provide input to r.mapcalc.

        Note that the temporary variables (maps) are not created and thus it does not matter whether they exists or not. -In the example above, if map elev_200 exists it will not be +In the example above, if map elev_200 exists it will not be overwritten and no error will be generated. -The reason is that the name elev_200 now denotes the temporary +The reason is that the name elev_200 now denotes the temporary variable (map) and not the existing map. -The following parts of the expression will use the temporary elev_200 -and the existing elev_200 will be left intact and will not be used. +The following parts of the expression will use the temporary elev_200 +and the existing elev_200 will be left intact and will not be used. If a user want to use the existing map, the name of the temporary variable (map) must be changed.

        Using the same map for input and output results

        A map cannot be used both as an input and as an output as in -this invalid expression oldmap = oldmap + 1, instead +this invalid expression oldmap = oldmap + 1, instead a subsequent rename using g.rename is needed when the same name is desired: @@ -797,7 +797,7 @@

        KNOWN ISSUES

        Any maps generated by a r.mapcalc command only exist after the entire command has completed. All maps are generated concurrently, row-by-row (i.e. there is an implicit "for row in rows {...}" around the entire expression). -Thus the #, @, and [ ] operators cannot be used on a map +Thus the #, @, and [ ] operators cannot be used on a map generated within same r.mapcalc command run. Consequently, the following (strikethrough code) does not work: @@ -806,11 +806,11 @@

        KNOWN ISSUES

        othermap = newmap[-1, 0] / newmap[1, 0] -

        Continuation lines must end with a \ and have no trailing +

        Continuation lines must end with a \ and have no trailing white space (blanks or tabs). If the user does leave white space at the end of continuation lines, the error messages produced by r.mapcalc will be meaningless and the equation will not work as the user intended. -This is particularly important for the eval() function. +This is particularly important for the eval() function.

        Currently, there is no comment mechanism in r.mapcalc. Perhaps adding a capability that would cause the entire line to be @@ -820,7 +820,7 @@

        KNOWN ISSUES

        of simply a blank line. This would make separation of multiple scripts separable by white space.

        r.mapcalc does not print a warning in case of operations on -NULL cells. It is left to the user to utilize the isnull() function. +NULL cells. It is left to the user to utilize the isnull() function.

        REFERENCES

        diff --git a/raster/r.mapcalc/r3.mapcalc.html b/raster/r.mapcalc/r3.mapcalc.html index 8990adefb68..742f5974384 100644 --- a/raster/r.mapcalc/r3.mapcalc.html +++ b/raster/r.mapcalc/r3.mapcalc.html @@ -397,8 +397,8 @@

        Usage from command line

         'result = volume * 2'
        -Without the quotes, the *, which has special meaning to the UNIX shell, -would be altered and r3.mapcalc would see something other than the *. +Without the quotes, the *, which has special meaning to the UNIX shell, +would be altered and r3.mapcalc would see something other than the *.

        Multiple computations

        @@ -409,7 +409,7 @@

        Backwards compatibility

        For the backwards compatibility with GRASS 6, -if no options are given, it manufactures file=- (which reads from +if no options are given, it manufactures file=- (which reads from stdin), so you can continue to use e.g.: 
         r3.mapcalc < file
@@ -420,7 +420,7 @@ 
        Backwards compatibility
        
 foo = 1
 EOF
        -But unless you need compatibility with previous GRASS GIS versions, use file= +But unless you need compatibility with previous GRASS GIS versions, use file= explicitly, as stated above.

        When the map name contains uppercase letter(s) or a dot which are not @@ -570,7 +570,7 @@

        KNOWN ISSUES

        Any maps generated by a r3.mapcalc command only exist after the entire command has completed. All maps are generated concurrently, row-by-row (i.e. there is an implicit "for row in rows {...}" around the entire expression). -Thus the #, @, and [ ] operators cannot be used on a map +Thus the #, @, and [ ] operators cannot be used on a map generated within same r3.mapcalc command run. 

        @@ -578,11 +578,11 @@ 
        KNOWN ISSUES
        
 othermap = newmap[-1, 0] / newmap[1, 0]
        -

        Continuation lines must end with a \ and have no trailing +

        Continuation lines must end with a \ and have no trailing white space (blanks or tabs). If the user does leave white space at the end of continuation lines, the error messages produced by r3.mapcalc will be meaningless and the equation will not work as the user intended. -This is particularly important for the eval() function. +This is particularly important for the eval() function.

        Currently, there is no comment mechanism in r3.mapcalc. Perhaps adding a capability that would cause the entire line to be @@ -592,7 +592,7 @@

        KNOWN ISSUES

        of simply a blank line. This would make separation of multiple scripts separable by white space.

        r3.mapcalc does not print a warning in case of operations on -NULL cells. It is left to the user to utilize the isnull() function. +NULL cells. It is left to the user to utilize the isnull() function.

        REFERENCES

        diff --git a/raster/r.null/r.null.html b/raster/r.null/r.null.html index 4d92b027d65..58293e58822 100644 --- a/raster/r.null/r.null.html +++ b/raster/r.null/r.null.html @@ -41,7 +41,7 @@

        NULL data compression

        By default no data files (i.e., NULL files) are not compressed unless a specific environment variable is set. The NULL file compression must be -explicitly turned on with export GRASS_COMPRESS_NULLS=1.
        +explicitly turned on with export GRASS_COMPRESS_NULLS=1.
        Warning: such raster maps can then only be opened with GRASS GIS 7.2.0 or later. NULL file compression can be managed with r.null -z. diff --git a/raster/r.object.geometry/r.object.geometry.html b/raster/r.object.geometry/r.object.geometry.html index 527db3cfffd..ca3524ebffc 100644 --- a/raster/r.object.geometry/r.object.geometry.html +++ b/raster/r.object.geometry/r.object.geometry.html @@ -23,10 +23,10 @@

        DESCRIPTION

      • area
      • perimeter
      • compact_square (compactness compared to a square: - compact_square = 4 * sqrt(area) / perimeter)
        • + compact_square = 4 * sqrt(area) / perimeter)
      • compact_circle (compactness compared to a circle: - compact_circle = perimeter / ( 2 * sqrt(PI * area) ))
        • -
      • fractal dimension ( fd = 2 * ( log(perimeter) / log(area + 0.001) ) )
        • + compact_circle = perimeter / ( 2 * sqrt(PI * area) )) +
      • fractal dimension ( fd = 2 * ( log(perimeter) / log(area + 0.001) ) )
      • mean x coordinate of object (in map units)
      • mean y coordinate of object (in map units)
      diff --git a/raster/r.out.bin/r.out.bin.html b/raster/r.out.bin/r.out.bin.html index 0041286cf25..48dcc20e334 100644 --- a/raster/r.out.bin/r.out.bin.html +++ b/raster/r.out.bin/r.out.bin.html @@ -9,7 +9,7 @@

      DESCRIPTION

      NOTES

      With the -h flag, data can be directly used by -GMT as Grid Format 1 (float) or +GMT as Grid Format 1 (float) or 2 (short). For example: 
      diff --git a/raster/r.out.gdal/r.out.gdal.html b/raster/r.out.gdal/r.out.gdal.html
index 28ddeb9c7d2..8a24e2bb870 100644
--- a/raster/r.out.gdal/r.out.gdal.html
+++ b/raster/r.out.gdal/r.out.gdal.html
@@ -9,7 +9,7 @@ 
      DESCRIPTION
      
 (createopt="TFW=YES,COMPRESS=DEFLATE").
 
      For possible createopt and metaopt parameters please
 consult the individual
-supported formats
+supported formats
 pages on the GDAL website.
 The createopt parameter may be used to create TFW or World files
 ("TFW=YES","WORLDFILE=ON").
@@ -25,7 +25,7 @@ 
      DESCRIPTION
      
 
 
      SUPPORTED RASTER FORMATS
      
 
-The set of supported
+The set of supported
 raster formats written by r.out.gdal depends on the local
 GDAL installation, printed with the -l flag. Available may be
 (incomplete list):
      
@@ -110,7 +110,7 @@ 
      Ranges of GDAL data types
      
 
 
      Adding overviews to speed up map display in other software
      
 
-Adding overviews with gdaladdo
+Adding overviews with gdaladdo
 after exporting can speed up display. The overviews are created internally
 within the exported file. The amount of levels (power-of-two factors) are
 controlled with the overviews parameter. The higher the overview level
@@ -151,13 +151,13 @@ 
      Improving GeoTIFF compatibility
      
 Here are some things to try:
 
 
        
-
      • Create a World file with createopt="TFW=YES".
        • 
+
      • Create a World file with createopt="TFW=YES".
        • 
 
 
      • Do not use GeoTIFF internal compression. Other GIS software often
 supports only a subset of the available compression methods with the
 supported methods differing between GIS software packages. Unfortunately
 this means the output image can be rather huge, but the file can be
-compressed with software like zip, gnuzip, or bzip2.
        • 
+compressed with software like zip, gnuzip, or bzip2.
 
 
      • Skip exporting the color table. Color tables are not always properly
 rendered, particularly for type UInt16, and the GeoTIFF file can appear
@@ -165,8 +165,8 @@ 
        Improving GeoTIFF compatibility
        
 a method to reset the color table and assign a new color table
 (sometimes called symbology).
        • 
 
-
      • Keep metadata simple with createopt="PROFILE=GeoTIFF" or
-createopt="PROFILE=BASELINE". With BASELINE no GDAL or GeoTIFF
+
      • Keep metadata simple with createopt="PROFILE=GeoTIFF" or
+createopt="PROFILE=BASELINE". With BASELINE no GDAL or GeoTIFF
 tags will be written and a World file is required (createopt="TFW=YES").
        • 
 
      
 
@@ -185,7 +185,7 @@ 
      EXAMPLES
      
 
 
      Export the integer raster basin_50K map to GeoTIFF format
      
 
-See also GeoTIFF format description (GDAL):
+See also GeoTIFF format description (GDAL):
 
 
       g.region raster=basin_50K -p
@@ -194,7 +194,7 @@ 
      Export the integer raster basin_50K map to GeoTIFF format
      
 
 
      Export the integer raster landclass96 map to Cloud Optimized GeoTIFF format
      
 
-See also Cloud Optimized GeoTIFF (COG) format description (GDAL):
+See also Cloud Optimized GeoTIFF (COG) format description (GDAL):
 
 
       g.region -p raster=landclass96
@@ -313,7 +313,7 @@ 
      Export RGB with alpha channel that encodes NULL cells
      
 
 
      Export the floating point raster elevation map to ERDAS/IMG format
      
 
-See also Erdas Imagine .img format description (GDAL):
+See also Erdas Imagine .img format description (GDAL):
 
 
       g.region raster=elevation -p
@@ -372,8 +372,8 @@ 
      REFERENCES
      
 
 
      SEE ALSO
      
 
-GDAL supported raster formats and
-GDAL supported vector formats
+GDAL supported raster formats and
+GDAL supported vector formats
 
 
      
 
diff --git a/raster/r.out.mat/r.out.mat.html b/raster/r.out.mat/r.out.mat.html
index 82bee6f3a87..32865313ca2 100644
--- a/raster/r.out.mat/r.out.mat.html
+++ b/raster/r.out.mat/r.out.mat.html
@@ -31,13 +31,13 @@ 
      NOTES
      
 copied between different system architectures without binary translation.
 

      
 
-As there is no IEEE value for NaN for integer maps, GRASS's null
+As there is no IEEE value for NaN for integer maps, GRASS's null
 value is used to represent it within these maps. You'll have to do something
 like this to clean them once the map is loaded into Matlab:
 
          map_data(find(map_data < -1e9)) = NaN;
      
 
 Null values in maps containing either floating point or double-precision
-floating point data should translate into NaN values as expected.
+floating point data should translate into NaN values as expected.
 

      
 
 
diff --git a/raster/r.out.mpeg/r.out.mpeg.html b/raster/r.out.mpeg/r.out.mpeg.html
index eb282acbbd9..aa8db1b3a4c 100644
--- a/raster/r.out.mpeg/r.out.mpeg.html
+++ b/raster/r.out.mpeg/r.out.mpeg.html
@@ -74,9 +74,9 @@ 
      NOTES
      
 
      Lawrence A. Rowe, Kevin Gong, Ketan Patel, and Dan Wallach Computer Science
 Division-EECS, Univ. of Calif. at Berkeley
 
      Available from Berkeley:
-http://biowiki.org/BerkeleyMpegEncoder
+http://biowiki.org/BerkeleyMpegEncoder (Wayback machine)
 
      or as part of the netpbm package (ppmtompeg):
-http://netpbm.sourceforge.net
+https://netpbm.sourceforge.net
 
 
diff --git a/scripts/v.in.geonames/v.in.geonames.html b/scripts/v.in.geonames/v.in.geonames.html
index a38aa770cc5..c8383c4bc3f 100644
--- a/scripts/v.in.geonames/v.in.geonames.html
+++ b/scripts/v.in.geonames/v.in.geonames.html
@@ -3,7 +3,7 @@ 
      DESCRIPTION
      
 v.in.geonames imports Geonames.org country files (Gazetteer
 data) into a GRASS vector points map. The country files can be
 downloaded from the
-GeoNames Data Dump
+GeoNames Data Dump
 Server. Only original files can be processed (unzip compressed
 file first). These Geonames files are encoded in UTF-8 which is
 maintained in the GRASS database.
@@ -35,8 +35,8 @@ 
      NOTES
      
 alternatenames    : alternatenames, comma separated varchar(4000)
 latitude          : latitude in decimal degrees (wgs84)
 longitude         : longitude in decimal degrees (wgs84)
-feature class     : see http://www.geonames.org/export/codes.html, char(1)
-feature code      : see http://www.geonames.org/export/codes.html, varchar(10)
+feature class     : see https://www.geonames.org/export/codes.html, char(1)
+feature code      : see https://www.geonames.org/export/codes.html, varchar(10)
 country code      : ISO-3166 2-letter country code, 2 characters
 cc2               : alternate country codes, comma separated, ISO-3166 2-letter country code, 60 characters
 admin1 code       : fipscode (subject to change to iso code), isocode for the us and ch, see file admin1Codes.txt for display names of this code; varchar(20)
@@ -46,7 +46,7 @@ 
      NOTES
      
 population        : integer
 elevation         : in meters, integer
 gtopo30           : average elevation of 30'x30' (ca 900mx900m) area in meters, integer
-timezone          : the timezone id (see file http://download.geonames.org/export/dump/timeZones.txt)
+timezone          : the timezone id (see file https://download.geonames.org/export/dump/timeZones.txt)
 modification date : date of last modification in yyyy-MM-dd format
 
      
 
@@ -55,7 +55,7 @@ 
      EXAMPLE
      
 Download and import geonames for Czech Republic.
 
 
      -wget http://download.geonames.org/export/dump/CZ.zip
+wget https://download.geonames.org/export/dump/CZ.zip
 unzip CZ.zip
 
 v.in.geonames input=CZ.txt output=geonames_cz
@@ -64,8 +64,8 @@ 
      EXAMPLE
      
 
      REFERENCES
      
 
 
 
 
      SEE ALSO
      
diff --git a/scripts/v.in.geonames/v.in.geonames.py b/scripts/v.in.geonames/v.in.geonames.py
index b6f5f47ace0..cf2e8c99705 100755
--- a/scripts/v.in.geonames/v.in.geonames.py
+++ b/scripts/v.in.geonames/v.in.geonames.py
@@ -8,9 +8,9 @@
 #               Converted to Python by Glynn Clements
 #
 # PURPOSE:      Import geonames.org dumps
-#               http://download.geonames.org/export/dump/
+#               https://download.geonames.org/export/dump/
 #
-#               Feature Codes: http://www.geonames.org/export/codes.html
+#               Feature Codes: https://www.geonames.org/export/codes.html
 #
 # COPYRIGHT:    (c) 2008-2014 Markus Neteler, GRASS Development Team
 #
@@ -69,7 +69,7 @@ def main():
     gs.message(_("Converting %d place names...") % num_places)
 
     # pump data into GRASS:
-    #  http://download.geonames.org/export/dump/readme.txt
+    #  https://download.geonames.org/export/dump/readme.txt
     #  The main 'geoname' table has the following fields :
     #  ---------------------------------------------------
     #  geonameid         : integer id of record in geonames database
@@ -78,8 +78,8 @@ def main():
     #  alternatenames    : alternatenames, comma separated varchar(4000)
     #  latitude          : latitude in decimal degrees (wgs84)
     #  longitude         : longitude in decimal degrees (wgs84)
-    #  feature class     : see http://www.geonames.org/export/codes.html, char(1)
-    #  feature code      : see http://www.geonames.org/export/codes.html, varchar(10)
+    #  feature class     : see https://www.geonames.org/export/codes.html, char(1)
+    #  feature code      : see https://www.geonames.org/export/codes.html, varchar(10)
     #  country code      : ISO-3166 2-letter country code, 2 characters
     #  cc2               : alternate country codes, comma separated, ISO-3166 2-letter country code, 60 characters
     #  admin1 code       : fipscode (subject to change to iso code), isocode for the us and ch, see file admin1Codes.txt for display names of this code; varchar(20)
@@ -89,7 +89,7 @@ def main():
     #  population        : integer
     #  elevation         : in meters, integer
     #  gtopo30           : average elevation of 30'x30' (ca 900mx900m) area in meters, integer
-    #  timezone          : the timezone id (see file http://download.geonames.org/export/dump/timeZones.txt)
+    #  timezone          : the timezone id (see file https://download.geonames.org/export/dump/timeZones.txt)
     #  modification date : date of last modification in yyyy-MM-dd format
 
     # geonameid|name|asciiname|alternatenames|latitude|longitude|featureclass|featurecode|countrycode|cc2|admin1code|admin2code|admin3code|admin4code|population|elevation|gtopo30|timezone|modificationdate
diff --git a/scripts/v.in.lines/v.in.lines.html b/scripts/v.in.lines/v.in.lines.html
index 2dff0a8263f..86a87c6dbcb 100644
--- a/scripts/v.in.lines/v.in.lines.html
+++ b/scripts/v.in.lines/v.in.lines.html
@@ -5,7 +5,7 @@ 
      DESCRIPTION
      
 
      NOTES
      
 
 Input ASCII coordinates are simply a series of "x y" data points.
-Lines are separated by a row containing "NaN NaN".
+Lines are separated by a row containing "NaN NaN".
 
 
      The user can import 3D lines by providing 3 columns of data in the input
 stream and using the -z flag.
diff --git a/scripts/v.in.mapgen/v.in.mapgen.html b/scripts/v.in.mapgen/v.in.mapgen.html
index af0b4a51c06..52f874cfe77 100644
--- a/scripts/v.in.mapgen/v.in.mapgen.html
+++ b/scripts/v.in.mapgen/v.in.mapgen.html
@@ -7,9 +7,9 @@ 
      NOTES
      
 
 This module only imports data into vector lines.
 
      The user can get coastline data in Mapgen or Matlab format from NOAA's Coastline
-Extractor at http://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html.
+Extractor at https://www.ngdc.noaa.gov/mgg/shorelines/shorelines.html.
 
      Matlab vector line maps are simply a series of "x y" data points. Lines
-are separated by a row containing NaN NaN.
+are separated by a row containing NaN NaN.
 
 Output from Matlab with this command:
 
      
diff --git a/scripts/v.in.wfs/v.in.wfs.html b/scripts/v.in.wfs/v.in.wfs.html
index eaa96c13780..fbee44ea6eb 100644
--- a/scripts/v.in.wfs/v.in.wfs.html
+++ b/scripts/v.in.wfs/v.in.wfs.html
@@ -35,7 +35,7 @@ 
      WFS import with API key
      
 v.in.wfs -l url="$URL"
 
      
 
-From that file we learn that the shipwreck layer is called "v:x633"
+From that file we learn that the shipwreck layer is called "v:x633"
 and that EPSG code 4326 (LatLong WGS84) is a supported SRS for this data layer.
 
 
      diff --git a/scripts/v.rast.stats/v.rast.stats.html b/scripts/v.rast.stats/v.rast.stats.html
index 966f7ae1a00..f9093158757 100644
--- a/scripts/v.rast.stats/v.rast.stats.html
+++ b/scripts/v.rast.stats/v.rast.stats.html
@@ -24,8 +24,8 @@ 
      NOTES
      
 
      The script stops if a (prefixed) upload column is already present in the
 vector map attribute table, unless otherwise instructed with the -c
 continue flag. The column prefix will be separated from the statistic name
-with an underscore. For example with a prefix of "elev" the sum
-column will be named elev_sum.
+with an underscore. For example with a prefix of "elev" the sum
+column will be named elev_sum.
 
      If a DBF database is being used, note that column names are restricted by the
 DBF specification to 10 characters. Therefore it is advised to be economical
 in the use of the column prefix when using DBF as any additional characters
@@ -81,4 +81,4 @@ 
      SEE ALSO
      
 
 
      AUTHOR
      
 
-Markus Neteler, CEA (for the EDEN EU/FP6 Project)
+Markus Neteler, CEA (for the EDEN EU/FP6 Project)
diff --git a/scripts/v.what.vect/v.what.vect.html b/scripts/v.what.vect/v.what.vect.html
index 0a4a88cca49..353431e3ce6 100644
--- a/scripts/v.what.vect/v.what.vect.html
+++ b/scripts/v.what.vect/v.what.vect.html
@@ -41,7 +41,7 @@ 
      EXAMPLES
      
 
      
 
      
 In this example, city names, population data and others from
-Geonames.org country files are
+Geonames.org country files are
 transferred to selected EU CORINE landuse/landcover classes
 ("Continuous urban fabric", 111, and "Discontinuous urban fabric", 112).
 Note: The example is in UTM projection to which the input maps have been
diff --git a/temporal/t.connect/t.connect.html b/temporal/t.connect/t.connect.html
index 2ac22aa31da..5ca9bdc0350 100644
--- a/temporal/t.connect/t.connect.html
+++ b/temporal/t.connect/t.connect.html
@@ -16,7 +16,7 @@ 
      NOTES
      
 Setting the connection with t.connect will not test the connection for validity.
 Hence a database connection will not be established.
 
      
-The connection values are stored in the mapset's VAR file.
+The connection values are stored in the mapset's VAR file.
 The -d flag will set the default
 TGIS connection parameters.
 A SQLite database "tgis/sqlite.db" will be created in the current mapset directory.
diff --git a/temporal/t.copy/t.copy.html b/temporal/t.copy/t.copy.html
index 9be8115a1e2..290f7661e3a 100644
--- a/temporal/t.copy/t.copy.html
+++ b/temporal/t.copy/t.copy.html
@@ -37,9 +37,4 @@ 
      SEE ALSO
      
 
 
      AUTHOR
      
 
-Markus Metz, mundialis
-
-
+Markus Metz, mundialis
diff --git a/temporal/t.merge/t.merge.html b/temporal/t.merge/t.merge.html
index b694d1a3203..ff24d1603f9 100644
--- a/temporal/t.merge/t.merge.html
+++ b/temporal/t.merge/t.merge.html
@@ -1,7 +1,7 @@
 
      DESCRIPTION
      
 
-This module is designed to register the maps of several input space
-time datasets in a single output dataset. The datasets to merge can be
+The t.merge module is designed to register the maps of several input
+space time datasets in a single output dataset. The datasets to merge can be
 either space time raster, 3D raster or vector datasets and must have
 the same temporal type (absolute or relative).
 
      
diff --git a/temporal/t.rast.algebra/t.rast.algebra.html b/temporal/t.rast.algebra/t.rast.algebra.html
index 1944d63baa3..e5786d9578c 100644
--- a/temporal/t.rast.algebra/t.rast.algebra.html
+++ b/temporal/t.rast.algebra/t.rast.algebra.html
@@ -590,7 +590,7 @@ 
      SEE ALSO
      
 
      REFERENCES
      
 
 The use of this module requires the following software to be installed:
-PLY(Python-Lex-Yacc)
+PLY(Python-Lex-Yacc)
 
 
      
 
      diff --git a/temporal/t.rast.extract/t.rast.extract.html b/temporal/t.rast.extract/t.rast.extract.html
index 1a3b6d84e5e..e7dcd7897c8 100644
--- a/temporal/t.rast.extract/t.rast.extract.html
+++ b/temporal/t.rast.extract/t.rast.extract.html
@@ -22,7 +22,7 @@ 
      DESCRIPTION
      
 
      NOTES
      
 
 The r.mapcalc sub-expression should not contain the left side
-"map =" of a full r.mapcalc expression, only the right
+"map =" of a full r.mapcalc expression, only the right
 side, eg.:
 
 
diff --git a/temporal/t.rast.mapcalc/t.rast.mapcalc.html b/temporal/t.rast.mapcalc/t.rast.mapcalc.html
index afbe1d04422..dbef6373aff 100644
--- a/temporal/t.rast.mapcalc/t.rast.mapcalc.html
+++ b/temporal/t.rast.mapcalc/t.rast.mapcalc.html
@@ -128,11 +128,11 @@ 
      NOTES
      
 
      EXAMPLES
      
 
 The following command creates a new space time raster dataset
-january_under_0 that will set to null all cells with
+january_under_0 that will set to null all cells with
 temperature above zero in the January maps while keeping all the rest
 as in the original time series. This will change the maximum values
 of all January maps in the new STRDS as compared to the original one,
-tempmean_monthly.
+tempmean_monthly.
 
 
       t.rast.mapcalc input=tempmean_monthly output=january_under_0 basename=january_under_0 \
diff --git a/temporal/t.rast.out.vtk/t.rast.out.vtk.html b/temporal/t.rast.out.vtk/t.rast.out.vtk.html
index c0a000cf3e5..9746406f093 100644
--- a/temporal/t.rast.out.vtk/t.rast.out.vtk.html
+++ b/temporal/t.rast.out.vtk/t.rast.out.vtk.html
@@ -1,6 +1,6 @@
 
      DESCRIPTION
      
 
-This module exports all maps registered in a space time raster datasets
+t.rast.out.vtk exports all maps registered in a space time raster datasets
 as VTK legacy files using a numerical numbering scheme. The VTK files
 can be visualized with any VTK based visualize. Our preferred tool is
 ParaView. The VTK legacy files are created using r.out.vtk.
diff --git a/temporal/t.rast.univar/t.rast.univar.html b/temporal/t.rast.univar/t.rast.univar.html
index 7ecc0ed3316..ee1f6940764 100644
--- a/temporal/t.rast.univar/t.rast.univar.html
+++ b/temporal/t.rast.univar/t.rast.univar.html
@@ -56,5 +56,5 @@ 
      SEE ALSO
      
 
 
      AUTHOR
      
 
-Sören Gebbert, Thünen Institute of Climate-Smart Agriculture
-Stefan Blumentrath, (Support for zones, parallel processing, and spatial relations)
+Sören Gebbert, Thünen Institute of Climate-Smart Agriculture
      
+Stefan Blumentrath (support for zones, parallel processing, and spatial relations)
diff --git a/temporal/t.rast3d.algebra/t.rast3d.algebra.html b/temporal/t.rast3d.algebra/t.rast3d.algebra.html
index 35680946f8d..29ec831cf68 100644
--- a/temporal/t.rast3d.algebra/t.rast3d.algebra.html
+++ b/temporal/t.rast3d.algebra/t.rast3d.algebra.html
@@ -8,7 +8,7 @@ 
      NOTES
      
 
 The module expects an expression as input parameter in the following form:
 
      
-"result = expression"
+"result = expression"
 
      
 
 The statement structure is exact the same as of t.rast.algebra,
@@ -17,7 +17,7 @@ 
      NOTES
      
 
 
      REFERENCES
      
 
-PLY(Python-Lex-Yacc)
+PLY(Python-Lex-Yacc)
 
 
      SEE ALSO
      
 
diff --git a/temporal/t.rast3d.univar/t.rast3d.univar.html b/temporal/t.rast3d.univar/t.rast3d.univar.html
index d9ccd43e154..a46f90507fb 100644
--- a/temporal/t.rast3d.univar/t.rast3d.univar.html
+++ b/temporal/t.rast3d.univar/t.rast3d.univar.html
@@ -15,5 +15,5 @@ 
      SEE ALSO
      
 
 
      AUTHOR
      
 
-Sören Gebbert, Thünen Institute of Climate-Smart Agriculture
-Stefan Blumentrath, (Support for zones)
+Sören Gebbert, Thünen Institute of Climate-Smart Agriculture
      
+Stefan Blumentrath (support for zones)
diff --git a/temporal/t.register/t.register.html b/temporal/t.register/t.register.html
index ca6c3339db3..31e11fb5962 100644
--- a/temporal/t.register/t.register.html
+++ b/temporal/t.register/t.register.html
@@ -275,9 +275,7 @@ 
      Importing and registering ECA&D climatic data
      
 Europe based on ECA&D information.
 
 Download and decompress mean temperature data from:
-here
-by accepting their
-Terms of use.
+here.
 
 
       # import E-OBS V12 into a lat-long project (alternatively, use r.external)
diff --git a/temporal/t.remove/t.remove.html b/temporal/t.remove/t.remove.html
index 3d9a9be56f7..09aeb53cefc 100644
--- a/temporal/t.remove/t.remove.html
+++ b/temporal/t.remove/t.remove.html
@@ -3,7 +3,7 @@ 
      DESCRIPTION
      
 The module t.remove removes space time datasets (STRDS, STR3DS,
 STVDS) from the temporal database. In other words, by default it deletes
 the relevant database entries. It can also unregister maps from temporal
-database using the recursive mode -r (recursive)
+database using the recursive mode -r (recursive).
 
      
 Optionally, also the raster, 3D raster and vector maps of the space time
 datasets can be removed from the current mapset using the -d (delete)
@@ -22,23 +22,23 @@ 
      EXAMPLE
      
 raster maps) are removed:
 
 
      -#Create new and empty STRDS
+# Create new and empty STRDS
 t.create output=precip_months_sum semantictype=mean \
   title="Monthly sum of precipitation" \
   description="Monthly sum of precipitation for the \
   North Carolina sample data"
 
-#Register maps from sample dataset (selecting a subset with g.list)
+# Register maps from sample dataset (selecting a subset with g.list)
 t.register -i type=raster input=precip_months_sum \
   maps=$(g.list type=raster pattern="201*_precip" separator=comma) \
   start="2010-01-01" increment="1 months"
 
-#Create some new data by aggregating with 1 years granularity
+# Create some new data by aggregating with 1 years granularity
 t.rast.aggregate input=precip_months_sum \
-  output=precip_years_sum basename=precip_years_sum granularity="1 \
-  years" method=sum
+  output=precip_years_sum basename=precip_years_sum \
+  granularity="1 years" method=sum
 
-#Remove all newly produced data:
+# Remove all newly produced data:
 
 # a) the aggregated STRDS with 1 years granularity along with its raster maps
 t.remove -df type=strds input=precip_years_sum
diff --git a/temporal/t.rename/t.rename.html b/temporal/t.rename/t.rename.html
index f7270c0741c..98ec45270bd 100644
--- a/temporal/t.rename/t.rename.html
+++ b/temporal/t.rename/t.rename.html
@@ -1,7 +1,8 @@
 
      DESCRIPTION
      
 
-This module renames space time datasets of different types (STRDS, STVDS, STR3DS)
-and updates the space time dataset register entries of the registered maps.
+The t.rename module renames space time datasets of different
+types (STRDS, STVDS, STR3DS) and updates the space time dataset register
+entries of the registered maps.
 
 
      NOTES
      
 
@@ -12,7 +13,7 @@ 
      EXAMPLE
      
 A new vector space time dataset will be created, renamed and in the end removed
 
 
      -#Create new and empty STVDS
+# Create new and empty STVDS
 t.create type=stvds output=toberenamed semantictype=mean \
   title="Example to rename" \
   description="This is an example just to show how rename"
diff --git a/temporal/t.sample/t.sample.html b/temporal/t.sample/t.sample.html
index 14003800c15..0ae2adb1d84 100644
--- a/temporal/t.sample/t.sample.html
+++ b/temporal/t.sample/t.sample.html
@@ -1,6 +1,6 @@
 
      DESCRIPTION
      
 
-The purpose of this module is to compute and to show spatio-temporal
+The purpose of t.sample is to compute and to show spatio-temporal
 relations between space time datasets of different type. Several input
 space time datasets are sampled by a sample space time dataset
 using temporal topological relations. The types of the input space time
diff --git a/temporal/t.select/t.select.html b/temporal/t.select/t.select.html
index 04b74ff2b72..bef3af167e3 100644
--- a/temporal/t.select/t.select.html
+++ b/temporal/t.select/t.select.html
@@ -6,7 +6,7 @@ 
      DESCRIPTION
      
 
      PROGRAM USE
      
 The module expects an expression as input parameter in the following form:
 
      
-"result = expression"
+"result = expression"
 
      
 
 The statement structure is similar to r.mapcalc, see r.mapcalc.
@@ -359,7 +359,7 @@ 
      EXAMPLES
      
 
 
      REFERENCES
      
 
-PLY(Python-Lex-Yacc)
+PLY(Python-Lex-Yacc)
 
      
 Gebbert, S., Leppelt, T., Pebesma, E., 2019. A topology based spatio-temporal map algebra for
 big data analysis. Data 4, 86. https://doi.org/10.3390/data4020086
diff --git a/temporal/t.support/t.support.html b/temporal/t.support/t.support.html
index be9e45b9d42..e7958797cb5 100644
--- a/temporal/t.support/t.support.html
+++ b/temporal/t.support/t.support.html
@@ -1,6 +1,7 @@
 
      DESCRIPTION
      
 
-This module is dedicated to modify and update the metadata of a space time dataset.
+The t.support module is dedicated to modify and update the metadata of
+a space time dataset.
 
      
 The title, description and the semantic type can be modified.
 
      
diff --git a/temporal/t.unregister/t.unregister.html b/temporal/t.unregister/t.unregister.html
index c6f59a9f1fc..b54782e592d 100644
--- a/temporal/t.unregister/t.unregister.html
+++ b/temporal/t.unregister/t.unregister.html
@@ -1,7 +1,7 @@
 
      DESCRIPTION
      
 
-This module is designed to unregister raster, 3D raster and vector map
-layers from space time datasets and the temporal database.
+The t.unregister module is designed to unregister raster, 3D raster
+and vector map layers from space time datasets and the temporal database.
 
 
      
 Map layer that should be unregistered from the temporal database can be
diff --git a/temporal/t.upgrade/t.upgrade.html b/temporal/t.upgrade/t.upgrade.html
index 5b0517a001a..1fd6e4986ca 100644
--- a/temporal/t.upgrade/t.upgrade.html
+++ b/temporal/t.upgrade/t.upgrade.html
@@ -1,7 +1,7 @@
 
      DESCRIPTION
      
 
-This module upgrades the temporal database in the current mapset
-from version 2 (default in GRASS 7) to 3 (default in GRASS 8).
+The t.upgrade module upgrades the temporal database in the current
+mapset from version 2 (default in GRASS 7) to 3 (default in GRASS 8).
 The version 3 introduces a semantic label support, see
 i.band.library for details.
 
diff --git a/temporal/t.vect.algebra/t.vect.algebra.html b/temporal/t.vect.algebra/t.vect.algebra.html
index 89453068a61..df91dfe0d62 100644
--- a/temporal/t.vect.algebra/t.vect.algebra.html
+++ b/temporal/t.vect.algebra/t.vect.algebra.html
@@ -442,7 +442,7 @@ 
      Examples: 
      
 
 
      REFERENCES
      
 
-PLY(Python-Lex-Yacc)
+PLY(Python-Lex-Yacc)
 
 
      SEE ALSO
      
 
diff --git a/temporal/t.vect.extract/t.vect.extract.html b/temporal/t.vect.extract/t.vect.extract.html
index c6b7716cf02..3904cd6800b 100644
--- a/temporal/t.vect.extract/t.vect.extract.html
+++ b/temporal/t.vect.extract/t.vect.extract.html
@@ -7,7 +7,7 @@ 
      DESCRIPTION
      
 
      EXAMPLE
      
 
 In the following example a new space time vector dataset will be create
-with all the data later than 2000:
+with all the data later than the year 2000:
 
 
       t.vect.extract input=shoreline where="start_time > 2000" \
diff --git a/temporal/t.vect.list/t.vect.list.html b/temporal/t.vect.list/t.vect.list.html
index 0e7211671a6..4b33bbc3626 100644
--- a/temporal/t.vect.list/t.vect.list.html
+++ b/temporal/t.vect.list/t.vect.list.html
@@ -2,7 +2,7 @@ 
      DESCRIPTION
      
 
 
 
-This module provides the same functionality as
+The t.vect.list module provides the same functionality as
 t.rast.list, the only difference is the
 vector map layer metadata.
 
diff --git a/temporal/t.vect.observe.strds/t.vect.observe.strds.html b/temporal/t.vect.observe.strds/t.vect.observe.strds.html
index e1ca0a6c6c3..c5e923af7e2 100644
--- a/temporal/t.vect.observe.strds/t.vect.observe.strds.html
+++ b/temporal/t.vect.observe.strds/t.vect.observe.strds.html
@@ -94,7 +94,7 @@ 
      EXAMPLE
      
  +----------------------------------------------------------------------------+
  | Name:            precip_stations_monthly                                   |
  | Mapset:          climate_2009_2012                                         |
- | Project:        nc_spm_temporal_workshop                                  |
+ | Project:         nc_spm_temporal_workshop                                  |
  | Database:        /grassdata                                                |
  | Title:           North Carolina 30 year precipitation normals (3D)         |
  | Map scale:       1:1                                                       |
diff --git a/utils/g.html2man/htmltags.txt b/utils/g.html2man/htmltags.txt
deleted file mode 100644
index 1ecbb475c13..00000000000
--- a/utils/g.html2man/htmltags.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-List of tags supported by g.html2man
-
-
-<HEADER>
-<HEAD>
-<BODY>
-<BLINK>
-<A HREF="#toc"></A>
-<PRE>
-<IMG SRC=>
-<A NAME="toc">
-<HR>
-<H2>
-<H3>
-<BR>
-<BR>
-<DT>
-<DD>
-<LI>
-<UL>
-<OL>
-<B>
-<I>
-<P>
- 
-
-Hackish:
-<table>
diff --git a/vector/v.buffer/v.buffer.html b/vector/v.buffer/v.buffer.html
index 8870cd335c5..b2e11ac47cd 100644
--- a/vector/v.buffer/v.buffer.html
+++ b/vector/v.buffer/v.buffer.html
@@ -33,7 +33,7 @@ <h2>NOTES</h2>
 <i>For advanced users:</i> the built-in buffer algorithm is no longer
 used, as we use GEOS instead. If GRASS was not compiled with GEOS support
 or the <a href="variables.html">environmental
-variable</a> <tt>GRASS_VECTOR_BUFFER</tt> is defined, then GRASS
+variable</a> <code>GRASS_VECTOR_BUFFER</code> is defined, then GRASS
 generates buffers using the built-in buffering algorithm (which is still
 buggy for some input data).
 
diff --git a/vector/v.build/v.build.html b/vector/v.build/v.build.html
index c66da69110a..20fd726d44a 100644
--- a/vector/v.build/v.build.html
+++ b/vector/v.build/v.build.html
@@ -76,7 +76,8 @@ <h2>SEE ALSO</h2>
 <a href="v.build.all.html">v.build.all</a>,
 <a href="v.build.polylines.html">v.build.polylines</a>,
 <a href="v.edit.html">v.edit</a>,
-<a href="v.split.html">v.split</a>
+<a href="v.split.html">v.split</a>,
+<a href="v.support.html">v.support</a>
 </em>
 
 <p>See also <em><a href="wxGUI.vdigit.html">wxGUI vector digitizer</a></em>.
diff --git a/vector/v.cluster/v.cluster.html b/vector/v.cluster/v.cluster.html
index 235e9491b1e..fd70f1ebaa9 100644
--- a/vector/v.cluster/v.cluster.html
+++ b/vector/v.cluster/v.cluster.html
@@ -20,7 +20,9 @@ <h2>DESCRIPTION</h2>
 <b>distance</b> or <b>method=density</b> if clusters should be created
 separately for each observed density (distance to the farthest neighbor).
 
-<h4>dbscan</h4>
+<h3>Clustering methods</h3>
+
+<h4>dbscan method</h4>
 The <a href="https://en.wikipedia.org/wiki/DBSCAN">Density-Based Spatial
 Clustering of Applications with Noise</a> is a commonly used clustering
 algorithm. A new cluster is started for a point with at least
@@ -29,12 +31,12 @@ <h4>dbscan</h4>
 least <i>min</i> - 1 neighbors are within the maximum distance for each
 point already in the cluster.
 
-<h4>dbscan2</h4>
+<h4>dbscan2 method</h4>
 Similar to <i>dbscan</i>, but here it is sufficient if the resultant
 cluster consists of at least <b>min</b> points, even if no point in the
 cluster has at least <i>min - 1</i> neighbors within <b>distance</b>.
 
-<h4>density</h4>
+<h4>density method</h4>
 This method creates clusters according to their point density. The
 maximum distance is not used. Instead, the points are sorted ascending
 by the distance to their farthest neighbor (core distance), inspecting
@@ -44,7 +46,7 @@ <h4>density</h4>
 own maximum distance. This method can identify clusters with different
 densities and can create nested clusters.
 
-<h4>optics</h4>
+<h4>optics method</h4>
 This method is
 <a href="https://en.wikipedia.org/wiki/OPTICS_algorithm">Ordering Points to
 Identify the Clustering Structure</a>. It is controlled by the number
@@ -75,7 +77,7 @@ <h4>optics</h4>
 cluster. The order of the input points is arbitrary and can thus
 influence the resultant clusters.
 
-<h4>optics2</h4>
+<h4>optics2 method</h4>
 <b>EXPERIMENTAL</b> This method is similar to OPTICS, minimizing the
 reachability of each point. Points are reconnected if their
 reachability can be reduced. Contrary to OPTICS, a cluster's seed is
@@ -176,6 +178,7 @@ <h2>EXAMPLE</h2>
 
 Generate random points for analysis (100 points per area), use different
 method for clustering and visualize using color stored the attribute table.
+
 <div class="code"><pre>
 # pick a subregion of the vector urbanarea
 g.region -p n=272950 s=188330 w=574720 e=703090 res=10
diff --git a/vector/v.colors/v.colors.html b/vector/v.colors/v.colors.html
index 440ed5763ec..654413ba040 100644
--- a/vector/v.colors/v.colors.html
+++ b/vector/v.colors/v.colors.html
@@ -42,7 +42,7 @@ <h2>EXAMPLES</h2>
 
 <h3>Define color table based on categories</h3>
 
-Define color table <tt>wave</tt> based on categories from layer 1
+Define color table <code>wave</code> based on categories from layer 1
 
 <div class="code"><pre>
 v.colors map=soils_general layer=1 color=wave
@@ -50,8 +50,8 @@ <h3>Define color table based on categories</h3>
 
 <h3>Define color table based on attribute values</h3>
 
-Define color table <tt>ryg</tt> based on values from attribute
-column <tt>AREA</tt>. Attribute table is linked to layer 1.
+Define color table <code>ryg</code> based on values from attribute
+column <code>AREA</code>. Attribute table is linked to layer 1.
 
 <div class="code"><pre>
 v.to.db map=soils_general layer=1 option=area column=AREA
@@ -60,7 +60,7 @@ <h3>Define color table based on attribute values</h3>
 
 <h3>Define color table stored as RGB values in attribute table</h3>
 
-Write color values to the attribute table (column <tt>GRASSRGB</tt>)
+Write color values to the attribute table (column <code>GRASSRGB</code>)
 instead of creating color table.
 
 <div class="code"><pre>
@@ -145,7 +145,7 @@ <h2>SEE ALSO</h2>
 page <a href="https://grasswiki.osgeo.org/wiki/Color_tables">Color
 tables</a> (from GRASS User Wiki)
 
-<p><a href="http://colorbrewer.org">ColorBrewer</a> is an online tool designed to
+<p><a href="https://colorbrewer2.org">ColorBrewer</a> is an online tool designed to
 help people select good color schemes for maps and other graphics.
 
 <h2>AUTHORS</h2>
diff --git a/vector/v.db.select/v.db.select.html b/vector/v.db.select/v.db.select.html
index 13bbbbb1b78..8447259be3b 100644
--- a/vector/v.db.select/v.db.select.html
+++ b/vector/v.db.select/v.db.select.html
@@ -16,7 +16,7 @@ <h4>Plain text</h4>
 table using the <em>v.db.select</em> GUI dialog.
 
 <p>
-The individual fields (attribute values) are separated by a pipe (<tt>|</tt>)
+The individual fields (attribute values) are separated by a pipe (<code>|</code>)
 which can be customized using the <b>separator</b> option.
 The records (rows) are separated by newlines.
 
@@ -32,8 +32,8 @@ <h4>Plain text</h4>
 </pre></div>
 
 When escaping is enabled, the following characters in the fields are escaped:
-backslash (<tt>\\</tt>), carriage return (<tt>\r</tt>), line feed (<tt>\n</tt>),
-tabulator (<tt>\t</tt>), form feed (<tt>\f</tt>), and backslash (<tt>\b</tt>).
+backslash (<code>\\</code>), carriage return (<code>\r</code>), line feed (<code>\n</code>),
+tabulator (<code>\t</code>), form feed (<code>\f</code>), and backslash (<code>\b</code>).
 
 <p>
 No quoting or escaping is performed by default, so if these characters are in
@@ -50,7 +50,7 @@ <h4>Plain text</h4>
 <h4>CSV</h4>
 
 CSV (comma-separated values) has many variations. This module by default produces
-CSV with comma (<tt>,</tt>) as the field separator (delimiter). All text fields
+CSV with comma (<code>,</code>) as the field separator (delimiter). All text fields
 (based on the type) are quoted with double quotes. Double quotes in fields are
 represented as two double quotes. Newline characters in the fields are present
 as-is in the output. Header is included by default containing column names.
@@ -95,11 +95,11 @@ <h4>JSON</h4>
 tabulator, form feed, backslash, and double quote) for string values.
 Numbers in the database such as integers and doubles are represented as numbers,
 while texts (TEXT, VARCHAR, etc.) and dates in the database are represented
-as strings in JSON. NULL values in database are represented as JSON <tt>null</tt>.
+as strings in JSON. NULL values in database are represented as JSON <code>null</code>.
 Indentation and newlines in the output are minimal and not guaranteed.
 
 <p>
-Records which are the result of the query are stored under key <tt>records</tt>
+Records which are the result of the query are stored under key <code>records</code>
 as an array (list) of objects (collections of key-value pairs).
 The keys for attributes are lowercase or uppercase depending on how
 the columns were defined in the database.
@@ -174,7 +174,7 @@ <h4>Vertical plain text</h4>
 the vertical separator (<b>vertical_separator</b> option).
 
 <p>
-Example with (horizontal) separator <tt>=</tt> and vertical separator <tt>newline</tt>:
+Example with (horizontal) separator <code>=</code> and vertical separator <code>newline</code>:
 
 <div class="code"><pre>
 cat=1
diff --git a/vector/v.decimate/v.decimate.html b/vector/v.decimate/v.decimate.html
index e1bad03acbf..9f7b0001307 100644
--- a/vector/v.decimate/v.decimate.html
+++ b/vector/v.decimate/v.decimate.html
@@ -138,4 +138,4 @@ <h2>SEE ALSO</h2>
 
 <h2>AUTHOR</h2>
 
-Vaclav Petras, <a href="http://geospatial.ncsu.edu/osgeorel/">NCSU OSGeoREL</a>
+Vaclav Petras, <a href="https://geospatial.ncsu.edu/geoforall/">NCSU GeoForAll Lab</a>
diff --git a/vector/v.delaunay/v.delaunay.html b/vector/v.delaunay/v.delaunay.html
index 2c8b8db4531..de033403816 100644
--- a/vector/v.delaunay/v.delaunay.html
+++ b/vector/v.delaunay/v.delaunay.html
@@ -30,6 +30,8 @@ <h2>SEE ALSO</h2>
 <a href="v.voronoi.html">v.voronoi</a>,
 <a href="v.hull.html">v.hull</a>
 </em>
+<p>
+<a href="https://en.wikipedia.org/wiki/Delaunay_triangulation">Delaunay triangulation (Wikipedia)</a>
 
 <h2>AUTHORS</h2>
 
diff --git a/vector/v.distance/v.distance.html b/vector/v.distance/v.distance.html
index 2be5c1bd537..582887d23f3 100644
--- a/vector/v.distance/v.distance.html
+++ b/vector/v.distance/v.distance.html
@@ -152,10 +152,10 @@ <h3>Univariate statistics on results</h3>
 
 Create a vector map containing connecting lines and investigate mean
 distance to targets. An alternative solution is to use
-the <tt>v.distance upload=dist</tt> option to upload distances into
+the <code>v.distance upload=dist</code> option to upload distances into
 the <i>bugs</i> vector directly, then run v.univar on that. Also note
-you can upload two columns at a time, e.g. <tt>v.distance
-upload=cat,dist column=nearest_id,dist_to_nr</tt>.
+you can upload two columns at a time, e.g. <code>v.distance
+upload=cat,dist column=nearest_id,dist_to_nr</code>.
 
 <div class="code"><pre>
 # create working copy
diff --git a/vector/v.edit/v.edit.html b/vector/v.edit/v.edit.html
index 3768e65ad4d..7597e157452 100644
--- a/vector/v.edit/v.edit.html
+++ b/vector/v.edit/v.edit.html
@@ -27,7 +27,7 @@ <h2>DESCRIPTION</h2>
 selects all features (and prints their id's to standard output)
 covered by two bounding boxes (center at 599505,4921010 and
 603389.0625,4918292.1875, size 2*10000) with attribute
-<tt>label='interstate'</tt>.
+<code>label='interstate'</code>.
 
 <h2>NOTES</h2>
 
@@ -108,7 +108,7 @@ <h3>Tool description</h3>
     <li><b>break</b> - Split given vector line or boundary into two
     lines on location given by <b>coords</b>. If <b>coords</b> not
     given, breaks all selected lines at each intersection (based
-    on <em><a href="v.clean.html">v.clean</a></em>, <tt>tool=break</tt>).</li>
+    on <em><a href="v.clean.html">v.clean</a></em>, <code>tool=break</code>).</li>
 
     <li><b>snap</b> - Snap vector features in given threshold. See
     also module <em><a href="v.clean.html">v.clean</a></em>. Note that this
diff --git a/vector/v.external.out/v.external.out.html b/vector/v.external.out/v.external.out.html
index f9c3575aa88..9241a6bda43 100644
--- a/vector/v.external.out/v.external.out.html
+++ b/vector/v.external.out/v.external.out.html
@@ -9,30 +9,30 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-Number of available output formats (<tt>v.external.out -f</tt>)
+Number of available output formats (<code>v.external.out -f</code>)
 depends on OGR installation. 'PostgreSQL' format is presented also
 when GRASS comes with PostgreSQL support (check for '--with-postgres'
-in <tt>g.version -b</tt> output).
+in <code>g.version -b</code> output).
 
 <p>
 To store geometry and attribute data in PostGIS database ('PostgreSQL'
 format) GRASS uses built-in <em>GRASS-PostGIS data
 provider</em>. PostGIS data can be written also by OGR library
-when <tt>GRASS_VECTOR_OGR</tt> environmental variable is defined or
+when <code>GRASS_VECTOR_OGR</code> environmental variable is defined or
 GRASS is not compiled with PostgreSQL support.
 
 <p>
 Creation <b>options</b> refer to the output format specified
 by <b>format</b> option. See the list of valid creation options
-at <a href="https://gdal.org/drivers/vector/">OGR formats
+at <a href="https://gdal.org/en/stable/drivers/vector/">OGR formats
 specification page</a>, example
-for <a href="https://gdal.org/drv_shapefile.html">ESRI
+for <a href="https://gdal.org/en/stable/drivers/vector/shapefile.html">ESRI
 Shapefile</a>
-or <a href="https://gdal.org/drv_pg.html">PostgreSQL/PostGIS</a>
+or <a href="https://gdal.org/en/stable/drivers/vector/pg.html">PostgreSQL/PostGIS</a>
 format (section "Layer Creation Options"). Options are
-comma-separated pairs (<tt>key=value</tt>), the options are
+comma-separated pairs (<code>key=value</code>), the options are
 case-insensitive,
-eg. <tt>options="SCHEMA=myschema,FID=cat"</tt>.
+eg. <code>options="SCHEMA=myschema,FID=cat"</code>.
 
 <h3>PostgreSQL/PostGIS Creation Options</h3>
 
@@ -40,39 +40,39 @@ <h3>PostgreSQL/PostGIS Creation Options</h3>
 (<b>format=PostgreSQL</b>) supports different creation <b>options</b>
 compared to PostgreSQL/PostGIS driver from OGR library:
 <ul>
-  <li><tt>SCHEMA=<name></tt> - name of schema where to create
+  <li><code>SCHEMA=<name></code> - name of schema where to create
   feature tables. If schema doesn't exists, it's automatically created
   when writing PostGIS data.</li>
-  <li><tt>FID=<column></tt> - name of column which will be used as
-  primary key (feature id), default: <tt>fid</tt></li>
-  <li><tt>GEOMETRY_NAME=<column></tt> name of column which will
-  be used for storing geometry data in feature table, default: <tt>geom</tt></li>
-  <li><tt>SPATIAL_INDEX=YES|NO</tt> - enable/disable spatial index on geometry column, default: YES</li>
-  <li><tt>PRIMARY_KEY=YES|NO</tt> - enable/disable primary key on FID column, default: YES</li>
-  <li><tt>SRID=<value></tt> - spatial reference identifier,
+  <li><code>FID=<column></code> - name of column which will be used as
+  primary key (feature id), default: <code>fid</code></li>
+  <li><code>GEOMETRY_NAME=<column></code> name of column which will
+  be used for storing geometry data in feature table, default: <code>geom</code></li>
+  <li><code>SPATIAL_INDEX=YES|NO</code> - enable/disable spatial index on geometry column, default: YES</li>
+  <li><code>PRIMARY_KEY=YES|NO</code> - enable/disable primary key on FID column, default: YES</li>
+  <li><code>SRID=<value></code> - spatial reference identifier,
   default: not defined</li>
-  <li><tt>TOPOLOGY=YES|NO</tt> - enable/disable
+  <li><code>TOPOLOGY=YES|NO</code> - enable/disable
   native <a href="https://grasswiki.osgeo.org/wiki/PostGIS_Topology">PostGIS
   topology</a>, default: NO</li>
 </ul>
 
-Options relevant only to topological output (<tt>TOPOLOGY=YES</tt>):
+Options relevant only to topological output (<code>TOPOLOGY=YES</code>):
 
 <ul>
-  <li><tt>TOPOSCHEMA_NAME=<schema name></tt> - name of PostGIS
-  Topology schema (relevant only for <tt>TOPOLOGY=YES</tt>),
-  default: <tt>topo_<input></tt></li>
-  <li><tt>TOPOGEOM_NAME=<column></tt> - name of column which
+  <li><code>TOPOSCHEMA_NAME=<schema name></code> - name of PostGIS
+  Topology schema (relevant only for <code>TOPOLOGY=YES</code>),
+  default: <code>topo_<input></code></li>
+  <li><code>TOPOGEOM_NAME=<column></code> - name of column which
   will be used for storing topogeometry data in feature table,
-  default: <tt>topo</tt></li>
-  <li><tt>TOPO_TOLERANCE=<value></tt> - tolerance for PostGIS
+  default: <code>topo</code></li>
+  <li><code>TOPO_TOLERANCE=<value></code> - tolerance for PostGIS
   Topology schema,
-  see <a href="http://www.postgis.net/docs/manual-2.0/CreateTopology.html">CreateTopology</a>
-  function for defails, default: <tt>0</tt></li>
-  <li><tt>TOPO_GEO_ONLY=YES|NO</tt> - store in PostGIS Topology schema
-  only data relevant to Topo-Geo data model, default: <tt>NO</tt></li>
-  <li><tt>SIMPLE_FEATURE=YES|NO</tt> - build simple features geometry
-  in <tt>GEOMETRY_NAME</tt> column from topogeometry data, default:
+  see <a href="https://postgis.net/docs/CreateTopology.html">CreateTopology</a>
+  function for defails, default: <code>0</code></li>
+  <li><code>TOPO_GEO_ONLY=YES|NO</code> - store in PostGIS Topology schema
+  only data relevant to Topo-Geo data model, default: <code>NO</code></li>
+  <li><code>SIMPLE_FEATURE=YES|NO</code> - build simple features geometry
+  in <code>GEOMETRY_NAME</code> column from topogeometry data, default:
   NO</li>
 </ul>
 
@@ -122,7 +122,7 @@ <h3>PostGIS (simple features)</h3>
 # do some processing...
 </pre></div>
 
-<i>Note:</i> If the environment variable <tt>GRASS_VECTOR_OGR</tt>
+<i>Note:</i> If the environment variable <code>GRASS_VECTOR_OGR</code>
 is defined, or GRASS is compiled without PostgreSQL support then GRASS
 will use PostgreSQL driver from OGR library for reading and writing
 PostGIS data.
@@ -181,7 +181,7 @@ <h2>REFERENCES</h2>
 
 <ul>
   <li><a href="https://trac.osgeo.org/grass/wiki/Grass7/VectorLib/OGRInterface">GRASS-OGR data provider</a></li>
-  <li><a href="https://gdal.org/api/">OGR vector library C API</a> documentation</li>
+  <li><a href="https://gdal.org/en/stable/api/">OGR vector library C API</a> documentation</li>
   <li><a href="https://trac.osgeo.org/grass/wiki/Grass7/VectorLib/PostGISInterface">GRASS-PostGIS data provider</a></li>
   <li><a href="https://www.postgresql.org/docs/9.1/static/libpq.html">libpq - C Library</a></li>
 </ul>
diff --git a/vector/v.external/v.external.html b/vector/v.external/v.external.html
index 200d3726363..da39db7dc0f 100644
--- a/vector/v.external/v.external.html
+++ b/vector/v.external/v.external.html
@@ -47,7 +47,7 @@ <h3>Supported OGR vector formats</h3>
 </pre></div>
 
 For details see
-<a href="https://gdal.org/drivers/vector/">GDAL web site</a>.
+<a href="https://gdal.org/en/stable/drivers/vector/">GDAL web site</a>.
 
 <h2>EXAMPLES</h2>
 
@@ -64,7 +64,7 @@ <h3>PostGIS layers</h3>
 
 By default, PostGIS links are created by built-in PostGIS support,
 ie. using <em>GRASS-PostGIS data driver</em>. If the environment
-variable <tt>GRASS_VECTOR_OGR</tt> exists, or GRASS is compiled
+variable <code>GRASS_VECTOR_OGR</code> exists, or GRASS is compiled
 without PostgreSQL support then GRASS will use OGR-PostgreSQL driver
 for creating a link.
 
@@ -124,7 +124,7 @@ <h3>Linking subset of features</h3>
 
 <h2>REFERENCES</h2>
 
-<a href="https://gdal.org/api/">OGR vector library C
+<a href="https://gdal.org/en/stable/api/">OGR vector library C
 API</a> documentation
 
 <h2>SEE ALSO</h2>
@@ -142,7 +142,7 @@ <h2>SEE ALSO</h2>
 <p>
 <a href="https://gdal.org/">GDAL Library</a>
 <br>
-<a href="http://postgis.org/">PostGIS</a>
+<a href="https://postgis.net/">PostGIS</a>
 
 <p>
 See
diff --git a/vector/v.in.ascii/v.in.ascii.html b/vector/v.in.ascii/v.in.ascii.html
index cd1ab9c7cf1..b6f0b24aa1f 100644
--- a/vector/v.in.ascii/v.in.ascii.html
+++ b/vector/v.in.ascii/v.in.ascii.html
@@ -24,9 +24,9 @@ <h2>NOTES</h2>
 The input is read from the file specified by the <b>input</b> option or
 from standard input.
 
-<p>The field separator may be a character, the word '<tt>tab</tt>'
-(or '<tt>\t</tt>') for tab, '<tt>space</tt>' (or ' ') for a blank,
-or '<tt>comma</tt>' (or ',') for a comma.
+<p>The field separator may be a character, the word '<code>tab</code>'
+(or '<code>\t</code>') for tab, '<code>space</code>' (or ' ') for a blank,
+or '<code>comma</code>' (or ',') for a comma.
 
 <p>An attribute table is only created if it is needed, i.e. when at
 least one attribute column is present in the input file besides
@@ -48,15 +48,15 @@ <h2>NOTES</h2>
 
 <p>If old version is requested, the <b>output</b> files
 from <em><a href="v.out.ascii.html">v.out.ascii</a></em> is placed in
-the <tt>$LOCATION/$MAPSET/dig_ascii/</tt>
-and <tt>$LOCATION/$MAPSET/dig_att</tt> directory.
+the <code>$LOCATION/$MAPSET/dig_ascii/</code>
+and <code>$LOCATION/$MAPSET/dig_att</code> directory.
 
 <h3>Import of files without category column</h3>
 
 If the input file does not contain a category column, there is the
 possibility to auto-generate these IDs (categories). To automatically
 add an additional column named 'cat', the <b>cat</b> parameter must be
-set to the virtual column number 0 (<tt>cat=0</tt>). This is the
+set to the virtual column number 0 (<code>cat=0</code>). This is the
 default action if the <b>cat</b> parameter is not set.
 
 <h3>Importing from a spreadsheet</h3>
@@ -68,9 +68,9 @@ <h3>Importing from a spreadsheet</h3>
 contains any header lines, such as column headings, the
 <b>skip</b> parameter should be used. These skipped header lines will
 be written to the map's history file for later reference (read with
-<tt>v.info -h</tt>). The skip option only works in <b>points</b> mode.
+<code>v.info -h</code>). The skip option only works in <b>points</b> mode.
 
-<p>Any line starting with the hash character ('<tt>#</tt>') will be treated as
+<p>Any line starting with the hash character ('<code>#</code>') will be treated as
 a comment and skipped completely if located in the main data file. If located
 in the header, as defined by the <b>skip</b> parameter, it will be treated as
 a header line and written to the history file.
@@ -82,7 +82,7 @@ <h3>Import of sexagesimal degree (degree, minutes, seconds, DMS)</h3>
 the positions are internally translated into decimal degrees during
 the import, the original DMS values are maintained in the attribute
 table. This requires both the latitude and the longitude columns to be
-defined as <tt>varchar()</tt>, not as numbers.  A warning will be
+defined as <code>varchar()</code>, not as numbers.  A warning will be
 issued which can be ignored. See <a href="vectorascii.html">GRASS
 ASCII vector format specification</a> for details.
 
@@ -280,7 +280,7 @@ <h3>Example 8 - point format mode</h3>
 
 <h2>REFERENCES</h2>
 
-<a href="sql.html">SQL command notes</a> for creating databases
+<a href="sql.html">SQL command notes</a> for creating databases,
 <br>
 <a href="vectorascii.html">GRASS ASCII vector format</a> specification
 
diff --git a/vector/v.in.lidar/v.in.lidar.html b/vector/v.in.lidar/v.in.lidar.html
index 72177b9f5ed..a71c02ee101 100644
--- a/vector/v.in.lidar/v.in.lidar.html
+++ b/vector/v.in.lidar/v.in.lidar.html
@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.in.lidar</em> converts LiDAR point clouds in LAS format to a GRASS
-vector, using the <a href="http://www.liblas.org">libLAS</a> library.
+vector, using the <a href="https://liblas.org">libLAS</a> library.
 The created vector is true 3D with x, y, z coordinates.
 
 <p>
@@ -80,8 +80,8 @@ <h2>Project Creation</h2>
 information, and if the LAS driver supports it. If the source dataset CRS does
 not match the CRS of the current project (previously called location)
 <em>v.in.lidar</em> will
-report an error message ("<tt>Coordinate reference system of dataset does not appear to
-match current project</tt>") and then report the PROJ_INFO parameters of
+report an error message ("<code>Coordinate reference system of dataset does not appear to
+match current project</code>") and then report the PROJ_INFO parameters of
 the source dataset.
 
 <p>If the user wishes to ignore the difference between the coordinate
@@ -105,30 +105,28 @@ <h2>NOTES</h2>
 
 <h2>EXAMPLE</h2>
 
-This example is analogous to the example used in the GRASS wiki page for
-<a href="https://grasswiki.osgeo.org/wiki/LIDAR#Import_LAS_as_vector_points">importing LAS as vector points</a>.
-<p>The sample LAS data are in the file "Serpent Mound Model LAS Data.las",
+The sample LAS data are in the file "Serpent Mound Model LAS Data.laz",
 available at
-<a href="http://www.appliedimagery.com/downloads/sampledata/Serpent%20Mound%20Model%20LAS%20Data.las">appliedimagery.com</a>
+<a href="https://github.com/PDAL/data/raw/4ee9ee43b195268a59113555908c1c0cdf955bd4/liblas/Serpent%20Mound%20Model%20LAS%20Data.laz">Serpent Mound Model LAS Data.laz</a>
 
 <div class="code"><pre>
-  # print LAS file info
-  v.in.lidar -p input="Serpent Mound Model LAS Data.las"
+# print LAS file info
+v.in.lidar -p input="Serpent Mound Model LAS Data.laz"
 
-  # create a project with CRS information of the LAS data
-  v.in.lidar -i input="Serpent Mound Model LAS Data.las" project=Serpent_Mound
+# create a project with CRS information of the LAS data
+v.in.lidar -i input="Serpent Mound Model LAS Data.laz" project=Serpent_Mound
 
-  # quit and restart GRASS in the newly created project "Serpent_Mound"
-  # real import of LiDAR LAS data, without topology and without attribute table
-  v.in.lidar -tb input="Serpent Mound Model LAS Data.las" output=Serpent_Mound_Model_pts
+# quit and restart GRASS in the newly created project "Serpent_Mound"
+# real import of LiDAR LAS data, without topology and without attribute table
+v.in.lidar -tb input="Serpent Mound Model LAS Data.laz" output=Serpent_Mound_Model_pts
 </pre></div>
 
 <h2>REFERENCES</h2>
 
 <a href="https://www.asprs.org/committee-general/laser-las-file-format-exchange-activities.html">
 ASPRS LAS format</a><br>
-<a href="http://www.liblas.org/">LAS library</a> <br>
-<a href="http://test.liblas.org/doxygen/liblas_8h.htm">LAS library C API</a> documentation
+<a href="https://liblas.org/">LAS library</a> <br>
+<a href="https://liblas.org/doxygen/liblas_8h.html">LAS library C API</a> documentation
 
 <h2>SEE ALSO</h2>
 
diff --git a/vector/v.in.ogr/v.in.ogr.html b/vector/v.in.ogr/v.in.ogr.html
index 2ab3ca938a6..e899a8a5701 100644
--- a/vector/v.in.ogr/v.in.ogr.html
+++ b/vector/v.in.ogr/v.in.ogr.html
@@ -23,11 +23,11 @@ <h3>Supported Vector Formats</h3>
 
 <em>v.in.ogr</em> uses the OGR library which supports various vector
 data formats including
-<a href="https://gdal.org/drivers/vector/shapefile.html">ESRI Shapefile</a>,
-<a href="https://gdal.org/drivers/vector/mitab.html">Mapinfo File</a>, UK .NTF,
+<a href="https://gdal.org/en/stable/drivers/vector/shapefile.html">ESRI Shapefile</a>,
+<a href="https://gdal.org/en/stable/drivers/vector/mitab.html">Mapinfo File</a>, UK .NTF,
 SDTS, TIGER, IHO S-57 (ENC), DGN, GML, GPX, AVCBin, REC, Memory, OGDI,
 and PostgreSQL, depending on the local OGR installation. For details
-see the <a href="https://gdal.org/drivers/vector/">OGR format overview</a>.
+see the <a href="https://gdal.org/en/stable/drivers/vector/">OGR format overview</a>.
 The <b>-f</b> prints a list of the vector formats supported
 by the system's OGR (Simple Features Library). The OGR (Simple Features
 Library) is part of the <a href="https://gdal.org">GDAL</a> library,
@@ -142,7 +142,7 @@ <h3>File encoding</h3>
 ISO8859_1 which may not be appropriate for many
 languages. Unfortunately it is not clear what other values may be
 appropriate (see example below). To change encoding the user can set
-up <tt><a href="https://gdal.org/user/configoptions.html">SHAPE_ENCODING</a></tt>
+up <code><a href="https://gdal.org/en/stable/user/configoptions.html">SHAPE_ENCODING</a></code>
 environmental variable or simply to define
 encoding value using <b>encoding</b> parameter.
 
@@ -257,7 +257,7 @@ <h3>PostGIS tables</h3>
 </pre></div>
 
 Generally, <em>v.in.ogr</em> just follows the
-<a href="https://gdal.org/drivers/vector/">format-specific</a>
+<a href="https://gdal.org/en/stable/drivers/vector/">format-specific</a>
 syntax defined by the OGR library.
 
 
@@ -265,14 +265,14 @@ <h3>PostGIS tables</h3>
 <h3>Default connection settings as datasource (PostgreSQL only)</h3>
 
 If datasource (<b>input</b>) is specified as 'PG:' and the default DB
-driver is <a href="grass-pg.html">PostgreSQL</a> (<tt>pg</tt>) than
+driver is <a href="grass-pg.html">PostgreSQL</a> (<code>pg</code>) than
 the connection string is determined from the default DB settings, see
 examples below.
 
 <p>
 For schema support, first set a default schema with
 <em><a href="db.connect.html">db.connect</a></em>. If schema support
-is used the schema name must be specified whenever a <tt>db.*</tt>
+is used the schema name must be specified whenever a <code>db.*</code>
 module is called. User and password for connection to the database can
 be specified by <em><a href="db.login.html">db.login</a></em>.
 
@@ -301,7 +301,7 @@ <h3>Default connection settings as datasource (PostgreSQL only)</h3>
 
 <h3>OpenStreetMap (OSM)</h3>
 
-<a href="https://gdal.org/drivers/vector/osm.html">OSM data</a> are available in
+<a href="https://gdal.org/en/stable/drivers/vector/osm.html">OSM data</a> are available in
 .osm (XML based) and .pbf (optimized binary) formats. The .pbf format
 is recommended because file sizes are smaller. The OSM driver will
 categorize features into 5 layers :
@@ -357,8 +357,8 @@ <h3>OpenStreetMap (OSM)</h3>
 
 <h3>Oracle Spatial</h3>
 
-Note that you have to set the environment-variables <tt>ORACLE_BASE,
-ORACLE_SID, ORACLE_HOME</tt> and <tt>TNS_ADMIN</tt> accordingly.
+Note that you have to set the environment-variables <code>ORACLE_BASE,
+ORACLE_SID, ORACLE_HOME</code> and <code>TNS_ADMIN</code> accordingly.
 
 <div class="code"><pre>
 v.in.ogr input=OCI:username/password@database_instance output=grasslayer layer=roads_oci
@@ -461,7 +461,7 @@ <h2>REFERENCES</h2>
 
 <ul>
   <li><a href="https://gdal.org/">OGR vector library</a></li>
-  <li><a href="https://gdal.org/api/vector_c_api.html">OGR vector library C API</a> documentation</li>
+  <li><a href="https://gdal.org/en/stable/api/vector_c_api.html">OGR vector library C API</a> documentation</li>
 </ul>
 
 <h2>SEE ALSO</h2>
diff --git a/vector/v.in.pdal/v.in.pdal.html b/vector/v.in.pdal/v.in.pdal.html
index 1042f8415bf..d5832c93cff 100644
--- a/vector/v.in.pdal/v.in.pdal.html
+++ b/vector/v.in.pdal/v.in.pdal.html
@@ -27,7 +27,7 @@ <h2>REFERENCES</h2>
     V. Petras, A. Petrasova, J. Jeziorska, H. Mitasova (2016):
     <em>Processing UAV and lidar point clouds in GRASS GIS</em>.
     XXIII ISPRS Congress 2016
-    [<a href="http://www.int-arch-photogramm-remote-sens-spatial-inf-sci.net/XLI-B7/945/2016/">ISPRS Archives</a>,
+    [<a href="https://doi.org/10.5194/isprs-archives-XLI-B7-945-2016">ISPRS Archives</a>,
     <a href="https://www.researchgate.net/publication/304340172_Processing_UAV_and_lidar_point_clouds_in_GRASS_GIS">ResearchGate</a>]</li>
 </ul>
 
@@ -43,4 +43,4 @@ <h2>SEE ALSO</h2>
 <h2>AUTHOR</h2>
 
 Vaclav Petras,
-<a href="http://geospatial.ncsu.edu/osgeorel/">NCSU GeoForAll Lab</a>
+<a href="https://geospatial.ncsu.edu/geoforall/">NCSU GeoForAll Lab</a>
diff --git a/vector/v.label/v.label.html b/vector/v.label/v.label.html
index 0331e6ff8a9..f697a882a9a 100644
--- a/vector/v.label/v.label.html
+++ b/vector/v.label/v.label.html
@@ -12,7 +12,7 @@ <h2>NOTES</h2>
 as the <em>size</em> option.
 <p>
 A description of the labels file follows.<p>
-The file is located in <tt>$MAPSET/paint/labels/</tt>.
+The file is located in <code>$MAPSET/paint/labels/</code>.
 The file is a plain-text ASCII file containing the following fields:
 
 <h4>Caution: The following information may be incomplete, out of date, and wrong!</h4>
@@ -24,8 +24,8 @@ <h4>Caution: The following information may be incomplete, out of date, and wrong
 <dd><!--Up to four lines of text.-->
 Lines in multiple line labels will appear one above the next.
 More than one line of text can be specified by notating the end of a
-line with a '<b><tt>\n</tt></b>'.<br>
-(e.g. <tt>SPEARFISH<b>\n</b>SOUTH DAKOTA)</tt>.
+line with a '<b><code>\n</code></b>'.<br>
+(e.g. <code>SPEARFISH<b>\n</b>SOUTH DAKOTA)</code>.
 
 <!-- I don't think it exists. -HB 6/2005
 <dt><b>SKIP</b>:
@@ -105,11 +105,11 @@ <h4>Caution: The following information may be incomplete, out of date, and wrong
 
 <ol>
 <li>By color name:<br>
-<tt>aqua black blue brown cyan gray green grey indigo
-magenta orange purple red violet white yellow</tt></li>
+<code>aqua black blue brown cyan gray green grey indigo
+magenta orange purple red violet white yellow</code></li>
 
 <li>As red, green, blue component values. (0-255)<br>
-for example: <tt>128:100:200</tt></li>
+for example: <code>128:100:200</code></li>
 
 <!-- eh?
 <li>As red, green, blue percentages.
@@ -124,7 +124,7 @@ <h4>Caution: The following information may be incomplete, out of date, and wrong
 <em><a href="d.labels.html">d.labels</a></em>.)
 -->
 
-<li>Specify "<tt>none</tt>" to suppress the lettering.</li>
+<li>Specify "<code>none</code>" to suppress the lettering.</li>
 </ol>
 
 
@@ -139,9 +139,9 @@ <h4>Caution: The following information may be incomplete, out of date, and wrong
 appears to be in two colors. The text is drawn first in
 this color at a wider line width, and then redrawn in the
 text color at the regular line width.  No highlight color
-("<tt>none</tt>") is used by default, if unspecified by the
+("<code>none</code>") is used by default, if unspecified by the
 user.  To specify use of no highlight color, specify
-"<tt>none</tt>".
+"<code>none</code>".
 (See <a href="#textcolor">TEXT COLOR</a>
 above for a list of permissible color names.)
 
@@ -157,7 +157,7 @@ <h4>Caution: The following information may be incomplete, out of date, and wrong
 <dt><b>BACKGROUND COLOR</b>:
 
 <dd>Text may be boxed in a solid color by specifying a background color.
-Specify "<tt>none</tt>" for no background.  The default background color
+Specify "<code>none</code>" for no background.  The default background color
 setting, if unspecified by the user, is <em>white</em>.
 (See <a href="#textcolor">TEXT COLOR</a>
 above for a list of permissible color names.)
@@ -166,7 +166,7 @@ <h4>Caution: The following information may be incomplete, out of date, and wrong
 <dt><b>BORDER COLOR</b>:
 
 <dd>Select a color for the border around the background.
-Specify "<tt>none</tt>" to suppress the border.
+Specify "<code>none</code>" to suppress the border.
 The default border color used, if unspecified, is <em>black</em>.
 (See <a href="#textcolor">TEXT COLOR</a>
 above for a list of permissible color names.)
@@ -197,7 +197,7 @@ <h2>EXAMPLE</h2>
 Since the label files are simple text files, you can merge them together
 if you like. For example if you set the label colors based on database
 attributes using multiple runs with the <b>where</b> option.
-This example uses the standard UNIX <tt>cat</tt> program.
+This example uses the standard UNIX <code>cat</code> program.
 
 <div class="code"><pre>
 cd $MAPSET/paint/labels/
diff --git a/vector/v.lidar.correction/v.lidar.correction.html b/vector/v.lidar.correction/v.lidar.correction.html
index 5e45edc02f6..29d1bab645d 100644
--- a/vector/v.lidar.correction/v.lidar.correction.html
+++ b/vector/v.lidar.correction/v.lidar.correction.html
@@ -90,7 +90,7 @@ <h2>REFERENCES</h2>
 <br>
 <br>
 Performances of the filter can be seen in the
-<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+<a href="https://www.itc.nl/isprs/wgIII-3/filtertest/">ISPRS WG III/3 Comparison of Filters</a>
 report by Sithole, G. and Vosselman, G., 2003.
 
 <h2>SEE ALSO</h2>
diff --git a/vector/v.lidar.edgedetection/v.lidar.edgedetection.html b/vector/v.lidar.edgedetection/v.lidar.edgedetection.html
index 08fd672d266..77f0efe6e0b 100644
--- a/vector/v.lidar.edgedetection/v.lidar.edgedetection.html
+++ b/vector/v.lidar.edgedetection/v.lidar.edgedetection.html
@@ -142,7 +142,7 @@ <h2>REFERENCES</h2>
 <li>Brovelli M. A., Cannata M. and Longoni U.M., 2002. DTM LIDAR in area urbana,
 Bollettino SIFET N.2, pp. 7-26.</li>
 <li>Performances of the filter can be seen in the
-<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+<a href="https://www.itc.nl/isprs/wgIII-3/filtertest/">ISPRS WG III/3 Comparison of Filters</a>
 report by Sithole, G. and Vosselman, G., 2003.</li>
 </ul>
 
diff --git a/vector/v.lidar.growing/v.lidar.growing.html b/vector/v.lidar.growing/v.lidar.growing.html
index d98309eb59c..58c76c59fb2 100644
--- a/vector/v.lidar.growing/v.lidar.growing.html
+++ b/vector/v.lidar.growing/v.lidar.growing.html
@@ -68,7 +68,7 @@ <h2>REFERENCES</h2>
 Bollettino SIFET N.2, pp. 7-26.
 <p>
 Performances of the filter can be seen in the
-<a href="http://www.itc.nl/isprswgIII-3/filtertest/MainDoc.htm">ISPRS WG III/3 Comparison of Filters</a>
+<a href="https://www.itc.nl/isprs/wgIII-3/filtertest/">ISPRS WG III/3 Comparison of Filters</a>
 report by Sithole, G. and Vosselman, G., 2003.
 
 <h2>SEE ALSO</h2>
diff --git a/vector/v.lrs/lrs.html b/vector/v.lrs/lrs.html
index edc517788cd..63d99b6c1fd 100644
--- a/vector/v.lrs/lrs.html
+++ b/vector/v.lrs/lrs.html
@@ -167,14 +167,16 @@ <h2>NOTES</h2>
 
 <h2>SEE ALSO</h2>
 
-<em>R. Blazek, 2004, <a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>, Bangkok, GRASS User Conf. Proc.</em><br>
-<em>R. Blazek, 2005, <a href="http://creativecity.gscc.osaka-cu.ac.jp/IJG/article/download/320/321">Introducing the Linear Reference System in GRASS</a>, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100</em><br>
+<em>R. Blazek, 2004, <a href="https://foss4g.asia/2004/Full%20Paper_PDF/Introducing%20the%20Linear%20Reference%20System%20in%20GRASS.pdf">Introducing the Linear Reference System in GRASS</a>, Bangkok, GRASS User Conf. Proc.</em><br>
+<em>R. Blazek, 2005, <a href="https://web.archive.org/web/20240814152234/http://creativecity.gscc.osaka-cu.ac.jp/IJG/article/download/320/321">Introducing the Linear Reference System in GRASS</a>, International Journal of Geoinformatics, Vol. 1(3), pp. 95-100</em><br>
 <p>
-<em><a href="v.build.polylines.html">v.build.polylines</a></em>,
-<em><a href="v.lrs.create.html">v.lrs.create</a></em>,
-<em><a href="v.lrs.segment.html">v.lrs.segment</a></em>,
-<em><a href="v.lrs.where.html">v.lrs.where</a></em>,
-<em><a href="v.lrs.label.html">v.lrs.label</a></em>
+<em>
+<a href="v.build.polylines.html">v.build.polylines</a>,
+<a href="v.lrs.create.html">v.lrs.create</a>,
+<a href="v.lrs.segment.html">v.lrs.segment</a>,
+<a href="v.lrs.where.html">v.lrs.where</a>,
+<a href="v.lrs.label.html">v.lrs.label</a>
+</em>
 
 <h2>AUTHORS</h2>
 
diff --git a/vector/v.lrs/v.lrs.create/v.lrs.create.html b/vector/v.lrs/v.lrs.create/v.lrs.create.html
index 518bb80fedf..eb969065186 100644
--- a/vector/v.lrs/v.lrs.create/v.lrs.create.html
+++ b/vector/v.lrs/v.lrs.create/v.lrs.create.html
@@ -150,7 +150,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://foss4g.asia/2004/Full%20Paper_PDF/Introducing%20the%20Linear%20Reference%20System%20in%20GRASS.pdf">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHORS</h2>
diff --git a/vector/v.lrs/v.lrs.label/v.lrs.label.html b/vector/v.lrs/v.lrs.label/v.lrs.label.html
index dbd2f64ac67..fb96858b486 100644
--- a/vector/v.lrs/v.lrs.label/v.lrs.label.html
+++ b/vector/v.lrs/v.lrs.label/v.lrs.label.html
@@ -33,7 +33,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://foss4g.asia/2004/Full%20Paper_PDF/Introducing%20the%20Linear%20Reference%20System%20in%20GRASS.pdf">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHORS</h2>
diff --git a/vector/v.lrs/v.lrs.segment/v.lrs.segment.html b/vector/v.lrs/v.lrs.segment/v.lrs.segment.html
index 0a2b39dfd1f..259b54ae048 100644
--- a/vector/v.lrs/v.lrs.segment/v.lrs.segment.html
+++ b/vector/v.lrs/v.lrs.segment/v.lrs.segment.html
@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.lrs.segment</em> creates points/segments from input lines,
-linear reference system and positions read from <tt>standard in</tt>
+linear reference system and positions read from <code>standard in</code>
 or a file.
 <p>
 The format is as follows:<br>
@@ -56,7 +56,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://foss4g.asia/2004/Full%20Paper_PDF/Introducing%20the%20Linear%20Reference%20System%20in%20GRASS.pdf">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHOR</h2>
diff --git a/vector/v.lrs/v.lrs.where/v.lrs.where.html b/vector/v.lrs/v.lrs.where/v.lrs.where.html
index cdf9651f389..e8c81834f8e 100644
--- a/vector/v.lrs/v.lrs.where/v.lrs.where.html
+++ b/vector/v.lrs/v.lrs.where/v.lrs.where.html
@@ -45,7 +45,7 @@ <h2>SEE ALSO</h2>
 <p>
 <em>
 <a href="lrs.html">LRS tutorial</a>,<br>
-<a href="http://gisws.media.osaka-cu.ac.jp/grass04/viewpaper.php?id=50">Introducing the Linear Reference System in GRASS</a>
+<a href="https://foss4g.asia/2004/Full%20Paper_PDF/Introducing%20the%20Linear%20Reference%20System%20in%20GRASS.pdf">Introducing the Linear Reference System in GRASS</a>
 </em>
 
 <h2>AUTHORS</h2>
diff --git a/vector/v.mkgrid/v.mkgrid.html b/vector/v.mkgrid/v.mkgrid.html
index a1e7d87a6df..3b9433f761d 100644
--- a/vector/v.mkgrid/v.mkgrid.html
+++ b/vector/v.mkgrid/v.mkgrid.html
@@ -157,8 +157,8 @@ <h3>Using hexagons for point density</h3>
 since the hexagons cannot cover all the area around the edges
 (the computational region extent needs to be enlarged if all points
 should be considered).
-The last command sets the vector map color table to <tt>viridis</tt>
-based on the <tt>count</tt> column.
+The last command sets the vector map color table to <code>viridis</code>
+based on the <code>count</code> column.
 
 <div class="code"><pre>
 v.colors map=hexagons use=attr column=count color=viridis
diff --git a/vector/v.net.path/v.net.path.html b/vector/v.net.path/v.net.path.html
index 60b26f3a591..216f35b103f 100644
--- a/vector/v.net.path/v.net.path.html
+++ b/vector/v.net.path/v.net.path.html
@@ -16,10 +16,10 @@ <h2>DESCRIPTION</h2>
 and also different costs for both directions of a vector line.
 For areas, costs will be calculated along boundary lines.
 <p>
-The input vector needs to be prepared with <tt>v.net operation=connect</tt>
+The input vector needs to be prepared with <code>v.net operation=connect</code>
 in order to connect points representing center nodes to the network.
 
-<p>Nodes and arcs can be closed using <tt>cost = -1</tt>.
+<p>Nodes and arcs can be closed using <code>cost = -1</code>.
 <p>Least cost paths are written to the output vector map with an
 attached attribute table.
 <p>Nodes can be
@@ -43,7 +43,7 @@ <h2>DESCRIPTION</h2>
 
 <p>
 Points specified by category must be exactly on network nodes, and the
-input vector map needs to be prepared with <tt>v.net operation=connect</tt>.
+input vector map needs to be prepared with <code>v.net operation=connect</code>.
 <p>
 When specifying coordinates, the next network node to a given coordinate
 pair is used.
@@ -52,19 +52,19 @@ <h2>DESCRIPTION</h2>
 The attribute table will contain the following attributes:
 
 <ul>
-    <li><tt>cat</tt>  - path unique category assigned by module</li>
-    <li><tt>id</tt>   - path id (read from input)</li>
-    <li><tt>fcat</tt> - from point category</li>
-    <li><tt>tcat</tt> - to point category</li>
-    <li><tt>sp</tt> - result status:
+    <li><code>cat</code>  - path unique category assigned by module</li>
+    <li><code>id</code>   - path id (read from input)</li>
+    <li><code>fcat</code> - from point category</li>
+    <li><code>tcat</code> - to point category</li>
+    <li><code>sp</code> - result status:
     <ul>
         <li>     0 - OK, path found</li>
         <li>     1 - node is not reachable</li>
         <li>     2 - point of given category does not exist</li>
     </ul></li>
-    <li><tt>cost</tt> - travelling costs (on the network, not to/from network)</li>
-    <li><tt>fdist</tt> - the distance from first point to the network</li>
-    <li><tt>tdist</tt> - the distance from the network to second point</li>
+    <li><code>cost</code> - travelling costs (on the network, not to/from network)</li>
+    <li><code>fdist</code> - the distance from first point to the network</li>
+    <li><code>tdist</code> - the distance from the network to second point</li>
 </ul>
 
 <p>
@@ -84,7 +84,7 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-Nodes and arcs can be closed using <tt>cost = -1</tt>.
+Nodes and arcs can be closed using <code>cost = -1</code>.
 <p>If the cost columns <b>arc_column</b>, <b>arc_backward_column</b> and <b>node_column</b> are not
 specified, the length of network segments is measured and
 zero costs are assumed for nodes.
@@ -92,7 +92,7 @@ <h2>NOTES</h2>
 accurate results, the line length must be taken into account when
 assigning costs as attributes. For example, to get the <em>fastest path</em>,
 the columns 'max_speed' and 'length' are required. The correct fastest
-path can then be found by specifying <tt>arc_column=length/max_speed</tt>. If not yet
+path can then be found by specifying <code>arc_column=length/max_speed</code>. If not yet
 existing, the column containing the line length ("length") has to added to the
 attributes table using <em><a href="v.to.db.html">v.to.db</a></em>.
 
diff --git a/vector/v.net/v.net.html b/vector/v.net/v.net.html
index baef25e5484..c9a8cb57eb5 100644
--- a/vector/v.net/v.net.html
+++ b/vector/v.net/v.net.html
@@ -39,9 +39,9 @@ <h2>DESCRIPTION</h2>
 category. In order to assign unique costs to each line, a new layer
 needs to be created with<br>
 <!-- like this it is rather useless, still to be improved (eg as a full example below!) -->
-<tt>v.category input=yourmap option=add cat=1 step=1 layer=3 output=newmap</tt><br>
+<code>v.category input=yourmap option=add cat=1 step=1 layer=3 output=newmap</code><br>
 followed by<br>
-<tt>v.db.addtable map=newmap layer=3 table=tablename</tt>.</li>
+<code>v.db.addtable map=newmap layer=3 table=tablename</code>.</li>
 
 <li>Create nodes and arcs from a vector line/boundary file using the
 <em>node</em> operation. This is useful if you are mostly interested
@@ -173,7 +173,7 @@ <h3>Merge in nodes from a separate map within given threshold</h3>
 v.category streets_net option=report
 </pre></div>
 
-The nodes are stored in layer 2 unless <tt>node_layer=1</tt> is used.
+The nodes are stored in layer 2 unless <code>node_layer=1</code> is used.
 
 <h3>Generating network for vector point map</h3>
 
diff --git a/vector/v.out.ascii/v.out.ascii.html b/vector/v.out.ascii/v.out.ascii.html
index 964df04b084..e87bcba9075 100644
--- a/vector/v.out.ascii/v.out.ascii.html
+++ b/vector/v.out.ascii/v.out.ascii.html
@@ -19,17 +19,17 @@ <h2>NOTES</h2>
 
 <p>If old version is requested, the <b>output</b> files
 from <em>v.out.ascii</em> is placed in
-the <tt>$LOCATION/$MAPSET/dig_ascii/</tt>
-and <tt>$LOCATION/$MAPSET/dig_att</tt> directory.
+the <code>$LOCATION/$MAPSET/dig_ascii/</code>
+and <code>$LOCATION/$MAPSET/dig_att</code> directory.
 
 <p>If <b>layer > 0</b> then only features with a category number
 will be exported. Use <em><a href="v.category.html">v.category</a></em> to add
 them if needed or define <b>layer=-1</b> to export also features without category.
 
 <p><em>v.out.ascii</em> in the old version mode (<b>-o</b>) does not
-copy the <tt>dig_cats</tt> file associated with the binary
+copy the <code>dig_cats</code> file associated with the binary
 vector <b>input</b> map to the new <b>output</b> file name. The user
-must copy the <tt>dig_cats</tt> file to the new <b>output</b> name if
+must copy the <code>dig_cats</code> file to the new <b>output</b> name if
 this is desired (e.g. using the UNIX <em>cp</em> command).
 
 <p>It is possible to output the coordinates of vertices in a non-points vector
diff --git a/vector/v.out.dxf/v.out.dxf.html b/vector/v.out.dxf/v.out.dxf.html
index 95057f05f22..1cf45b3d3e0 100644
--- a/vector/v.out.dxf/v.out.dxf.html
+++ b/vector/v.out.dxf/v.out.dxf.html
@@ -8,7 +8,7 @@ <h2>DESCRIPTION</h2>
 
 <h2>NOTES</h2>
 
-DXF files output by AutoCAD have the suffix <tt>.dxf</tt>
+DXF files output by AutoCAD have the suffix <code>.dxf</code>
 
 <h2>REFERENCES</h2>
 
diff --git a/vector/v.out.lidar/v.out.lidar.html b/vector/v.out.lidar/v.out.lidar.html
index 2d0708d98ae..295812480e0 100644
--- a/vector/v.out.lidar/v.out.lidar.html
+++ b/vector/v.out.lidar/v.out.lidar.html
@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.out.lidar</em> converts GRASS vector map to a LiDAR point clouds
-in LAS format using the <a href="http://www.liblas.org">libLAS</a> library.
+in LAS format using the <a href="https://liblas.org">libLAS</a> library.
 
 <p>
 The <b>-r</b> flag limits the export to the current computational region
@@ -20,7 +20,7 @@ <h2>NOTES</h2>
 
 The typical file extensions for the LAS format are .las and .laz (compressed).
 The compressed LAS (.laz) format can be exported only if libLAS has been
-compiled with <a href="http://www.laszip.org/">LASzip</a> support.
+compiled with <a href="https://laszip.org/">LASzip</a> support.
 It is also good when libLAS was compiled with GDAL. This is needed when
 working with projections.
 
@@ -39,7 +39,7 @@ <h2>REFERENCES</h2>
 
 <a href="https://www.asprs.org/committee-general/laser-las-file-format-exchange-activities.html">
 ASPRS LAS format</a><br>
-<a href="http://www.liblas.org/">LAS library</a> <br>
+<a href="https://liblas.org/">LAS library</a> <br>
 
 <h2>SEE ALSO</h2>
 
diff --git a/vector/v.out.ogr/v.out.ogr.html b/vector/v.out.ogr/v.out.ogr.html
index 664a5c35a1a..e97d194281d 100644
--- a/vector/v.out.ogr/v.out.ogr.html
+++ b/vector/v.out.ogr/v.out.ogr.html
@@ -13,15 +13,15 @@ <h2>DESCRIPTION</h2>
 The OGR library supports many various formats including:
 
 <ul>
-  <li><a href="https://gdal.org/drv_geopackage.html">OGC GeoPackage</a></li>
-  <li><a href="https://gdal.org/drv_shapefile.html">ESRI Shapefile</a></li>
-  <li><a href="https://gdal.org/drv_pg.html">PostGIS</a></li>
-  <li><a href="https://gdal.org/drv_sqlite.html">SpatiaLite</a></li>
-  <li><a href="https://gdal.org/drv_csv.html">CSV</a></li>
-  <li><a href="https://gdal.org/drv_gml.html">GML</a></li>
-  <li><a href="https://gdal.org/drv_kml.html">KML</a></li>
-  <li><a href="https://gdal.org/drv_mitab.html">Mapinfo File</a></li>
-  <li><a href="https://gdal.org/drv_tiger.html">TIGER</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/gpkg.html">OGC GeoPackage</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/shapefile.html">ESRI Shapefile</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/pg.html">PostGIS</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/sqlite.html">SpatiaLite</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/csv.html">CSV</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/gml.html">GML</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/kml.html">KML</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/mitab.html">Mapinfo File</a></li>
+  <li><a href="https://gdal.org/en/stable/drivers/vector/tiger.html">TIGER</a></li>
   <li>... and many others</li>
 </ul>
 
@@ -29,7 +29,7 @@ <h2>DESCRIPTION</h2>
 
 <p>
 For further available other supported formats go
-<a href="https://gdal.org/drivers/vector/">here</a>.
+<a href="https://gdal.org/en/stable/drivers/vector/">here</a>.
 
 <h2>NOTES</h2>
 
@@ -63,7 +63,7 @@ <h2>NOTES</h2>
 
 <p>
 Performance: export to SQLite based formats including OGC GeoPackage may
-become faster with the environmental variable <tt>OGR_SQLITE_CACHE=1024</tt>
+become faster with the environmental variable <code>OGR_SQLITE_CACHE=1024</code>
 being set (value depends on available RAM, see
 <a href="https://trac.osgeo.org/gdal/wiki/ConfigOptions#OGR_SQLITE_CACHE">OGR ConfigOptions</a>).
 
diff --git a/vector/v.out.postgis/v.out.postgis.html b/vector/v.out.postgis/v.out.postgis.html
index 2307ce6a394..0c0906097db 100644
--- a/vector/v.out.postgis/v.out.postgis.html
+++ b/vector/v.out.postgis/v.out.postgis.html
@@ -6,48 +6,48 @@ <h2>DESCRIPTION</h2>
 <p>
 By default GRASS GIS topological features are converted into simple
 features
-(see <a href="http://www.opengeospatial.org/standards/sfa">OGC Simple
+(see <a href="https://www.ogc.org/publications/standard/sfa/">OGC Simple
 Feature Access</a> specification for details). Flag <b>-l</b> allows
 to export vector features as topological elements stored
-in <a href="http://postgis.refractions.net/docs/Topology.html">PostGIS
+in <a href="https://postgis.net/docs/Topology.html">PostGIS
 Topology</a> schema. Note that topological export requires PostGIS
 version 2 or later.
 
 <p>
 Additional creation options can be defined by <b>options</b> parameter:
 <ul>
-  <li><tt>FID=<column></tt> - name of column which will be used as
-  primary key (feature id), default: <tt>fid</tt></li>
-  <li><tt>GEOMETRY_NAME=<column></tt> name of column which will
-  be used for storing geometry data in feature table, default: <tt>geom</tt></li>
-  <li><tt>SPATIAL_INDEX=YES|NO</tt> - enable/disable creating spatial
-  index on geometry column, default: <tt>YES</tt></li>
-  <li><tt>PRIMARY_KEY=YES|NO</tt> - enable/disable adding primary key
-  on FID column, default: <tt>YES</tt></li>
-  <li><tt>SRID=<value></tt> - spatial reference identifier,
+  <li><code>FID=<column></code> - name of column which will be used as
+  primary key (feature id), default: <code>fid</code></li>
+  <li><code>GEOMETRY_NAME=<column></code> name of column which will
+  be used for storing geometry data in feature table, default: <code>geom</code></li>
+  <li><code>SPATIAL_INDEX=YES|NO</code> - enable/disable creating spatial
+  index on geometry column, default: <code>YES</code></li>
+  <li><code>PRIMARY_KEY=YES|NO</code> - enable/disable adding primary key
+  on FID column, default: <code>YES</code></li>
+  <li><code>SRID=<value></code> - spatial reference identifier,
   default: not defined</li>
 </ul>
 
 PostGIS Topology related options (relevant only for <b>-l</b> flag):
 
 <ul>
-  <li><tt>TOPOSCHEMA_NAME=<schema name></tt> - name of PostGIS
-  Topology schema, default: <tt>topo_<input></tt></li>
-  <li><tt>TOPOGEOM_NAME=<column></tt> - name of column which
+  <li><code>TOPOSCHEMA_NAME=<schema name></code> - name of PostGIS
+  Topology schema, default: <code>topo_<input></code></li>
+  <li><code>TOPOGEOM_NAME=<column></code> - name of column which
   will be used for storing topogeometry data in feature table,
-  default: <tt>topo</tt></li>
-  <li><tt>TOPO_TOLERANCE=<value></tt> - tolerance for PostGIS
+  default: <code>topo</code></li>
+  <li><code>TOPO_TOLERANCE=<value></code> - tolerance for PostGIS
   Topology schema,
-  see <a href="http://www.postgis.net/docs/manual-2.0/CreateTopology.html">CreateTopology</a>
-  function for details, default: <tt>0</tt></li>
-  <li><tt>TOPO_GEO_ONLY=YES|NO</tt> - store in PostGIS Topology schema
+  see <a href="https://postgis.net/docs/CreateTopology.html">CreateTopology</a>
+  function for details, default: <code>0</code></li>
+  <li><code>TOPO_GEO_ONLY=YES|NO</code> - store in PostGIS Topology schema
   only data relevant to Topo-Geo data model,
-  default: <tt>NO</tt></li>
+  default: <code>NO</code></li>
 </ul>
 
 <p>
 Creation <b>options</b> are comma-separated pairs
-(<tt>key=value</tt>), the options are case-insensitive. Note
+(<code>key=value</code>), the options are case-insensitive. Note
 that <b>options</b> defined
 by <em><a href="v.external.out.html">v.external.out</a></em> are
 ignored by <em>v.out.postgis</em>.
@@ -63,9 +63,9 @@ <h2>NOTES</h2>
 areas) become polygons, isles become holes. Geometry of simple feature
 elements is stored in PostGIS feature table in the column named
 "geom". Name of the geometry column can be changed
-by <b>options=</b><tt>GEOMETRY_NAME=<column></tt>. Note that for
+by <b>options=</b><code>GEOMETRY_NAME=<column></code>. Note that for
 exporting vector features as simple features can be alternatively
-used <a href="https://gdal.org/drv_pg.html">PostgreSQL driver</a>
+used <a href="https://gdal.org/en/stable/drivers/vector/pg.html">PostgreSQL driver</a>
 from <a href="https://gdal.org/">OGR</a> library
 through <em><a href="v.out.ogr.html">v.out.ogr</a></em> module.
 
@@ -83,7 +83,7 @@ <h2>NOTES</h2>
 <em>v.out.postgis</em> currently supports only three basic output
 simple feature types: Points, Linestrings and Polygons. Also 3D
 features of the same type are supported, eg. 3D points are exported
-as <tt>PointZ</tt> simple feature. Faces are exported as 3D
+as <code>PointZ</code> simple feature. Faces are exported as 3D
 polygons. 3D features are written to the output automatically if input
 vector map is 3D. If <b>-2</b> flag is given then the output is always
 2D (z-coordinate is silently ignored for 3D input vector maps).
@@ -95,7 +95,7 @@ <h2>NOTES</h2>
 <p>
 <em>v.out.postgis</em> also allows exporting vector features as
 <em>topological elements</em>
-in <a href="http://postgis.refractions.net/docs/Topology.html">PostGIS
+in <a href="https://postgis.net/docs/Topology.html">PostGIS
 Topology</a> schema. PostGIS Topology extension uses three tables to
 store basic topological elements which forms topological objects like
 areas or isles in GRASS terminology. <em>Nodes</em> (0-dimensional
@@ -116,9 +116,9 @@ <h2>NOTES</h2>
 
 Tables <i>node</i>, <i>edge</i> and <i>face</i> are stored in given
 topological schema. By default <em>v.out.postgis</em> defines its name
-as <tt>topo_<input></tt>. Alternatively, the name for topology
+as <code>topo_<input></code>. Alternatively, the name for topology
 schema can be defined
-by <b>options=</b><tt>TOPOSCHEMA_NAME=<name></tt>.
+by <b>options=</b><code>TOPOSCHEMA_NAME=<name></code>.
 
 <h2>EXAMPLES</h2>
 
@@ -162,7 +162,7 @@ <h3>Export data into specific database schema</h3>
 
 Database schema for storing exported data can be defined
 by <b>output_layer</b> as
-<tt><schema_name>.<table_name></tt>. If the specified
+<code><schema_name>.<table_name></code>. If the specified
 schema doesn't exist in the database, then it's automatically created.
 
 <p>
@@ -177,7 +177,7 @@ <h3>Export data with creation options</h3>
 
 Example below demonstrates how to define name for geometry column and
 disable building spatial index. Spatial reference system is defined
-by <tt>srid</tt> identifier which corresponds in this case with EPSG
+by <code>srid</code> identifier which corresponds in this case with EPSG
 3358 (North Carolina dataset).
 
 <div class="code"><pre>
@@ -233,7 +233,7 @@ <h3>Export topological data</h3>
 By default <em>v.out.postgis</em> exports data as simple
 features. Flag <b>-l</b> allows exporting data as topological elements
 instead of simple features. Export topological elements is stored in
-<a href="http://postgis.refractions.net/docs/Topology.html">PostGIS
+<a href="https://postgis.net/docs/Topology.html">PostGIS
 Topology</a> schema.
 
 <div class="code"><pre>
@@ -264,8 +264,8 @@ <h2>REQUIREMENTS</h2>
 <h2>REFERENCES</h2>
 
 <ul>
-  <li><a href="http://www.opengeospatial.org/standards/sfa">OGC Simple Feature Access</a> specification</li>
-  <li><a href="http://postgis.net/docs/Topology.html">PostGIS Topology</a> documentation</li>
+  <li><a href="https://www.ogc.org/publications/standard/sfa/">OGC Simple Feature Access</a> specification</li>
+  <li><a href="https://postgis.net/docs/Topology.html">PostGIS Topology</a> documentation</li>
   <li><a href="https://grass.osgeo.org/programming8/vlibPg.html">GRASS-PostGIS data provider</a></li>
 </ul>
 
diff --git a/vector/v.out.vtk/v.out.vtk.html b/vector/v.out.vtk/v.out.vtk.html
index 97d8c82c0e7..ff4f2945e5a 100644
--- a/vector/v.out.vtk/v.out.vtk.html
+++ b/vector/v.out.vtk/v.out.vtk.html
@@ -49,9 +49,9 @@ <h2>NOTES</h2>
  <li><i>vtk polygons</i> -- representing areas and faces </li>
 </ul>
 <p>The VTK file can be visualized with
-<em><a href="http://www.vtk.org">VTK Toolkit</a></em>,
-<em><a href="http://www.paraview.org">Paraview</a></em> and
-<em><a href="http://mayavi.sourceforge.net">MayaVi</a></em>.
+<em><a href="https://vtk.org/">VTK Toolkit</a></em>,
+<em><a href="https://www.paraview.org/">Paraview</a></em> and
+<em><a href="https://github.com/enthought/mayavi">MayaVi</a></em>.
 
 <h3>Attention</h3>
 <p>If areas or faces are exported, the data have to be triangulated within Paraview or
diff --git a/vector/v.proj/v.proj.html b/vector/v.proj/v.proj.html
index 9910b7258b4..8552b0327f6 100644
--- a/vector/v.proj/v.proj.html
+++ b/vector/v.proj/v.proj.html
@@ -79,9 +79,9 @@ <h2>REFERENCES</h2>
   <li> <a href="https://www.asprs.org/asprs-publications/grids-and-datums">ASPRS Grids and Datum</a></li>
   <li> <a href="http://geotiff.maptools.org/proj_list/">Projections Transform List</a> (PROJ)</li>
   <li> <a href="https://proj.org/operations/index.html">Coordinate operations</a> by PROJ (projections, conversions, transformations, pipeline operator)</li>
-  <li> <a href="http://www.mapref.org">MapRef -
+  <li> <a href="https://mapref.org">MapRef -
       The Collection of Map Projections and Reference Systems for Europe</a></li>
-  <li> <a href="http://www.crs-geo.eu">Information and Service System for European Coordinate Reference Systems - CRS</a></li>
+  <li> <a href="https://www.crs-geo.eu">Information and Service System for European Coordinate Reference Systems - CRS</a></li>
 </ul>
 
 <h2>SEE ALSO</h2>
diff --git a/vector/v.random/v.random.html b/vector/v.random/v.random.html
index 5a9ce903d40..abfc25d8c67 100644
--- a/vector/v.random/v.random.html
+++ b/vector/v.random/v.random.html
@@ -36,7 +36,7 @@ <h3>Restriction to vector areas</h3>
 <h2>NOTES</h2>
 
 Importantly, attributes will only be transferred if <b>layer</b> > 0
-(e.g., <tt>layer=1</tt>).
+(e.g., <code>layer=1</code>).
 
 <h2>EXAMPLES</h2>
 
diff --git a/vector/v.reclass/v.reclass.html b/vector/v.reclass/v.reclass.html
index 4fc3e1b81cd..6a75033376c 100644
--- a/vector/v.reclass/v.reclass.html
+++ b/vector/v.reclass/v.reclass.html
@@ -51,12 +51,12 @@ <h3>Example 1: Reclass by rules</h3>
 <em>land</em> with area category values selected from database by SQL
 select statement:
 <br>
-<tt>select id from tland where use = 'E13' and owner = 'Jara Cimrman'</tt>
+<code>select id from tland where use = 'E13' and owner = 'Jara Cimrman'</code>
 changed to category 1;
 <br>
 values selected from database by SQL select statement:
 <br>
-<tt>select id from tland where use = 'E14'</tt> changed to category 2.
+<code>select id from tland where use = 'E14'</code> changed to category 2.
 
 <h3>Example 2: Reclass by attribute column</h3>
 
diff --git a/vector/v.segment/v.segment.html b/vector/v.segment/v.segment.html
index 43f83abdd44..eda0b89c916 100644
--- a/vector/v.segment/v.segment.html
+++ b/vector/v.segment/v.segment.html
@@ -1,7 +1,7 @@
 <h2>DESCRIPTION</h2>
 
 <em>v.segment</em> generates segments or points from input lines and from
-positions read from a text file or '<tt>stdin</tt>'. It includes the creation
+positions read from a text file or '<code>stdin</code>'. It includes the creation
 of parallel lines or points in given destination from the line.
 
 <p>The format is:
@@ -15,7 +15,7 @@ <h2>DESCRIPTION</h2>
 line.
 
 <p>
-The user could send to <tt>stdin</tt> something like:
+The user could send to <code>stdin</code> something like:
 <div class="code"><pre>
 P 1 356 24.56
 P 2 495 12.31
diff --git a/vector/v.select/v.select.html b/vector/v.select/v.select.html
index cf799cfe21e..f4004a897b0 100644
--- a/vector/v.select/v.select.html
+++ b/vector/v.select/v.select.html
@@ -240,7 +240,7 @@ <h3>RELATE feature A is spatially related to feature B (using GEOS)</h3>
 d.vect map=v_select_TOUCHES
 </pre></div>
 
-The result of <tt>relate='T********'</tt> is the same as seen
+The result of <code>relate='T********'</code> is the same as seen
 above in the example 'TOUCHES'.
 
 See the <a href="https://en.wikipedia.org/wiki/DE-9IM">DE-9IM</a> page
diff --git a/vector/v.support/v.support.html b/vector/v.support/v.support.html
index 1c81680e1ef..565c4fbfe63 100644
--- a/vector/v.support/v.support.html
+++ b/vector/v.support/v.support.html
@@ -1,6 +1,8 @@
 <h2>DESCRIPTION</h2>
 
-<em>v.support</em> is used to set/update vector map metadata.
+<em>v.support</em> is used to set/update vector map metadata. While GRASS
+GIS typically generates these metadata entries automatically, <em>v.support</em>
+allows users to manually edit them when necessary.
 
 <h2>EXAMPLE</h2>
 
diff --git a/vector/v.to.db/v.to.db.html b/vector/v.to.db/v.to.db.html
index f0ba460d450..6b32084261d 100644
--- a/vector/v.to.db/v.to.db.html
+++ b/vector/v.to.db/v.to.db.html
@@ -95,9 +95,9 @@ <h3>Updating attribute tables</h3>
 
 <p>Compute D<sub>L</sub>, the Fractal Dimension (Mandelbrot, 1982), of the
 boundary defining a polygon based on the formula:
-<br><tt>
+<br><code>
 D = 2 * (log perimeter) / (log area):<br>
-</tt>
+</code>
 <div class="code"><pre>
 g.copy vect=soils,mysoils
 v.db.addcolumn mysoils col="d double precision"
diff --git a/vector/v.to.rast/v.to.rast.html b/vector/v.to.rast/v.to.rast.html
index 4ebe8bf4922..7cbfc68f48a 100644
--- a/vector/v.to.rast/v.to.rast.html
+++ b/vector/v.to.rast/v.to.rast.html
@@ -49,7 +49,7 @@ <h2>NOTES</h2>
 Labeled areas and/or centroids will produce filled raster coverages with edges
 that straddle the original area boundary <b>as long as the boundary is NOT
 labeled</b>.
-<br>(Use <tt>v.category option=del type=boundary</tt> to remove.)</li>
+<br>(Use <code>v.category option=del type=boundary</code> to remove.)</li>
 <li>
 Labeled lines and boundaries will produce lines of raster cells which touch the
 original vector line. This tends to be more aggressive than area-only conversions.</li>
diff --git a/vector/v.to.rast3/v.to.rast3.html b/vector/v.to.rast3/v.to.rast3.html
index 14bfb0eada0..42a50851491 100644
--- a/vector/v.to.rast3/v.to.rast3.html
+++ b/vector/v.to.rast3/v.to.rast3.html
@@ -14,7 +14,7 @@ <h2>NOTES</h2>
 <img src="v_to_rast3_test.png" border="0"><br>
 <table border="0" width="600">
 <tr><td><center>
-<i>This screenshot shows the result of the v.to.rast3 test. Visualized
+<i>Fig: This screenshot shows the result of the v.to.rast3 test. Visualized
 are the cube of the GRASS region, the vector points as black dots and
 the voxel cells as wireframe model. Only cells with non-null values are
 shown.</i>
diff --git a/vector/v.voronoi/v.voronoi.html b/vector/v.voronoi/v.voronoi.html
index c058a0587fd..fa79d1507a8 100644
--- a/vector/v.voronoi/v.voronoi.html
+++ b/vector/v.voronoi/v.voronoi.html
@@ -91,6 +91,8 @@ <h2>SEE ALSO</h2>
 <a href="v.delaunay.html">v.delaunay</a>,
 <a href="v.hull.html">v.hull</a>
 </em>
+<p>
+<a href="https://en.wikipedia.org/wiki/Voronoi_diagram">Voronoi diagram (Wikipedia)</a>
 
 <h2>AUTHORS</h2>
 
diff --git a/vector/v.what.rast/v.what.rast.html b/vector/v.what.rast/v.what.rast.html
index fe067a18138..05c5eddbd89 100644
--- a/vector/v.what.rast/v.what.rast.html
+++ b/vector/v.what.rast/v.what.rast.html
@@ -34,10 +34,10 @@ <h2>NOTES</h2>
 geometry instead, use <em><a href="v.drape.html">v.drape</a></em>.
 <p>
 Categories and values are output unsorted with the print flag. To sort them
-pipe the output of this module into the UNIX <tt>sort</tt> tool
-(<tt>sort -n</tt>). If you need coordinates, after sorting use
-<em><a href="v.out.ascii.html">v.out.ascii</a></em> and the UNIX <tt>paste</tt> tool
-(<tt>paste -d'|'</tt>). In the case of a NULL result, a "<tt>*</tt>"
+pipe the output of this module into the UNIX <code>sort</code> tool
+(<code>sort -n</code>). If you need coordinates, after sorting use
+<em><a href="v.out.ascii.html">v.out.ascii</a></em> and the UNIX <code>paste</code> tool
+(<code>paste -d'|'</code>). In the case of a NULL result, a "<code>*</code>"
 will be printed in lieu of the value.
 <p>
 The interpolation flag is only useful for continuous value raster maps,
diff --git a/visualization/ximgview/ximgview.html b/visualization/ximgview/ximgview.html
index c5012ca7d41..1e07dd7eb38 100644
--- a/visualization/ximgview/ximgview.html
+++ b/visualization/ximgview/ximgview.html
@@ -23,7 +23,7 @@ <h2>EXAMPLE</h2>
 export GRASS_RENDER_FILE_READ=TRUE
 
 d.erase
-ximgview $GRASS_RENDER_FILE percent=50 &
+ximgview $GRASS_RENDER_FILE percent=50 &
 d.rast elevation.dem
 d.vect roads
 </pre></div>
@@ -31,10 +31,14 @@ <h2>EXAMPLE</h2>
 <h2>SEE ALSO</h2>
 
 <em>
-<a href="pngdriver.html">PNG driver</a><br>
-<a href="cairodriver.html">cairo driver</a><br>
+<a href="pngdriver.html">PNG driver</a>,
+<a href="cairodriver.html">cairo driver</a>,
 <a href="wximgview.html">wximgview</a>
 </em>
+<br>
+<em>
+<a href="variables.html">variables</a>
+</em>
 
 <h2>AUTHOR</h2>