From 688e625e7db3be9a465ce99ba25f36d2ebdd5aeb Mon Sep 17 00:00:00 2001 From: Anna Petrasova Date: Tue, 18 Feb 2025 17:20:26 -0500 Subject: [PATCH] docs: fixing no-inline-html liniting error, part 1 (#5120) * docs: fixing no-inline-html liniting error, part 1 * revert unrelated htmldriver example --- display/d.graph/d.graph.md | 33 +- display/d.rhumbline/d.rhumbline.md | 2 +- display/d.text/d.text.md | 2 +- imagery/i.atcorr/i.atcorr.md | 465 +++---------------- imagery/i.cluster/i.cluster.md | 39 +- raster/r.buffer/r.buffer.md | 2 +- raster/r.cost/r.cost.md | 18 +- raster/r.grow.distance/r.grow.distance.md | 6 +- raster/r.gwflow/r.gwflow.md | 7 +- raster/r.lake/r.lake.md | 4 +- raster/r.li/r.li.cwed/r.li.cwed.md | 11 +- raster/r.slope.aspect/r.slope.aspect.md | 68 +-- raster/r.stream.extract/r.stream.extract.md | 28 +- raster/r.terraflow/r.terraflow.md | 2 +- raster/r.texture/r.texture.md | 2 +- raster/r.to.rast3/r.to.rast3.md | 7 +- raster/r.to.rast3elev/r.to.rast3elev.md | 7 +- raster/r.walk/r.walk.md | 4 +- raster/r.water.outlet/r.water.outlet.md | 2 +- raster/r.watershed/front/r.watershed.md | 8 +- raster3d/r3.cross.rast/r3.cross.rast.md | 7 +- raster3d/r3.in.ascii/r3.in.ascii.md | 31 +- raster3d/r3.out.ascii/r3.out.ascii.md | 7 +- raster3d/r3.to.rast/r3.to.rast.md | 7 +- raster3d/raster3dintro.md | 2 +- scripts/i.spectral/i.spectral.md | 6 +- scripts/r.in.wms/r.in.wms.md | 2 +- scripts/r.mapcalc.simple/r.mapcalc.simple.md | 2 +- scripts/r.reclass.area/r.reclass.area.md | 4 +- vector/v.buffer/v.buffer.md | 25 +- vector/v.clean/v.clean.md | 6 +- vector/v.delaunay/v.delaunay.md | 2 +- vector/v.hull/v.hull.md | 8 +- vector/v.label/v.label.md | 2 +- vector/v.random/v.random.md | 19 +- vector/v.surf.rst/v.surf.rst.md | 4 +- vector/v.to.rast3/v.to.rast3.md | 7 +- vector/v.voronoi/v.voronoi.md | 9 +- 38 files changed, 240 insertions(+), 627 deletions(-) diff --git a/display/d.graph/d.graph.md b/display/d.graph/d.graph.md index 9b47ce9abc8..750b2184b56 100644 --- a/display/d.graph/d.graph.md +++ b/display/d.graph/d.graph.md @@ -33,22 +33,17 @@ be used instead. The graphics language is simple, and uses the following commands: -\[ [\#](#comment) \| [move](#move) \| [draw](#draw) \| -[polygon](#polygon) \| [polyline](#polyline) \| [color](#color) \| -[text](#text) \| [size](#size) \| [symbol](#symbol) \| -[rotation](#rotation) \| [icon](#icon) \| [width](#width) \] - -**\#** *comment* +**\#** *comment* A line of comment which is ignored in the processing. -**move** *xpos ypos* +**move** *xpos ypos* The current location is updated to *xpos ypos*. Unless the **-m** flag is used, values are stated as a percent of the active display frame's horizontal (*xpos*) and vertical (*ypos*) size, and may be floating point values. Values are between 0-100. **Note.** A space must separate *xpos* and *ypos*. -**draw** *xpos ypos* +**draw** *xpos ypos* A line is drawn in the current color from the current location to the new location *xpos ypos*, which then becomes the current location. Unless the **-m** flag is used, values are stated as a percent of the @@ -56,21 +51,21 @@ active display frame's horizontal (*xpos*) and vertical (*ypos*) size, and may be floating point values. Values are between 0-100. **Note.** A space must separate *xpos* and *ypos*. -**polygon** +**polygon**    *xpos ypos*    *xpos ypos*   ... The coordinates appearing beneath the word *polygon*, one pair per line, circumscribe a polygon that is to be filled with the current color. -**polyline** +**polyline**    *xpos ypos*    *xpos ypos*   ... The coordinates appearing beneath the word *polyline*, one pair per line, circumscribe a polygon that is not to be filled with color. -**color** *color* +**color** *color* Sets the current color to that stated; subsequent graphics will be drawn in the stated color, until the current color is set to a different color. Options are *red*, *orange*, *yellow*, *green*, *blue*, *indigo*, @@ -78,20 +73,20 @@ color. Options are *red*, *orange*, *yellow*, *green*, *blue*, *indigo*, (separated by colons), or the word "none" (draws in the default background color). -**text** *line-of-text* +**text** *line-of-text* The stated text is drawn at the current location using the current color, and the new current location is then positioned at the end of the text string. -**size** *xper yper* +**size** *xper yper* Subsequent text will be drawn such that the text is *xper* percent of the graphics monitor display frame wide and *yper* percent of the frame high. By default, the text size is set to 5 percent of the active frame's width and 5 percent of the frame's height. If only one value is -given, then that value will be used for both x and y scaling. -**Note.** A space must separate *xper* and *yper*. +given, then that value will be used for both x and y scaling. +A space must separate *xper* and *yper*. -**symbol** *type size xper yper \[line_color \[fill_color\]\]* +**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 @@ -102,15 +97,15 @@ 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 *fill_color* is grey. -**rotation** *angle* +**rotation** *angle* Subsequent text and symbols will be drawn such that they are rotated *angle* degrees counter-clockwise from east. -**icon** *type size x y* +**icon** *type size x y* Draws an icon of types *o*, *x*, or *+* with specified *size* (in %) at location *x,y*. Note: type *o* designates a square. -**width** *value* +**width** *value* Subsequent lines (including non-FreeType text) will be drawn with the given pixel thickness. The default value is 0. diff --git a/display/d.rhumbline/d.rhumbline.md b/display/d.rhumbline/d.rhumbline.md index 7c9776e53b3..b8c95fac02b 100644 --- a/display/d.rhumbline/d.rhumbline.md +++ b/display/d.rhumbline/d.rhumbline.md @@ -28,7 +28,7 @@ d.rhumbline coordinates=55:58W,33:18S,26:43E,60:37N \ d.grid 10 ``` - +![Rhumbline (loxodrome)](d_rhumbline.png) *Rhumbline (loxodrome)* ## NOTES diff --git a/display/d.text/d.text.md b/display/d.text/d.text.md index 3f53002c20a..1eca42a92ec 100644 --- a/display/d.text/d.text.md +++ b/display/d.text/d.text.md @@ -53,7 +53,7 @@ using 4/100'ths (4%) of the active frame's vertical space per line: d.text text="This is a test of d.text" color=yellow bgcolor=gray size=4 ``` - +![Displayed Text](d_text.png) *Displayed Text* ## NOTES diff --git a/imagery/i.atcorr/i.atcorr.md b/imagery/i.atcorr/i.atcorr.md index 452ff8adbcd..aeba526d904 100644 --- a/imagery/i.atcorr/i.atcorr.md +++ b/imagery/i.atcorr/i.atcorr.md @@ -39,371 +39,77 @@ different reference system. ### A. Geometrical conditions - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeDescriptionDetails
1meteosat observationenter month,day,decimal hour (universal time-hh.ddd)
-                      n. of column,n. of line. (full scale -5000*2500) 
2goes east observationenter month,day,decimal hour (universal time-hh.ddd)
-                      n. of column,n. of line. (full scale -17000*12000)c
3goes west observationenter month,day,decimal hour (universal time-hh.ddd)
-                      n. of column,n. of line. (full scale -17000*12000)
4avhrr (PM noaa)enter month,day,decimal hour (universal time-hh.ddd)
-                      n. of column(1-2048),xlonan,hna
-                      give long.(xlonan) and overpass hour (hna) -at
-                      the ascendant node at equator
5avhrr (AM noaa)enter month,day,decimal hour (universal time-hh.ddd)
-                      n. of column(1-2048),xlonan,hna
-                      give long.(xlonan) and overpass hour (hna) -at
-                      the ascendant node at equator
6hrv (spot)enter month,day,hh.ddd,long.,lat. *
7tm (landsat)enter month,day,hh.ddd,long.,lat. *
8etm+ (landsat7)enter month,day,hh.ddd,long.,lat. *
9liss (IRS 1C)enter month,day,hh.ddd,long.,lat. *
10asterenter month,day,hh.ddd,long.,lat. *
11avnirenter month,day,hh.ddd,long.,lat. *
12ikonosenter month,day,hh.ddd,long.,lat. *
13RapidEyeenter month,day,hh.ddd,long.,lat. *
14VGT1 (SPOT4)enter month,day,hh.ddd,long.,lat. *
15VGT2 (SPOT5)enter month,day,hh.ddd,long.,lat. *
16WorldView 2enter month,day,hh.ddd,long.,lat. *
17QuickBirdenter month,day,hh.ddd,long.,lat. *
18LandSat 8enter month,day,hh.ddd,long.,lat. *
19Geoeye 1enter month,day,hh.ddd,long.,lat. *
20Spot6enter month,day,hh.ddd,long.,lat. *
21Spot7enter month,day,hh.ddd,long.,lat. *
22Pleiades1Aenter month,day,hh.ddd,long.,lat. *
23Pleiades1Benter month,day,hh.ddd,long.,lat. *
24Worldview3enter month,day,hh.ddd,long.,lat. *
25Sentinel-2Aenter month,day,hh.ddd,long.,lat. *
26Sentinel-2Benter month,day,hh.ddd,long.,lat. *
27PlanetScope 0c 0denter month,day,hh.ddd,long.,lat. *
28PlanetScope 0eenter month,day,hh.ddd,long.,lat. *
29PlanetScope 0f 10enter month,day,hh.ddd,long.,lat. *
30Worldview4enter month,day,hh.ddd,long.,lat. *
31AVIRISenter month,day,hh.ddd,long.,lat. *
32Hyperion VNIRenter month,day,hh.ddd,long.,lat. *
33Hyperion SWIRenter month,day,hh.ddd,long.,lat. *
- -> *NOTE*: for HRV, TM, ETM+, LISS and ASTER experiments, longitude and -> latitude are the coordinates of the scene center. Latitude must be \> -> 0 for northern hemisphere and \< 0 for southern. Longitude must be \> -> 0 for eastern hemisphere and \< 0 for western. +| Code | Description | Details | +|------|------------------------------|---------| +| 1 | **meteosat** observation | enter month, day, decimal hour (universal time-hh.ddd), n. of column, n. of line. (full scale 5000×2500) | +| 2 | **goes east** observation | enter month, day, decimal hour (universal time-hh.ddd), n. of column, n. of line. (full scale 17000×12000) | +| 3 | **goes west** observation | enter month, day, decimal hour (universal time-hh.ddd), n. of column, n. of line. (full scale 17000×12000) | +| 4 | **avhrr** (PM noaa) | enter month, day, decimal hour (universal time-hh.ddd), n. of column(1-2048), xlonan, hna, give long.(xlonan) and overpass hour (hna) at the ascendant node at equator | +| 5 | **avhrr** (AM noaa) | enter month, day, decimal hour (universal time-hh.ddd)
n. of column(1-2048), xlonan, hna, give long.(xlonan) and overpass hour (hna) at the ascendant node at equator | +| 6 | **hrv** (spot) | enter month, day, hh.ddd, long., lat. * | +| 7 | **tm** (landsat) | enter month, day, hh.ddd, long., lat. * | +| 8 | **etm+** (landsat7) | enter month, day, hh.ddd, long., lat. * | +| 9 | **liss** (IRS 1C) | enter month, day, hh.ddd, long., lat. * | +| 10 | **aster** | enter month, day, hh.ddd, long., lat. * | +| 11 | **avnir** | enter month, day, hh.ddd, long., lat. * | +| 12 | **ikonos** | enter month, day, hh.ddd, long., lat. * | +| 13 | **RapidEye** | enter month, day, hh.ddd, long., lat. * | +| 14 | **VGT1 (SPOT4)** | enter month, day, hh.ddd, long., lat. * | +| 15 | **VGT2 (SPOT5)** | enter month, day, hh.ddd, long., lat. * | +| 16 | **WorldView 2** | enter month, day, hh.ddd, long., lat. * | +| 17 | **QuickBird** | enter month, day, hh.ddd, long., lat. * | +| 18 | **LandSat 8** | enter month, day, hh.ddd, long., lat. * | +| 19 | **Geoeye 1** | enter month, day, hh.ddd, long., lat. * | +| 20 | **Spot6** | enter month, day, hh.ddd, long., lat. * | +| 21 | **Spot7** | enter month, day, hh.ddd, long., lat. * | +| 22 | **Pleiades1A** | enter month, day, hh.ddd, long., lat. * | +| 23 | **Pleiades1B** | enter month, day, hh.ddd, long., lat. * | +| 24 | **Worldview3** | enter month, day, hh.ddd, long., lat. * | +| 25 | **Sentinel-2A** | enter month, day, hh.ddd, long., lat. * | +| 26 | **Sentinel-2B** | enter month, day, hh.ddd, long., lat. * | +| 27 | **PlanetScope 0c 0d** | enter month, day, hh.ddd, long., lat. * | +| 28 | **PlanetScope 0e** | enter month, day, hh.ddd, long., lat. * | +| 29 | **PlanetScope 0f 10** | enter month, day, hh.ddd, long., lat. * | +| 30 | **Worldview4** | enter month, day, hh.ddd, long., lat. * | +| 31 | **AVIRIS** | enter month, day, hh.ddd, long., lat. * | +| 32 | **Hyperion VNIR** | enter month, day, hh.ddd, long., lat. * | +| 33 | **Hyperion SWIR** | enter month, day, hh.ddd, long., lat. * | + +*NOTE*: for HRV, TM, ETM+, LISS and ASTER experiments, longitude and +latitude are the coordinates of the scene center. Latitude must be \> +0 for northern hemisphere and \< 0 for southern. Longitude must be \> +0 for eastern hemisphere and \< 0 for western. ### B. Atmospheric model - ---- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeMeaning
0no gaseous absorption
1tropical
2midlatitude summer
3midlatitude winter
4subarctic summer
5subarctic winter
6us standard 62
7Define your own atmospheric model as a set of the following 5 -parameters per each measurement:
-
-altitude [km]
-pressure [mb]
-temperature [k]
-h2o density [g/m3]
-o3 density [g/m3]
-
-For example: there is one radiosonde measurement for each altitude of -0-25km at a step of 1km, one measurement for each altitude of 25-50km at -a step of 5km, and two single measurements for altitudes 70km and 100km. -This makes 34 measurements. In that case, there are 34*5 values to -input.
8Define your own atmospheric model providing values of the water -vapor and ozone content:
-
-uw [g/cm2]
-uo3 [cm-atm]
-
-The profile is taken from us62.
+| Code | Meaning | +|------|---------| +| 0 | no gaseous absorption | +| 1 | tropical | +| 2 | midlatitude summer | +| 3 | midlatitude winter | +| 4 | subarctic summer | +| 5 | subarctic winter | +| 6 | us standard 62 | +| 7 | Define your own atmospheric model as a set of the following 5 parameters per each measurement: altitude [km], pressure [mb], temperature [k], h2o density [g/m³], o3 density [g/m³]. For example: there is one radiosonde measurement for each altitude of 0-25km at a step of 1km, one measurement for each altitude of 25-50km at a step of 5km, and two single measurements for altitudes 70km and 100km. This makes 34 measurements. In that case, there are 34*5 values to input. | +| 8 | Define your own atmospheric model providing values of the water vapor and ozone content: uw [g/cm²], uo3 [cm-atm]. The profile is taken from us62.| ### C. Aerosols model - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeMeaningDetails
0no aerosols 
1continental model 
2maritime model 
3urban model 
4shettle model for background desert aerosol 
5biomass burning 
6stratospheric model 
7define your own modelEnter the volumic percentage of each component:
-
-c(1) = volumic % of dust-like
-c(2) = volumic % of water-soluble
-c(3) = volumic % of oceanic
-c(4) = volumic % of soot
-
-All values should be between 0 and 1.
8define your own modelSize distribution function: Multimodal Log Normal (up to 4 -modes).
9define your own modelSize distribution function: Modified gamma.
10define your own modelSize distribution function: Junge Power-Law.
11define your own modelSun-photometer measurements, 50 values max, entered as:
-
-r and d V / d (logr)
-
-where r is the radius [micron], V is the volume, d V / d (logr) -[cm3/cm2/micron].
-
-Followed by:
-
-nr and ni for each wavelength
-
-where nr and ni are respectively the real and imaginary part of the -refractive index.
+| Code | Meaning | Details | +|------|---------|---------| +| 0 | no aerosols | | +| 1 | continental model | | +| 2 | maritime model | | +| 3 | urban model | | +| 4 | shettle model for background desert aerosol | | +| 5 | biomass burning | | +| 6 | stratospheric model | | +| 7 | define your own model | Enter the volumic percentage of each component: c(1) = volumic % of dust-like, c(2) = volumic % of water-soluble, c(3) = volumic % of oceanic, c(4) = volumic % of soot. All values should be between 0 and 1. | +| 8 | define your own model | Size distribution function: Multimodal Log Normal (up to 4 modes). | +| 9 | define your own model | Size distribution function: Modified gamma. | +| 10 | define your own model | Size distribution function: Junge Power-Law. | +| 11 | define your own model | Sun-photometer measurements, 50 values max, entered as:r and dV/d(logr) where r is the radius [micron], V is the volume, dV/d(logr) [cm³/cm²/micron]. Followed by: nr and ni for each wavelength where nr and ni are respectively the real and imaginary part of the refractive index. | ### D. Aerosol concentration model (visibility) @@ -470,44 +176,17 @@ simulation. Specifically: - wlsup: This represents the upper wavelength limit (or maximum wavelength) of the spectral band for the simulation. - ---- - - - - - - - - - - - - - - - - - - - - - - -
CodeMeaning
-2Enter wlinf, wlsup.
-The filter function will be equal to 1 over the whole band (as iwave=0) -but step by step output will be printed.
-1Enter wl (monochr. cond, gaseous absorption is included).
0Enter wlinf, wlsup.
-The filter function will be equal to 1 over the whole band.
1Enter wlinf, wlsup and user's filter function s (lambda) by step of -0.0025 micrometer.
+| Code | Meaning | +|------|---------| +| -2 | Enter wlinf, wlsup. The filter function will be equal to 1 over the whole band (as iwave=0) but step by step output will be printed. | +| -1 | Enter wl (monochr. cond, gaseous absorption is included). | +| 0 | Enter wlinf, wlsup.
The filter function will be equal to 1 over the whole band. | +| 1 | Enter wlinf, wlsup and user's filter function s(lambda) by step of 0.0025 micrometer. | Pre-defined satellite bands: -| | | +| Code | Band name (peak response) | |----------|-----------------------------------------------------| -| **Code** | **Band name (peak response)** | | 2 | **meteosat** vis band (0.350-1.110) | | 3 | **goes east** band vis (0.490-0.900) | | 4 | **goes west** band vis (0.490-0.900) | diff --git a/imagery/i.cluster/i.cluster.md b/imagery/i.cluster/i.cluster.md index 2169d29c185..fb673d7ecad 100644 --- a/imagery/i.cluster/i.cluster.md +++ b/imagery/i.cluster/i.cluster.md @@ -14,11 +14,8 @@ the clusters (e.g., land cover spectral signatures) are influenced by six parameters set by the user. A relevant parameter set by the user is the initial number of clusters to be discriminated. - - -| | -|----------------------------------------------------------------------| -| *Fig.: Land use/land cover clustering of LANDSAT scene (simplified)* | +![Land use/land cover clustering of LANDSAT scene](i_cluster_landsat_clustering.png) +*Fig.: Land use/land cover clustering of LANDSAT scene (simplified)* *i.cluster* starts by generating spectral signatures for this number of clusters and "attempts" to end up with this number of clusters during @@ -60,26 +57,26 @@ classify only the same imagery group used for generating signatures. ### Parameters -**group=***name* +**group:** The name of the group file which contains the imagery files that the user wishes to classify. -**subgroup=***name* +**subgroup:** The name of the subset of the group specified in group option, which must contain only imagery band files and more than one band file. The user must create a group and a subgroup by running the GRASS program *[i.group](i.group.md)* before running *i.cluster*. -**signaturefile=***name* +**signaturefile:** The name assigned to output signature file which contains signatures of classes and can be used as the input file for the GRASS program *[i.maxlik](i.maxlik.md)* for an unsupervised classification. -**classes=***value* +**classes:** The number of clusters that will initially be identified in the clustering process before the iterations begin. -**seed=***name* +**seed:** The name of a seed signature file is optional. The seed signatures are signatures that contain cluster means and covariance matrices which were calculated prior to the current run of *i.cluster*. They may be acquired @@ -89,22 +86,22 @@ by *[g.gui.iclass](g.gui.iclass.md)*). The purpose of seed signatures is to optimize the cluster decision boundaries (means) for the number of clusters specified. -**sample=***rows,cols* +**sample:** These numbers are optional with default values based on the size of the data set such that the total pixels to be processed is approximately 10,000 (consider round up). The smaller these numbers, the larger the sample size used to generate the signatures for the classes defined. -**iterations=***value* +**iterations:** This parameter determines the maximum number of iterations which is greater than the number of iterations predicted to achieve the optimum percent convergence. The default value is 30. If the number of iterations reaches the maximum designated by the user; the user may want to rerun *i.cluster* with a higher number of iterations (see -[*reportfile*](#reportfile)). -Default: 30 +*reportfile*). +Default: 30 -**convergence=***value* +**convergence:** A high percent convergence is the point at which cluster means become stable during the iteration process. The default value is 98.0 percent. When clusters are being created, their means constantly change as pixels @@ -118,10 +115,10 @@ iterative process. The percent convergence should be reached before the maximum number of iterations. If the maximum number of iterations is reached, it is probable that the desired percent convergence was not reached. The number of iterations is reported in the cluster statistics -in the report file (see [*reportfile*](#reportfile)). +in the report file (see *reportfile*). Default: 98.0 -**separation=***value* +**separation:** This is the minimum separation below which clusters will be merged in the iteration process. The default value is 0.0. This is an image-specific number (a "magic" number) that depends on the image data @@ -129,16 +126,16 @@ being classified and the number of final clusters that are acceptable. Its determination requires experimentation. Note that as the minimum class (or cluster) separation is increased, the maximum number of iterations should also be increased to achieve this separation with a -high percentage of convergence (see [*convergence*](#convergence)). +high percentage of convergence (see *convergence*). Default: 0.0 -**min_size=***value* +**min_size:** This is the minimum number of pixels that will be used to define a cluster, and is therefore the minimum number of pixels for which means and covariance matrices will be calculated. -Default: 17 +Default: 17 -**reportfile=***name* +**reportfile:** The reportfile is an optional parameter which contains the result, i.e., the statistics for each cluster. Also included are the resulting percent convergence for the clusters, the number of iterations that was required diff --git a/raster/r.buffer/r.buffer.md b/raster/r.buffer/r.buffer.md index ee27825bd4f..e83da1b3972 100644 --- a/raster/r.buffer/r.buffer.md +++ b/raster/r.buffer/r.buffer.md @@ -91,7 +91,7 @@ r.category input=roads.buf 6 400-500 meters ``` - +![Distances to road](r_buffer_road.png) *Distances to road* ## SEE ALSO diff --git a/raster/r.cost/r.cost.md b/raster/r.cost/r.cost.md index cb7545bbafe..98fa9951631 100644 --- a/raster/r.cost/r.cost.md +++ b/raster/r.cost/r.cost.md @@ -75,11 +75,8 @@ also considered. Knight's move example: - - -| | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| *Flat cost surface without (left pane) and with the knight's move (right pane). The default is to grow the cost outwards in 8 directions. Using the knight's move grows it outwards in 16 directions.* | +![Flat cost surface without and with the knight's move](rcost_knightsmove.png) +*Flat cost surface without (left pane) and with the knight's move (right pane). The default is to grow the cost outwards in 8 directions. Using the knight's move grows it outwards in 16 directions.* If the **nearest** output parameter is specified, the module will calculate for each cell its nearest starting point based on the @@ -95,11 +92,8 @@ option to help the algorithm pick a particular direction. Example for solving multiple directions: - - -| | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| *A field of equal cumulative costs with multiple paths (black). By default a path along the edge will be selected (red). Path selection can be controlled with the solver option (blue).* | +![A field of equal cumulative costs with multiple paths](rcost_solvedir.png) +*A field of equal cumulative costs with multiple paths (black). By default a path along the edge will be selected (red). Path selection can be controlled with the solver option (blue).* Multiple directions can be solved as in the above example with the following steps: @@ -241,9 +235,7 @@ Spearfish region): d.rast dist_meters ``` - - -## Movement Direction +### Movement Direction The movement direction surface is created to record the sequence of movements that created the cost accumulation surface. This movement diff --git a/raster/r.grow.distance/r.grow.distance.md b/raster/r.grow.distance/r.grow.distance.md index fd1e07629a1..df2f8281117 100644 --- a/raster/r.grow.distance/r.grow.distance.md +++ b/raster/r.grow.distance/r.grow.distance.md @@ -82,10 +82,10 @@ r.grow.distance input=streams_derived distance=dist_from_streams r.colors map=dist_from_streams color=rainbow ``` - +![Euclidean distance from the streams network in meters (map subset)](r_grow_distance.png) *Euclidean distance from the streams network in meters (map subset)* - +![r_grow_distance_zoom](r_grow_distance_zoom.png) *Euclidean distance from the streams network in meters (detail, numbers shown with d.rast.num)* @@ -97,7 +97,7 @@ r.grow.distance -m input=sea distance=dist_from_sea_geodetic metric=geodesic r.colors map=dist_from_sea_geodetic color=rainbow ``` - +![Geodesic distances to sea in meters](r_grow_distance_sea.png) *Geodesic distances to sea in meters* ## SEE ALSO diff --git a/raster/r.gwflow/r.gwflow.md b/raster/r.gwflow/r.gwflow.md index 29c9ef8cbc6..edb41d72a8d 100644 --- a/raster/r.gwflow/r.gwflow.md +++ b/raster/r.gwflow/r.gwflow.md @@ -9,11 +9,8 @@ project's coordinate reference system must be meters. This module is sensitive to mask settings. All cells which are outside the mask are ignored and handled as no flow boundaries. - - -| | -|------------------------| -| *Workflow of r.gwflow* | +![Workflow of r.gwflow](r_gwflow_concept.png) +*Workflow of r.gwflow* *r.gwflow* calculates the piezometric head and optionally the water budget and the filter velocity field, based on the hydraulic diff --git a/raster/r.lake/r.lake.md b/raster/r.lake/r.lake.md index 35a4cfe1368..2252a977f08 100644 --- a/raster/r.lake/r.lake.md +++ b/raster/r.lake/r.lake.md @@ -93,8 +93,8 @@ d.rast flooding d.vect streets_wake ``` - -Small flooding along a street (*r.lake*, using Lidar 1m DEM) +![Small flooding along a street](r_lake_lidar_dem.jpg) +*Small flooding along a street (*r.lake*, using Lidar 1m DEM)* ## SEE ALSO diff --git a/raster/r.li/r.li.cwed/r.li.cwed.md b/raster/r.li/r.li.cwed/r.li.cwed.md index fc25c4aeb68..de6c57a451f 100644 --- a/raster/r.li/r.li.cwed/r.li.cwed.md +++ b/raster/r.li/r.li.cwed/r.li.cwed.md @@ -9,16 +9,19 @@ with: - **k**: attribute - **m**: number of non-null attributes in the sampling area -- **eik**: total +- **e_ik**: total length of edge in landscape between patch types i and k -- **dik**: +- **d_ik**: dissimilarity (edge contrast weight) between patch types i and k - **Area**: total landscape area The input file contains a row for each couple of patch type that we want to consider in the calculation. Each row must be saved using this -syntax: -patchType1,patchType2,dissimilarityBetweenPatchType1andPatchType2 +syntax: + +```sh +patchType1,patchType2,dissimilarityBetweenPatchType1andPatchType2 +``` ## NOTES diff --git a/raster/r.slope.aspect/r.slope.aspect.md b/raster/r.slope.aspect/r.slope.aspect.md index 415e6657136..dc3597ad0f6 100644 --- a/raster/r.slope.aspect/r.slope.aspect.md +++ b/raster/r.slope.aspect/r.slope.aspect.md @@ -45,7 +45,7 @@ where the terrain is almost flat. A option **min_slope** can be used to specify the minimum slope for which aspect is computed. For all cells with slope \< **min_slope**, both slope and aspect are set to zero. - +![aspect_diagram](aspect_diagram.png) The **slope** output raster map contains slope values, stated in degrees of inclination from the horizontal if **format**=degrees option (the @@ -58,45 +58,20 @@ The curvatures are expressed as 1/metres, e.g. a curvature of 0.05 corresponds to a radius of curvature of 20m. Convex form values are positive and concave form values are negative. - ----- - - - - - - - - - - - - - - - - - -
-

Example DEM
-
-

-

Slope (degree) from example DEM
-
-

-

Aspect (degree) from example DEM
-
-

-

Tangential curvature (m-1) from example DEM
-
-

-

Profile curvature (m-1) from example DEM
-
-

+![dem](dem.png) +*Example DEM* + +![slope](slope.png) +*Slope (degree) from example DEM* + +![aspect](aspect.png) +*Aspect (degree) from example DEM* + +![tcurv](tcurv.png) +*Tangential curvature (1/m) from example DEM* + +![pcurv](pcurv.png) +*Profile curvature (1/m) from example DEM* For some applications, the user will wish to use a reclassified raster map of slope that groups slope values into ranges of slope. This can be @@ -114,10 +89,11 @@ reclassification is given below: 5 9- 11 16- 20% 6 12- 14 21- 25% 7 15- 90 26% and higher +``` - The following color table works well with the above - reclassification. +The following color table works well with the above reclassification. +```sh category red green blue 0 179 179 179 @@ -196,10 +172,10 @@ r.colors map=pcurv color=curvature r.colors map=tcurv color=curvature ``` - - - - +![r_slope_aspect_slope](r_slope_aspect_slope.png) +![r_slope_aspect_aspect](r_slope_aspect_aspect.png) +![r_slope_aspect_pcurv](r_slope_aspect_pcurv.png) +![r_slope_aspect_tcurv](r_slope_aspect_tcurv.png) Figure: Slope, aspect, profile and tangential curvature raster map (North Carolina dataset) diff --git a/raster/r.stream.extract/r.stream.extract.md b/raster/r.stream.extract/r.stream.extract.md index ee757ede480..3c5aa50735d 100644 --- a/raster/r.stream.extract/r.stream.extract.md +++ b/raster/r.stream.extract/r.stream.extract.md @@ -24,11 +24,11 @@ Option **threshold** defines the minimum (optionally modified) flow accumulation value that will initiate a new stream. If Montgomery's method for channel initiation is used, the cell value of the accumulation input map is multiplied by -`(tan(local slope))``mexp` and then compared to +`(tan(local slope))^mexp` and then compared to **threshold**. If **mexp** is given, then the method of Montgomery and Foufoula-Georgiou (1993) is used to initiate a stream with this value. The cell value of the accumulation input map is multiplied by -`(tan(local slope))``mexp` and then compared to +`(tan(local slope))^mexp` and then compared to **threshold**. If threshold is reached or exceeded, a new stream is initiated. The default value 0 disables Montgomery. Montgomery and Foufoula-Georgiou (1993) generally recommend to use 2.0 as exponent. @@ -174,16 +174,16 @@ r.mapcalc expr="elev_ned_30m.acc.weighed = elev_ned_30m.acc * weight" r.colors map=elev_ned_30m.acc.weighed raster=elev_ned_30m.acc ``` -[](r_stream_extract_weights_zoom.png) -Weight map (spatial subset with lake in the southern half) +![Weight map](r_stream_extract_weights_zoom.png) +*Weight map (spatial subset with lake in the southern half)* -[](r_stream_extract_accum_orig_zoom.png) -Original flow accumulation map (spatial subset with lake in the southern -half) +![Original flow accumulation map](r_stream_extract_accum_orig_zoom.png) +*Original flow accumulation map (spatial subset with lake in the southern +half)* -[](r_stream_extract_accum_weighted_zoom.png) -Weighed flow accumulation map (spatial subset with lake in the southern -half) +![Weighed flow accumulation map](r_stream_extract_accum_weighted_zoom.png) +*Weighed flow accumulation map (spatial subset with lake in the southern +half)* Display both the original and the weighed accumulation map. Compare them and proceed if the weighed accumulation map makes sense. @@ -206,11 +206,11 @@ r.stream.extract elevation=elev_ned_30m@PERMANENT \ Now display both stream maps and decide which one is more realistic. -[](r_stream_extract_streams_noweight.png) -Extracted streams from original flow accumulation map +![Extracted streams from original flow accumulation map](r_stream_extract_streams_noweight.png) +*Extracted streams from original flow accumulation map* -[](r_stream_extract_streams_weighed.png) -Extracted streams from weighed flow accumulation map +![Extracted streams from weighed flow accumulation map](r_stream_extract_streams_weighed.png) +*Extracted streams from weighed flow accumulation map* ## REFERENCES diff --git a/raster/r.terraflow/r.terraflow.md b/raster/r.terraflow/r.terraflow.md index 39e1c685fa6..4567d342615 100644 --- a/raster/r.terraflow/r.terraflow.md +++ b/raster/r.terraflow/r.terraflow.md @@ -143,7 +143,7 @@ g.region raster=elev_lid792_1m r.terraflow elevation=elev_lid792_1m accumulation=elev_lid792_1m_accumulation ``` - +![Flow accumulation](rterraflow_accumulation.png) *Flow accumulation* Spearfish sample data set: diff --git a/raster/r.texture/r.texture.md b/raster/r.texture/r.texture.md index 9a1cee98eee..a33fead8827 100644 --- a/raster/r.texture/r.texture.md +++ b/raster/r.texture/r.texture.md @@ -250,7 +250,7 @@ direction, except for those areas where there are three columns of equal values (as size=3). The overlaid grid highlights that the texture measures output maps are cropped at the margins. - +![IDM textures according to direction](r_texture_directions_example.png) *IDM textures according to direction* ## REFERENCES diff --git a/raster/r.to.rast3/r.to.rast3.md b/raster/r.to.rast3/r.to.rast3.md index c6de372c6e8..88a51ca2473 100644 --- a/raster/r.to.rast3/r.to.rast3.md +++ b/raster/r.to.rast3/r.to.rast3.md @@ -5,11 +5,8 @@ important to properly set the 3D region settings, especially number or layers and depth of layers. If the 2D and 3D region settings are different, the 2D resolution will be adjusted to the 3D resolution. - - -| | -|------------------------| -| *How r.to.rast3 works* | +![How r.to.rast3 works](r.to.rast3.png) +*How r.to.rast3 works* ## NOTES diff --git a/raster/r.to.rast3elev/r.to.rast3elev.md b/raster/r.to.rast3elev/r.to.rast3elev.md index 1fd4ff5c074..68d4a2ca187 100644 --- a/raster/r.to.rast3elev/r.to.rast3elev.md +++ b/raster/r.to.rast3elev/r.to.rast3elev.md @@ -4,11 +4,8 @@ raster maps. If the 2d and 3d region settings are different, the 2d resolution will be adjust to the 3d resolution. - - -| | -|----------------------------| -| *How r.to.rast3elev works* | +![How r.to.rast3elev works](r.to.rast3elev.png) +*How r.to.rast3elev works* ## NOTES diff --git a/raster/r.walk/r.walk.md b/raster/r.walk/r.walk.md index 198e4a81e92..ccf30b2e5e7 100644 --- a/raster/r.walk/r.walk.md +++ b/raster/r.walk/r.walk.md @@ -83,9 +83,9 @@ K x x x K The minimum cumulative costs are computed using Dijkstra's algorithm, that find an optimum solution (for more details see *r.cost*, that uses -the same algorithm). +the same algorithm). -## Movement Direction +### Movement Direction The movement direction surface is created to record the sequence of movements that created the cost accumulation surface. This movement diff --git a/raster/r.water.outlet/r.water.outlet.md b/raster/r.water.outlet/r.water.outlet.md index 7301a301cda..2de1be8ff3b 100644 --- a/raster/r.water.outlet/r.water.outlet.md +++ b/raster/r.water.outlet/r.water.outlet.md @@ -46,7 +46,7 @@ d.his h=accum_5K i=basin_A30 r.report map=basin_A30 units=h ``` - +![Figure: Watershed draped over flow accumulation](r_water_outlet.png) *Figure: Watershed draped over flow accumulation* ## SEE ALSO diff --git a/raster/r.watershed/front/r.watershed.md b/raster/r.watershed/front/r.watershed.md index 7bbecf8b243..2e8e59ee7e4 100644 --- a/raster/r.watershed/front/r.watershed.md +++ b/raster/r.watershed/front/r.watershed.md @@ -151,9 +151,9 @@ from article entitled *Revised Slope Steepness Factor for the Universal Soil Loss Equation* (McCool et al. 1987). Since the S factor is a small number (usually less than one), the GRASS output map is of type DCELL. -### AT least-cost search algorithm +### A^T least-cost search algorithm -*r.watershed* uses an AT least-cost search algorithm (see +*r.watershed* uses an A^T least-cost search algorithm (see REFERENCES section) designed to minimize the impact of DEM data errors. Compared to *[r.terraflow](r.terraflow.md)*, this algorithm provides more accurate results in areas of low slope as well as DEMs constructed @@ -182,7 +182,7 @@ to those obtained when running *[r.cost](r.cost.md)* and direction (SFD, D8) and multiple flow direction (MFD). With MFD, water flow is distributed to all neighbouring cells with lower elevation, using slope towards neighbouring cells as a weighing factor for -proportional distribution. The AT least-cost path is always +proportional distribution. The A^T least-cost path is always included. As a result, depressions and obstacles are traversed with a graceful flow convergence before the overflow. The convergence factor causes flow accumulation to converge more strongly with higher values. @@ -418,7 +418,7 @@ Display output in a nice way ## REFERENCES -- Ehlschlaeger C. (1989). *Using the AT Search Algorithm to +- Ehlschlaeger C. (1989). *Using the A^T Search Algorithm to Develop Hydrologic Models from Digital Elevation Data*, **Proceedings of International Geographic Information Systems (IGIS) Symposium '89**, pp 275-281 (Baltimore, MD, 18-19 March 1989). diff --git a/raster3d/r3.cross.rast/r3.cross.rast.md b/raster3d/r3.cross.rast/r3.cross.rast.md index 7d2d7b51367..2e7995d1b96 100644 --- a/raster3d/r3.cross.rast/r3.cross.rast.md +++ b/raster3d/r3.cross.rast/r3.cross.rast.md @@ -6,11 +6,8 @@ map is located in the z-coordinate space of the 3D map. If so, the 3D voxel value for this position is transferred to the related cross section output map cell, otherwise the NULL value is set. - - -| | -|---------------------------| -| *How r3.cross.rast works* | +![How r3.cross.rast works](r3.cross.rast.png) +*How r3.cross.rast works* If the 2D and 3D region settings are different, the 2D resolution will be adjust to the 3D resolution. diff --git a/raster3d/r3.in.ascii/r3.in.ascii.md b/raster3d/r3.in.ascii/r3.in.ascii.md index 356d2a6ee1f..c0685f26dcb 100644 --- a/raster3d/r3.in.ascii/r3.in.ascii.md +++ b/raster3d/r3.in.ascii/r3.in.ascii.md @@ -16,11 +16,8 @@ The data is automatically imported into the correct internal coordinate system, that is visualized in the following picture, independently from the specified ordering in the ASCII input file: - - -| | -|--------------------------------------------------------------------------| -| *The volume coordinate system and tile layout of the imported voxel map* | +![The volume coordinate system and tile layout](raster3d_layout.png) +*The volume coordinate system and tile layout of the imported voxel map* ### Format @@ -64,7 +61,10 @@ separated by *space* or *CR*. input file the upper-left (NW) corner of the bottom level comes first. The according order option is: nsbt for north -\> south, bottom -\> top ordering. This is identical with *r.in.ascii* for single level data. So -the y coordinate is 0 at the northern edge. north: 3.0 +the y coordinate is 0 at the northern edge. + +```sh +north: 3.0 south: 0.0 east: 4.0 west: 0.0 @@ -73,18 +73,13 @@ bottom: 0.0 rows: 3 cols: 4 levels: 2 -w111x1,y1,z1 w211x2,y1,z1 w311x3,y1,z1 -w411x4,y1,z1 -w121x1,y2,z1 w221x2,y2,z1 w321x3,y2,z1 -w421x4,y2,z1 -w131x1,y3,z1 w231x2,y3,z1 w331x3,y3,z1 -w431x4,y3,z1 -w112x1,y1,z2 w212x2,y1,z2 w312x3,y1,z2 -w412x4,y1,z2 -w122x1,y2,z2 w222x2,y2,z2 w322x3,y2,z2 -w422x4,y2,z2 -w132x1,y3,z2 w232x2,y3,z2 w332x3,y3,z2 -w432x4,y3,z2 +x1,y1,z1 x2,y1,z1 x3,y1,z1 x4,y1,z1 +x1,y2,z1 x2,y2,z1 x3,y2,z1 x4,y2,z1 +x1,y3,z1 x2,y3,z1 x3,y3,z1 x4,y3,z1 +x1,y1,z2 x2,y1,z2 x3,y1,z2 x4,y1,z2 +x1,y2,z2 x2,y2,z2 x3,y2,z2 x4,y2,z2 +x1,y3,z2 x2,y3,z2 x3,y3,z2 x4,y3,z2 +``` Note that unit tests for *r3.in.ascii* are implemented in the *test.r3.out.ascii.sh* script located in the *r3.out.ascii* directory. diff --git a/raster3d/r3.out.ascii/r3.out.ascii.md b/raster3d/r3.out.ascii/r3.out.ascii.md index 51a58959d98..6a3a77e0521 100644 --- a/raster3d/r3.out.ascii/r3.out.ascii.md +++ b/raster3d/r3.out.ascii/r3.out.ascii.md @@ -76,11 +76,8 @@ Supported orders are: The internal storage scheme of 3D raster maps is visualized in the following picture: - - -| | -|-----------------------------------------------------------------| -| *The coordinate system and tile layout of a voxel map in GRASS* | +![The coordinate system and tile layout](raster3d_layout.png) +*The coordinate system and tile layout of a voxel map in GRASS* One level maps can be imported with *r.in.ascii* (2D raster) using the default **nsbt** order and removing the header lines "version", "order", diff --git a/raster3d/r3.to.rast/r3.to.rast.md b/raster3d/r3.to.rast/r3.to.rast.md index 43f63fb548a..3f844fe5db1 100644 --- a/raster3d/r3.to.rast/r3.to.rast.md +++ b/raster3d/r3.to.rast/r3.to.rast.md @@ -7,11 +7,8 @@ touched). The user can force *r3.to.rast* to use the 2D resolution of the input 3D raster map for the output maps, independently from the current region settings. - - -| | -|------------------------| -| *How r3.to.rast works* | +![How r3.to.rast works](r3.to.rast.png) +*How r3.to.rast works* ### Map type conversions diff --git a/raster3d/raster3dintro.md b/raster3d/raster3dintro.md index 623b959617f..da91b53c9c9 100644 --- a/raster3d/raster3dintro.md +++ b/raster3d/raster3dintro.md @@ -16,7 +16,7 @@ size of the tiles can be specified at import time with a given import module such as [r3.in.ascii](r3.in.ascii.md) or the data can be retiled using [r3.retile](r3.retile.md) after import or creation. - +![3D raster map coordinate system](raster3d_layout.png) *The 3D raster map coordinate system and the internal tile layout of the RASTER3D library* diff --git a/scripts/i.spectral/i.spectral.md b/scripts/i.spectral/i.spectral.md index 74209910cc3..260c3139ef1 100644 --- a/scripts/i.spectral/i.spectral.md +++ b/scripts/i.spectral/i.spectral.md @@ -18,9 +18,9 @@ i.spectral -g raster=lsat7_2002_10,lsat7_2002_20,lsat7_2002_30,lsat7_2002_40,lsa coordinates=636069,215440,637958,223393,633277,223605 ``` - -Spectral plot of 3 different land cover types: (1) water, (2) green -vegetation, and (3) highway +![Spectral plot of 3 different land cover types](i_spectral.png) +*Spectral plot of 3 different land cover types: (1) water, (2) green +vegetation, and (3) highway* North Carolina sample dataset: diff --git a/scripts/r.in.wms/r.in.wms.md b/scripts/r.in.wms/r.in.wms.md index d38efd862a1..09a3bb3cf45 100644 --- a/scripts/r.in.wms/r.in.wms.md +++ b/scripts/r.in.wms/r.in.wms.md @@ -89,7 +89,7 @@ r.in.wms url="https://tiles.maps.eox.at/wms?" layers=s2cloudless output=sentinel r.info sentinel2 ``` -[](r_in_wms_sentinel2.jpg) +![Raleigh (NC, USA) seen by Sentinel-2](r_in_wms_sentinel2.jpg) *Figure: Raleigh (NC, USA) seen by Sentinel-2 (10m resolution; image courtesy: EOX)* diff --git a/scripts/r.mapcalc.simple/r.mapcalc.simple.md b/scripts/r.mapcalc.simple/r.mapcalc.simple.md index dd0ad328e25..7f307989142 100644 --- a/scripts/r.mapcalc.simple/r.mapcalc.simple.md +++ b/scripts/r.mapcalc.simple/r.mapcalc.simple.md @@ -64,7 +64,7 @@ r.mapcalc.simple expression="A + B + C" a=zeros b=ones c=twos output=result1 r.mapcalc.simple expression="(A * B) / 2 + 3 * C" a=zeros b=ones c=twos output=result2 ``` - +![Figure: r.mapcalc.simple graphical user interface](r_mapcalc_simple.png) *Figure: r.mapcalc.simple graphical user interface* ### Example expressions diff --git a/scripts/r.reclass.area/r.reclass.area.md b/scripts/r.reclass.area/r.reclass.area.md index 7fbd47d986b..a20ff64d596 100644 --- a/scripts/r.reclass.area/r.reclass.area.md +++ b/scripts/r.reclass.area/r.reclass.area.md @@ -24,7 +24,7 @@ r.reclass.area input=zipcodes output=zipcodes_larger2000ha mode=greater value=20 r.report zipcodes_larger2000ha unit=h ``` - +![Figure: r.reclass.area method=reclass](zipcodes_larger2000ha.png) *Figure: r.reclass.area method=reclass* In this example, the ZIP code map in the North Carolina sample dataset @@ -36,7 +36,7 @@ substitutional removing of areas minor of 1000 ha: r.reclass.area input=zipcodes output=zipcodes_minor1000ha mode=lesser value=1000 method=rmarea ``` - +![Figure: r.reclass.area method=rmarea](zipcodes_minor1000ha.png) *Figure: r.reclass.area method=rmarea* ## SEE ALSO diff --git a/vector/v.buffer/v.buffer.md b/vector/v.buffer/v.buffer.md index 10423d41382..f7fc579f944 100644 --- a/vector/v.buffer/v.buffer.md +++ b/vector/v.buffer/v.buffer.md @@ -68,9 +68,9 @@ All examples are based on the North Carolina sample dataset. v.buffer input=roadsmajor output=roadsmajor_buffer type=line distance=100 ``` - -Buffer of 100m along the "roadsmajor" lines (map subset, original center -line shown in black) +![Buffer of 100m along the roadsmajor lines](v_buffer_lines.png) +*Buffer of 100m along the "roadsmajor" lines (map subset, original center +line shown in black)* ### Circles around input points @@ -78,9 +78,9 @@ line shown in black) v.buffer input=hospitals output=hospitals_circled type=point distance=2000 ``` - -Buffer of 2000m around the "hospitals" points (map subset, original -points shown in black, new area centroids in red) +![Buffer of 2000m around the hospitals points](v_buffer_points.png) +*Buffer of 2000m around the "hospitals" points (map subset, original +points shown in black, new area centroids in red)* ### Circles around input points with attribute transfer @@ -100,9 +100,9 @@ v.extract in=hospitals_circled output=hospital_36_circled layer=1 cats=36 -d v.buffer input=lakes output=lakes_buffer type=area distance=100 ``` - -Buffer of 100m around the "lakes" polygons (map subset, original areas -shown in black) +![Buffer of 100m around the "lakes" polygons](v_buffer_areas.png) +*Buffer of 100m around the "lakes" polygons (map subset, original areas +shown in black)* ### Buffer inside input areas @@ -113,9 +113,10 @@ buffer") is generated using a negative **distance** value: v.buffer input=lakes output=lakes_buffer type=area distance=-50 ``` - -Internal buffer of 50m inside the "lakes" polygons (map subset, original -areas shown in black) +![Internal buffer of 50m inside the lakes polygons](v_buffer_areas_int.png) +*Internal buffer of 50m inside the "lakes" polygons (map subset, original +areas shown in black)* + Not all features are buffered, only the polygons that allow creation inside a topological cleaned polygon. diff --git a/vector/v.clean/v.clean.md b/vector/v.clean/v.clean.md index d75a8ec6383..0b205334e7f 100644 --- a/vector/v.clean/v.clean.md +++ b/vector/v.clean/v.clean.md @@ -186,10 +186,8 @@ the tool does. Threshold does not apply, use dummy value if *v.clean* is run with several tools. -| | -|------------------------------------------------| -| | -| *tool=rmsa* | +![v_clean_rmsa](v_clean_rmsa.png) +*tool=rmsa* The *rmsa* tool should be followed by *break,rmdupl*. The *rmsa* tool followed by *break,rmdupl* may need to be run more than once to remove diff --git a/vector/v.delaunay/v.delaunay.md b/vector/v.delaunay/v.delaunay.md index a17605757a2..c5214fa77f1 100644 --- a/vector/v.delaunay/v.delaunay.md +++ b/vector/v.delaunay/v.delaunay.md @@ -6,7 +6,7 @@ Delaunay triangulation vector map (**output**). Delaunay triangulation example (red-yellow points are the data points from which the triangulation was generated): - +![v_delaunay](v_delaunay.png) ## EXAMPLE diff --git a/vector/v.hull/v.hull.md b/vector/v.hull/v.hull.md index a70c9806add..f84cec3112d 100644 --- a/vector/v.hull/v.hull.md +++ b/vector/v.hull/v.hull.md @@ -10,8 +10,8 @@ In the case of 3D input points, the hull will be a 3D hull as well, unless the user specifies the **-f** flag. The 3D hull will be composed of triangular faces. - -Fig: Convex hull polygon created with *v.hull* +![Convex hull polygon](v_hull.png) +*Fig: Convex hull polygon created with v.hull* ## NOTES @@ -43,8 +43,8 @@ d.vect random3d_b color=red # 3D view in wxGUI (g.gui) ``` - -Fig: Convex hull in 3D from 3D points created with *v.hull* +![Convex hull in 3D](v_hull_3d.png) +*Fig: Convex hull in 3D from 3D points created with v.hull* ## REFERENCES diff --git a/vector/v.label/v.label.md b/vector/v.label/v.label.md index 4d53aaa4f17..b49bfaf3b4a 100644 --- a/vector/v.label/v.label.md +++ b/vector/v.label/v.label.md @@ -75,7 +75,7 @@ vertical height of the letters in meters on the ground. Thus text will grow or shrink depending on the scale at which the map is drawn. Alternatively *fontsize* can set the font size in normal font points. -**TEXT COLOR**: +**TEXT COLOR**: This selects the text color. If unspecified, the label's text is drawn in *black*, by default. The text color can be specified in one of several ways: diff --git a/vector/v.random/v.random.md b/vector/v.random/v.random.md index 3783560808c..71f5e40a6c4 100644 --- a/vector/v.random/v.random.md +++ b/vector/v.random/v.random.md @@ -101,8 +101,8 @@ population standard deviation: 3563.95 skewness: 0.34703 ``` - -Random points with different X, Y, and Z coordinates +![Random points with different X, Y, and Z coordinates](vrandom_z.png) +*Random points with different X, Y, and Z coordinates* ### Generating random points in selected areas @@ -139,8 +139,8 @@ d.mon wx0 d.vect randareas6k -c ``` - -Random adjacent areas from random points (here: used as centroids) +![Random adjacent areas from random points](vrandom_polygons.png) +*Random adjacent areas from random points (here: used as centroids)* To eventually obtain isolated areas, selected areas can be extracted with *[v.extract](v.extract.md)*. @@ -207,9 +207,8 @@ cat|landclass96_cat|landclass96_label ... ``` - -Random points only sampled in forested areas (stratified random -sampling) +![Random points only sampled in forested areas](vrandom_restricted_attr.png) +*Random points only sampled in forested areas (stratified random sampling)* ### Stratified random sampling: Random sampling from vector map with spatial constraints @@ -222,9 +221,9 @@ r.to.vect -v input=landclass96 output=landclass96 type=area v.random restrict=landclass96 output=random_samples npoints=2 where="label = 'water'" layer=1 -a ``` - -Two random points sampled in each individual water body (stratified -random sampling) +![Two random points sampled in each individual water body](vrandom_restricted_area.png) +*Two random points sampled in each individual water body (stratified +random sampling)* ## SEE ALSO diff --git a/vector/v.surf.rst/v.surf.rst.md b/vector/v.surf.rst/v.surf.rst.md index 2732da7df3f..a2b714898d0 100644 --- a/vector/v.surf.rst/v.surf.rst.md +++ b/vector/v.surf.rst/v.surf.rst.md @@ -13,8 +13,8 @@ steepest slope), tangential curvature (measured in the direction of a tangent to contour line) or mean curvature are computed and saved as raster maps specified by the options **slope, aspect, pcurv, tcurv, mcurv** respectively. If **-d** flag is set, *v.surf.rst* outputs -partial derivatives fx,fy,fxx, -fyy,fxy instead of slope, aspect, profile, +partial derivatives *f_x*, *f_y*, *f_xx*, +*f_yy*, *f_xy* instead of slope, aspect, profile, tangential and mean curvatures respectively. If the input vector map have time stamp, the program creates time stamp for all output maps. diff --git a/vector/v.to.rast3/v.to.rast3.md b/vector/v.to.rast3/v.to.rast3.md index ea970c4279f..80bfc19ee85 100644 --- a/vector/v.to.rast3/v.to.rast3.md +++ b/vector/v.to.rast3/v.to.rast3.md @@ -10,11 +10,8 @@ point is converted into a single 3D raster cell (voxel) representing the location of the vector point. As 3D raster cell value the database attribute of the vector point is stored with floating point precision. - - -| | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| *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.* | +![Result of the v.to.rast3 test](v_to_rast3_test.png) +*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.* ## SEE ALSO diff --git a/vector/v.voronoi/v.voronoi.md b/vector/v.voronoi/v.voronoi.md index ecf7a4f079d..64c114349fe 100644 --- a/vector/v.voronoi/v.voronoi.md +++ b/vector/v.voronoi/v.voronoi.md @@ -44,7 +44,7 @@ v.voronoi input=hospitals output=hospitals_voronoi Result: - +![Voronoi diagram for hospitals in North Carolina](v_voronoi_points.png) *Voronoi diagram for hospitals in North Carolina* ### Voronoi diagram for areas @@ -58,7 +58,7 @@ v.voronoi input=urbanarea output=urbanarea_voronoi -a Result: - +![Voronoi diagram for urban areas in North Carolina](v_voronoi_areas.png) *Voronoi diagram for urban areas in North Carolina* ### Skeletons and center lines of areas @@ -73,9 +73,8 @@ v.voronoi input=urbanarea output=urbanarea_skeleton -s thin=2000 Result: - -*Skeleton (blue) and center line (red) for urban areas in North -Carolina* +![Skeleton and center line for urban areas in North Carolina](v_voronoi_skeleton.png) +*Skeleton (blue) and center line (red) for urban areas in North Carolina* ## REFERENCES