diff --git a/.markdownlint.yml b/.markdownlint.yml index 3e87a7f9dfe..7adf1fd7227 100644 --- a/.markdownlint.yml +++ b/.markdownlint.yml @@ -8,30 +8,13 @@ fix: true MD041: false # first-line-h1 # Errors from .html to .md rename (first step in HTML to Markdown conversion) -MD001: false # heading-increment -MD003: false # heading-style -MD004: false # ul-style -MD007: false # ul-indent -MD009: false # no-trailing-spaces -MD010: false # no-hard-tabs -MD011: false # no-reversed-links -MD012: false # no-multiple-blanks -MD013: false # line-length -MD018: false # no-missing-space-atx -MD019: false # no-multiple-space-atx -MD020: false # no-missing-space-closed-atx -MD022: false # blanks-around-headings -MD023: false # heading-start-left -MD024: false # no-duplicate-heading -MD026: false # no-trailing-punctuation -MD029: false # ol-prefix -MD032: false # blanks-around-lists -MD033: false # no-inline-html -MD034: false # no-bare-urls -MD037: false # no-space-in-emphasis -MD045: false # no-alt-text -MD049: false # emphasis-style -MD052: false # reference-links-images -MD055: false # table-pipe-style -MD058: false # blanks-around-tables +no-duplicate-heading: false +heading-increment: false +no-inline-html: false +no-alt-text: false +line-length: false # The block above this is to be eventually removed. + +no-emphasis-as-heading: false +link-fragments: false +no-space-in-links: false diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 147a34e82db..f327d257fb0 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -9,6 +9,7 @@ repos: exclude: | (?x)^( configure$| + .*\.md$| .*\.ascii$| .*\.asc$| .*\.ref$| diff --git a/db/db.describe/db.describe.md b/db/db.describe/db.describe.md index f13bec90cd0..8015e713daf 100644 --- a/db/db.describe/db.describe.md +++ b/db/db.describe/db.describe.md @@ -34,6 +34,7 @@ Column 2: OBJECTID:INTEGER:11 Column 3: AREA:DOUBLE PRECISION:20 [...] ``` + ```sh db.describe table=hospitals database='$GISDBASE/$LOCATION_NAME/PERMANENT/dbf/' \ driver=dbf @@ -66,6 +67,7 @@ type:INTEGER ```sh db.describe table=hospitals format=json ``` + ```sh { "table": "hospitals", diff --git a/display/d.graph/d.graph.md b/display/d.graph/d.graph.md index a97b339c9c0..9b47ce9abc8 100644 --- a/display/d.graph/d.graph.md +++ b/display/d.graph/d.graph.md @@ -132,7 +132,7 @@ A dynamic example can be found in the *d.polar* shell script. echo "symbol basic/star 20 2264417 5413182 black red" | d.graph -m ``` -### Split the screen into quadrants: +### Split the screen into quadrants ```sh d.frame -s full_screen diff --git a/display/d.linegraph/d.linegraph.md b/display/d.linegraph/d.linegraph.md index eab91bc12b6..5ff63568d36 100644 --- a/display/d.linegraph/d.linegraph.md +++ b/display/d.linegraph/d.linegraph.md @@ -84,6 +84,7 @@ use of underscores is not recommended and there is no need to use it at all in the GUI or when using *d.linegraph* in Python scripts. The way the program locates and labels tic marks is less than perfect: + 1) although distances between Y tics are proportional to the value, they are not proportional on the X axis; 2) decimal values between -1 and 1 can be printed on the X axis, but not diff --git a/display/d.text/d.text.md b/display/d.text/d.text.md index f19185202b9..3f53002c20a 100644 --- a/display/d.text/d.text.md +++ b/display/d.text/d.text.md @@ -9,7 +9,7 @@ angle, and boldness can be adjusted with commands in the standard input and then assigns values to these options on lines within the standard input). -### Commands: +### Commands **.C** *color* (where *color* is one of the available colors) causes text appearing on diff --git a/general/g.list/g.list.md b/general/g.list/g.list.md index 0053aa6a2ee..218d0049db1 100644 --- a/general/g.list/g.list.md +++ b/general/g.list/g.list.md @@ -208,5 +208,5 @@ of their region. ## AUTHOR Huidae Cho -grass4u@gmail.com + based on general/manage/cmd/list.c by Michael Shapiro diff --git a/general/g.parser/g.parser.md b/general/g.parser/g.parser.md index bdf12e0dd90..f1da65d3fe8 100644 --- a/general/g.parser/g.parser.md +++ b/general/g.parser/g.parser.md @@ -9,7 +9,7 @@ **g.parser** \[-**s**\] \[-**t**\] \[-**n**\] *filename* \[*argument*,...\] -### Flags: +### Flags **-t** Print strings for translation diff --git a/general/g.region/g.region.md b/general/g.region/g.region.md index b0772553b45..54fb7b4a2b7 100644 --- a/general/g.region/g.region.md +++ b/general/g.region/g.region.md @@ -99,7 +99,7 @@ specified. Flag **-o** was added in GRASS GIS version 8 to simulate *g.region* behavior in prior versions when current region file was always updated unless **-u** was specified. -### Additional parameter information: +### Additional parameter information **zoom=***name* Shrink current region settings to the smallest region encompassing all @@ -340,6 +340,7 @@ coordinate reference system since it is reprojected on the fly. ```sh g.region -p format=json ``` + ```sh { "projection": "99 (Lambert Conformal Conic)", @@ -368,9 +369,11 @@ g.region -p format=json "cells3": 2526500 } ``` + ```sh g.region -l format=json ``` + ```sh { "nw_long": -78.688888505507336, diff --git a/general/g.remove/g.remove.md b/general/g.remove/g.remove.md index 91b7a575498..603f9a0f84a 100644 --- a/general/g.remove/g.remove.md +++ b/general/g.remove/g.remove.md @@ -34,4 +34,4 @@ g.remove -f type=vector pattern="stream_*" exclude="*_final" ## AUTHOR Huidae Cho -grass4u@gmail.com + diff --git a/gui/wxpython/animation/g.gui.animation.md b/gui/wxpython/animation/g.gui.animation.md index 23df1565348..c97c94d8b29 100644 --- a/gui/wxpython/animation/g.gui.animation.md +++ b/gui/wxpython/animation/g.gui.animation.md @@ -36,11 +36,9 @@ follow these steps: - choose parameter (parameter of *[m.nviz.image](m.nviz.image.md)*) to animate (e.g. color_map) - Animation Tool screenshot - ## NOTE The Animation Tool follows the computational region settings, so please diff --git a/gui/wxpython/docs/wxGUI.iscatt.md b/gui/wxpython/docs/wxGUI.iscatt.md index d99cce16882..e1d8d6961cb 100644 --- a/gui/wxpython/docs/wxGUI.iscatt.md +++ b/gui/wxpython/docs/wxGUI.iscatt.md @@ -26,11 +26,9 @@ interactivity, which allows user to: ## TOOL CONTROLS LAYOUT - Interactive Scatter Plot Tool - 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 diff --git a/gui/wxpython/docs/wxGUI.md b/gui/wxpython/docs/wxGUI.md index b3d80fc998f..791f19cec5c 100644 --- a/gui/wxpython/docs/wxGUI.md +++ b/gui/wxpython/docs/wxGUI.md @@ -30,7 +30,6 @@ menu bar with a set of pull-down menus for all GRASS GIS functions (analysis, file I/O, GIS configuration and management); on a Mac, the GRASS functions menu is at the top of the screen. - screenshot Figure: Layer Manager screenshot on Ubuntu @@ -241,7 +240,6 @@ from the window, a map canvas where a map composition of one or more layers is displayed, and a statusbar with information about the geographic region of the maps displayed. - ![Map Display Window](wxGUI_map_display.jpg) Figure: Map Display screenshot on Ubuntu diff --git a/gui/wxpython/docs/wxGUI.nviz.md b/gui/wxpython/docs/wxGUI.nviz.md index 364cce154a6..df79df28833 100644 --- a/gui/wxpython/docs/wxGUI.nviz.md +++ b/gui/wxpython/docs/wxGUI.nviz.md @@ -37,10 +37,8 @@ display mode. ## 3D View Toolbar - toolbar - ![icon](icons/script-save.png)  *Generate command for m.nviz.image* Generate command for m.nviz.image based on current state. @@ -80,10 +78,8 @@ panel (following label *Look:*): - *top* moves the current eye position above the map center. - *reset* returns all current view settings to their default values. - toolbox - You can adjust the viewer's height above the scene, perspective and twist value to rotate the scene about the horizontal axis. An angle of 0 is flat. The scene rotates between -90 and 90 degrees. @@ -162,10 +158,8 @@ In the very bottom part of the panel position of surface can be set. To move the surface right (looking from the south) choose *X* axis and set some positive value. To reset the surface position press *Reset* button. - toolbox - #### Constant surface It is possible to add constant surface and set its properties like fine @@ -208,10 +202,8 @@ Currently are implemented these markers: Thematic mapping can be used to determine marker color and size (and line color and width). - toolbox - #### 3D rasters 3D raster maps (volumes, voxel models) can be displayed either as @@ -253,10 +245,8 @@ attributes. 3D rasters can be moved the same way like surfaces do. - toolbox - ### Analysis *Analysis* tab contains *Cutting planes* panel. @@ -289,10 +279,8 @@ light color, brightness and ambient. Light position is controlled similarly to eye position. If option *Show light model* is enabled light model is displayed to visualize the light settings. - toolbox - The *Fringe* panel allows you to draw fringes in different directions (North & East, South & East, South & West, North & West). It is possible to set the fringe color and height of the bottom edge. diff --git a/gui/wxpython/docs/wxGUI.toolboxes.md b/gui/wxpython/docs/wxGUI.toolboxes.md index b51d8d7a006..b912958d2a4 100644 --- a/gui/wxpython/docs/wxGUI.toolboxes.md +++ b/gui/wxpython/docs/wxGUI.toolboxes.md @@ -177,11 +177,9 @@ 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: - Toolboxes - menu customization - ## NOTES After the first start of wxGUI with custom toolboxes, `.grass/toolboxes` diff --git a/gui/wxpython/gcp/g.gui.gcp.md b/gui/wxpython/gcp/g.gui.gcp.md index 892b495f4eb..73c40520087 100644 --- a/gui/wxpython/gcp/g.gui.gcp.md +++ b/gui/wxpython/gcp/g.gui.gcp.md @@ -27,10 +27,8 @@ The GCP Manager is structured into three panels: ### Components of the GCP Manager - GCP Manager - *Toolbars* Two toolbars are provided with the GCP Manager, one for managing the map @@ -114,7 +112,6 @@ display region extents (both size and location of area displayed). Source and target display are adjusted by using the current GCPs for coordinate transformation: - *Adjust source display to target display* The extents of the source display are adjusted to the current extents of the target display. @@ -140,11 +137,9 @@ canvas (source or target). ![icon](icons/settings.png)  *Settings* Shows a settings dialog for GCP management and display: - *Symbology* Settings for map and GCP display: - *Highlight highest RMS error only* Only the GCP with the highest RMS error will be displayed in a different colour, both in the list of GCPs and the GCP Map Display. @@ -185,11 +180,9 @@ Select a source map for the left pane of the GCP Map Display. *Select target map to display* Select a target map for the right pane of the GCP Map Display. - *Rectification* Settings for georectification: - *Select rectification method* Set the polynomial order for georectification. This order will also be used for RMS error calculation. @@ -202,8 +195,6 @@ project when georectifying. Change the extension for output map names when doing the actual georectification. - - ![icon](icons/help.png)  *Show Help* Show help page for the GCP Manager. diff --git a/gui/wxpython/gmodeler/g.gui.gmodeler.md b/gui/wxpython/gmodeler/g.gui.gmodeler.md index 1a057ea5d7b..cc5e0e9dce1 100644 --- a/gui/wxpython/gmodeler/g.gui.gmodeler.md +++ b/gui/wxpython/gmodeler/g.gui.gmodeler.md @@ -197,8 +197,6 @@ window with *Save* and *Run* option are shown in the figures below. [](g_gui_gmodeler_model_avg.png) *Figure: A model to perform average statistics for zipcode zones.* - - [](g_gui_gmodeler_items.png) [](g_gui_gmodeler_python.png) @@ -255,8 +253,6 @@ set in the module dialog as input called `%raster`. [](g_gui_gmodeler_variables.png) *Figure: Example of raster file variable settings.* - - [](g_gui_gmodeler_variables_raster.png) *Figure: Example of raster file variable usage.* diff --git a/gui/wxpython/iclass/g.gui.iclass.md b/gui/wxpython/iclass/g.gui.iclass.md index 4647b18e928..14ba64bef50 100644 --- a/gui/wxpython/iclass/g.gui.iclass.md +++ b/gui/wxpython/iclass/g.gui.iclass.md @@ -28,11 +28,9 @@ supervised classification* or via command line as *g.gui.iclass*. - import vector map - export vector map with attribute table - Supervised Classification Tool - *wxIClass* performs the first pass in the GRASS two-pass supervised image classification process; the GRASS module *[i.maxlik](i.maxlik.md)* executes the second pass. Both programs must be run to generate a diff --git a/gui/wxpython/image2target/g.gui.image2target.md b/gui/wxpython/image2target/g.gui.image2target.md index eba981c13aa..30ed56a0766 100644 --- a/gui/wxpython/image2target/g.gui.image2target.md +++ b/gui/wxpython/image2target/g.gui.image2target.md @@ -27,10 +27,8 @@ The GCP Manager is structured into three panels: ### Components of the GCP Manager - GCP Manager - *Toolbars* Two toolbars are provided with the GCP Manager, one for managing the map @@ -114,7 +112,6 @@ display region extents (both size and location of area displayed). Source and target display are adjusted by using the current GCPs for coordinate transformation: - *Adjust source display to target display* The extents of the source display are adjusted to the current extents of the target display. @@ -140,11 +137,9 @@ canvas (source or target). ![icon](icons/settings.png)  *Settings* Shows a settings dialog for GCP management and display: - *Symbology* Settings for map and GCP display: - *Highlight highest RMS error only* Only the GCP with the highest RMS error will be displayed in a different colour, both in the list of GCPs and the GCP Map Display. @@ -185,11 +180,9 @@ Select a source map for the left pane of the GCP Map Display. *Select target map to display* Select a target map for the right pane of the GCP Map Display. - *Rectification* Settings for georectification: - *Select rectification method* Set the polynomial order for georectification. This order will also be used for RMS error calculation. @@ -202,8 +195,6 @@ project when georectifying. Change the extension for output map names when doing the actual georectification. - - ![icon](icons/help.png)  *Show Help* Show help page for the GCP Manager. diff --git a/gui/wxpython/mapswipe/g.gui.mapswipe.md b/gui/wxpython/mapswipe/g.gui.mapswipe.md index e8e05d1781a..c6667738360 100644 --- a/gui/wxpython/mapswipe/g.gui.mapswipe.md +++ b/gui/wxpython/mapswipe/g.gui.mapswipe.md @@ -21,7 +21,6 @@ Map Swipe allows you to: - change the appearance of cursor in 'mirror' mode (available in Map Swipe settings) - Map swipe screenshot Pre and post disaster images of the tsunami in Japan in 2011. The upper diff --git a/gui/wxpython/psmap/g.gui.psmap.md b/gui/wxpython/psmap/g.gui.psmap.md index 6a664ffa6e9..29b0b265a7d 100644 --- a/gui/wxpython/psmap/g.gui.psmap.md +++ b/gui/wxpython/psmap/g.gui.psmap.md @@ -16,11 +16,9 @@ Possible output files: - PostScript/EPS file - PDF (using ps2pdf) - wxGUI Cartographic Composer - Cartographic Composer enables to load in saved instructions file. Loading instruction files created by Cartographic Composer is more robust, as opposed to loading files created manually. diff --git a/gui/wxpython/rdigit/g.gui.rdigit.md b/gui/wxpython/rdigit/g.gui.rdigit.md index c07797d8331..89f87a2517d 100644 --- a/gui/wxpython/rdigit/g.gui.rdigit.md +++ b/gui/wxpython/rdigit/g.gui.rdigit.md @@ -21,18 +21,18 @@ the Map Display toolbar (from the combo box on the right). The typical workflow includes these steps: -1. Set computational region as needed. -2. Switch to Raster Digitizer and select a map to create. Select either +1. Set computational region as needed. +2. Switch to Raster Digitizer and select a map to create. Select either a new raster or create a new raster from existing raster, also select raster type (CELL, FCELL, DCELL) -3. Specify category value and width *before* drawing a feature -4. Specify digitizing tool (area, line, point) -5. Start digitizing and when you want to finish area or line, *use +3. Specify category value and width *before* drawing a feature +4. Specify digitizing tool (area, line, point) +5. Start digitizing and when you want to finish area or line, *use right click* -6. Change color of temporary overlay depending on your needs -7. Set different category and repeat -8. At any point you can use *Undo* or *Save* -9. If existing raster is used for the new raster, digitized areas will +6. Change color of temporary overlay depending on your needs +7. Set different category and repeat +8. At any point you can use *Undo* or *Save* +9. If existing raster is used for the new raster, digitized areas will respect the color table, but you can always set different color table. diff --git a/gui/wxpython/rlisetup/g.gui.rlisetup.md b/gui/wxpython/rlisetup/g.gui.rlisetup.md index d6622fb63de..6a9d7ae33a1 100644 --- a/gui/wxpython/rlisetup/g.gui.rlisetup.md +++ b/gui/wxpython/rlisetup/g.gui.rlisetup.md @@ -38,7 +38,7 @@ The startup window shows your configuration files, you can: **TODO: description below needs further updates** -1. ***View/Edit*** (Load a file) from the shown list: the configuration +1. ***View/Edit*** (Load a file) from the shown list: the configuration is shown in a small text editor window. 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 @@ -49,16 +49,16 @@ The startup window shows your configuration files, you can: `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. -2. ***Create*** a new configuration file: used for creating a new +2. ***Create*** a new configuration file: used for creating a new configuration file in an interactive way, in three steps: - 1. Choose file name and maps to use for setting: + 1. Choose file name and maps to use for setting: - *Name for new configuration file*(required): the name of new configuration file - *Raster map name to use to select areas* (required): the name of raster map used for selecting sampling areas - *Vector map to overlay* (optional): name of a vector map used for selecting sampling areas - 2. Set the sampling frame. The sample frame is a rectangular area + 2. Set the sampling frame. The sample frame is a rectangular area which contains all the areas to analyze. It can be defined in three ways: - *Whole map layer*: the sample frame is the whole map @@ -67,7 +67,7 @@ The startup window shows your configuration files, you can: and columns. - *Draw the sample frame*: the user draws the sample frame on map using mouse. - 3. Set the sample areas. The sample areas are simply the areas to + 3. Set the sample areas. The sample areas are simply the areas to analyze. They can be defined in five ways (see the picture below): - *Whole map layer*: the sample area is the whole sample frame @@ -107,10 +107,10 @@ The startup window shows your configuration files, you can: can be used only with the specified raster map, and the procedure can be used only if whole map layer is selected as sampling frame. -3. ***Remove a file*** the selected file is deleted from the available +3. ***Remove a file*** the selected file is deleted from the available configuration files. -4. ***Help***: open this help text. -5. ***Close*** module window. +4. ***Help***: open this help text. +5. ***Close*** module window. ## NOTES diff --git a/gui/wxpython/vdigit/g.gui.vdigit.md b/gui/wxpython/vdigit/g.gui.vdigit.md index e56dd982009..ecf5d445002 100644 --- a/gui/wxpython/vdigit/g.gui.vdigit.md +++ b/gui/wxpython/vdigit/g.gui.vdigit.md @@ -64,11 +64,9 @@ given threshold to the features from the background map. ### DIGITIZER TOOLBAR - Vector Digitizer Toolbar - ![icon](icons/point-create.png)  *Digitize new point* Add new point to vector map and optionally define its attributes (Ctrl+P). @@ -127,6 +125,7 @@ settings) (Ctrl+K). Attributes can be also modified. Same functionality is accessible from Main toolbar "Query vector map (editable mode)". ![icon](icons/tools.png)  *Additional tools* + - *Break selected lines/boundaries at intersection* Split given vector line or boundary into two lines on given position (based on *[v.clean](v.clean.md)*, `tool=break`). diff --git a/imagery/i.atcorr/i.atcorr.md b/imagery/i.atcorr/i.atcorr.md index 85e6e6f1d3f..41e060942c0 100644 --- a/imagery/i.atcorr/i.atcorr.md +++ b/imagery/i.atcorr/i.atcorr.md @@ -432,10 +432,9 @@ Target altitude (xps, in negative \[km\]): > otherwise xps expresses the altitude of the target (e.g., mean > elevation) in \[km\], given as negative value - Sensor platform (xpp, in negative \[km\] or -1000): -> +> > xpp = -1000 means that the sensor is on board a satellite. > xpp = 0 means that the sensor is at the ground level. > -100 \< xpp \< 0 defines the altitude of the sensor expressed in @@ -764,14 +763,13 @@ following information: - sensor height and, - sensor band. -1. *Geometrical conditions* +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). Our scene comes from the Sentinel-2A mission (the file name begins with S2A\_...). - -2. *Day, time, longitude and latitude of measurement* +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`), @@ -794,21 +792,18 @@ following information: 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`. - -3. *Atmospheric model* +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`. - -4. *Aerosol model* +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`. - -5. *Visibility or Aerosol Optical Depth* +5. *Visibility or Aerosol Optical Depth* For Sentinel-2 scenes, the visibility is not measured, and therefore we have to estimate the aerosol optical depth instead, e.g. from [AERONET](https://aeronet.gsfc.nasa.gov). With a bit of luck, you @@ -816,9 +811,8 @@ following information: Optical Depth at 500 nm at the same time as the scene was taken. In our case, on 28th October 2016, the *EPA-Res_Triangle_Pk* station measured AOD = 0.07 (approximately). - -6. *Mean target elevation above sea level* +6. *Mean target elevation above sea level* Mean target elevation above sea level refers to the mean elevation of the computational region. You can estimate it from the digital @@ -830,14 +824,12 @@ following information: 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`. - -7. *Sensor height* +7. *Sensor height* Since the sensor is on board a satellite, the sensor height will be set to `-1000`. - -8. *Sensor band* +8. *Sensor band* The overview of satellite bands can be found in table F (see above). For Sentinel-2A, the band numbers span from 166 to 178, and for diff --git a/imagery/i.cca/i.cca.md b/imagery/i.cca/i.cca.md index f28e21a0769..a36bdea1ac4 100644 --- a/imagery/i.cca/i.cca.md +++ b/imagery/i.cca/i.cca.md @@ -18,7 +18,7 @@ were used to collect the signatures. The output raster map names are built by appending a ".1", ".2", etc. to the output raster map name specified on the command line. -### Parameters: +### Parameters **group=***name* Name of the [imagery](i.group.md) group to which the raster band files diff --git a/imagery/i.cluster/i.cluster.md b/imagery/i.cluster/i.cluster.md index ec6d27d9baf..2169d29c185 100644 --- a/imagery/i.cluster/i.cluster.md +++ b/imagery/i.cluster/i.cluster.md @@ -58,7 +58,7 @@ consist of same raster bands (semantic labels match). If semantic labels are not set, it will be possible to use obtained signature file to classify only the same imagery group used for generating signatures. -### Parameters: +### Parameters **group=***name* The name of the group file which contains the imagery files that the diff --git a/imagery/i.evapo.pm/i.evapo.pm.md b/imagery/i.evapo.pm/i.evapo.pm.md index 52fded1703e..d0512214345 100644 --- a/imagery/i.evapo.pm/i.evapo.pm.md +++ b/imagery/i.evapo.pm/i.evapo.pm.md @@ -75,7 +75,7 @@ science for the Southern Switzerland) Original version of program: The [HydroFOSS](http://istgis.ist.supsi.ch:8001/geomatica/index.php?id=1) project, 2006, IST-SUPSI. -(http://istgis.ist.supsi.ch:8001/geomatica/index.php?id=1) *Massimiliano +() *Massimiliano Cannata, Scuola Universitaria Professionale della Svizzera Italiana - Istituto Scienze della Terra* *Maria A. Brovelli, Politecnico di Milano - Polo regionale di Como* diff --git a/imagery/i.evapo.time/i.evapo.time.md b/imagery/i.evapo.time/i.evapo.time.md index a548415d390..873cec49965 100644 --- a/imagery/i.evapo.time/i.evapo.time.md +++ b/imagery/i.evapo.time/i.evapo.time.md @@ -11,10 +11,10 @@ stations dataset. Inputs: Method: -1. each ETa pixel is divided by the same day ETo and become ETrF -2. each ETrF pixel is multiplied by the ETo sum for the representative +1. each ETa pixel is divided by the same day ETo and become ETrF +2. each ETrF pixel is multiplied by the ETo sum for the representative days -3. Sum all n temporal \[ETrF\*ETo_sum\] pixels to make a summed(ET) in +3. Sum all n temporal \[ETrF\*ETo_sum\] pixels to make a summed(ET) in \[DOYmin;DOYmax\] representative days calculation: let assume i belongs to range diff --git a/imagery/i.ortho.photo/i.ortho.photo/i.ortho.photo.md b/imagery/i.ortho.photo/i.ortho.photo/i.ortho.photo.md index 6027fea079b..eae184a99cb 100644 --- a/imagery/i.ortho.photo/i.ortho.photo/i.ortho.photo.md +++ b/imagery/i.ortho.photo/i.ortho.photo/i.ortho.photo.md @@ -9,22 +9,22 @@ maps in a single imagery group. Alternatively, all the steps can be performed separately by running the appropriate modules. - *Initialization Options* - 1. Create/Modify imagery group to be orthorectified: + 1. Create/Modify imagery group to be orthorectified: [i.group](i.group.md) - 2. Select/Modify target project (formerly known as location) and + 2. Select/Modify target project (formerly known as location) and mapset for orthorectification: [i.ortho.target](i.ortho.target.md) - 3. Select/Modify target elevation model used for orthorectification: + 3. Select/Modify target elevation model used for orthorectification: [i.ortho.elev](i.ortho.elev.md) - 4. Create/Modify camera file of imagery group: + 4. Create/Modify camera file of imagery group: [i.ortho.camera](i.ortho.camera.md) - *Transformation Parameters Computation* - 1. Compute image-to-photo transformation: + 1. Compute image-to-photo transformation: [g.gui.photo2image](g.gui.photo2image.md) - 2. Initialize parameters of camera: [i.ortho.init](i.ortho.init.md) - 3. Compute ortho-rectification parameters from ground control points: + 2. Initialize parameters of camera: [i.ortho.init](i.ortho.init.md) + 3. Compute ortho-rectification parameters from ground control points: [g.gui.image2target](g.gui.image2target.md) - *Ortho-rectification* - 1. Ortho-rectify imagery group: [i.ortho.rectify](i.ortho.rectify.md) + 1. Ortho-rectify imagery group: [i.ortho.rectify](i.ortho.rectify.md) The ortho-rectification procedure in GRASS GIS places the image pixels on the surface of the earth by matching the coordinate system of the @@ -65,7 +65,7 @@ coordinate system (e.g. ETRS33). The steps to follow are described below: -1. *Create/Modify imagery group to be orthorectified: +1. *Create/Modify imagery group to be orthorectified: [i.group](i.group.md)* This step is to be run in the **source project**. @@ -85,7 +85,7 @@ The steps to follow are described below: IMG_0022 source_mapset ``` -2. *Select/Modify target project and mapset for orthorectification: +2. *Select/Modify target project and mapset for orthorectification: [i.ortho.target](i.ortho.target.md)* This step is to be run in the **source project**. @@ -103,7 +103,7 @@ The steps to follow are described below: target_mapset ``` -3. *Select/Modify target elevation model used for orthorectification: +3. *Select/Modify target elevation model used for orthorectification: [i.ortho.elev](i.ortho.elev.md)* This step is to be run in the **source project**. @@ -130,7 +130,7 @@ The steps to follow are described below: no data values :(null) ``` -4. *Create/Modify camera file of imagery group: +4. *Create/Modify camera file of imagery group: [i.ortho.camera](i.ortho.camera.md)* This step is to be run in the **source project**. @@ -160,7 +160,7 @@ The steps to follow are described below: 3 0 -7.7 ``` -5. *Compute image-to-photo transformation: +5. *Compute image-to-photo transformation: [g.gui.photo2image](g.gui.photo2image.md)* This step is to be run in the **source project**. @@ -192,7 +192,7 @@ The steps to follow are described below: height="636" alt="i.ortho.photo example" />](i_ortho_photo_step5.png) *Step 5: Image-to-photo transformation of an oblique image* -6. *Initialize parameters of camera: [i.ortho.init](i.ortho.init.md)* +6. *Initialize parameters of camera: [i.ortho.init](i.ortho.init.md)* This step is to be run in the **source project**. @@ -233,7 +233,7 @@ The steps to follow are described below: STATUS (1=OK, 0=NOT OK) 0 ``` -7. *Compute ortho-rectification parameters from ground control points: +7. *Compute ortho-rectification parameters from ground control points: [g.gui.image2target](g.gui.image2target.md)* This step is to be run in the **target project**. @@ -270,7 +270,7 @@ The steps to follow are described below: *Step 7: Detail of ground control points matching in an oblique image and terrain model* -8. *Ortho-rectify imagery group: [i.ortho.rectify](i.ortho.rectify.md)* +8. *Ortho-rectify imagery group: [i.ortho.rectify](i.ortho.rectify.md)* This step is to be run in the **source project**. diff --git a/imagery/i.rectify/i.rectify.md b/imagery/i.rectify/i.rectify.md index dfb83a3269c..1e8a3bae70d 100644 --- a/imagery/i.rectify/i.rectify.md +++ b/imagery/i.rectify/i.rectify.md @@ -163,7 +163,7 @@ manual](https://grass.osgeo.org/gdp/imagery/grass4_image_processing.pdf)* William R. Enslin, Michigan State University, Center for Remote Sensing Modified for GRASS 5.0 by: -Luca Palmeri (palmeri@ux1.unipd.it) +Luca Palmeri () Bill Hughes -Pierre de Mouveaux (pmx@audiovu.com) +Pierre de Mouveaux () CMD mode by Bob Covill diff --git a/imagery/i.segment/i.segment.md b/imagery/i.segment/i.segment.md index 0bf710885d4..ff32b890603 100644 --- a/imagery/i.segment/i.segment.md +++ b/imagery/i.segment/i.segment.md @@ -23,9 +23,9 @@ in the raster map. The similarity between the current segment and each of its neighbors is calculated according to the given distance formula. Segments will be merged if they meet a number of criteria, including: -1. The pair is mutually most similar to each other (the similarity +1. The pair is mutually most similar to each other (the similarity distance will be smaller than to any other neighbor), and -2. The similarity must be lower than the input threshold. The process +2. The similarity must be lower than the input threshold. The process is repeated until no merges are made during a complete pass. #### Similarity and Threshold diff --git a/imagery/i.smap/i.smap.md b/imagery/i.smap/i.smap.md index d9b7ac8070e..c4b9fdf74ce 100644 --- a/imagery/i.smap/i.smap.md +++ b/imagery/i.smap/i.smap.md @@ -20,13 +20,13 @@ somewhat less computation. This mode is selected with the **-m** flag ## OPTIONS -### Flags: +### Flags **-m** Use maximum likelihood estimation (instead of smap). Normal operation is to use SMAP estimation (see NOTES below). -### Parameters: +### Parameters **group=***name* imagery group diff --git a/imagery/i.svm.predict/i.svm.predict.md b/imagery/i.svm.predict/i.svm.predict.md index 6ffd03c6ede..ab172c641e8 100644 --- a/imagery/i.svm.predict/i.svm.predict.md +++ b/imagery/i.svm.predict/i.svm.predict.md @@ -59,7 +59,7 @@ Please cite both - LIBSVM and i.svm. - For i.svm.\* modules: Nartiss, M., & Melniks, R. (2023). Improving pixel-­based classification of GRASS GIS with support vector machine. Transactions - in GIS, 00, 1–16. https://doi.org/10.1111/tgis.13102 + in GIS, 00, 1–16. - For LIBSVM: Chang, C.-C., & Lin, C.-J. (2011). LIBSVM : a library for support vector machines. ACM Transactions on Intelligent Systems and diff --git a/imagery/i.svm.train/i.svm.train.md b/imagery/i.svm.train/i.svm.train.md index b801fb8f943..87a10a72cb5 100644 --- a/imagery/i.svm.train/i.svm.train.md +++ b/imagery/i.svm.train/i.svm.train.md @@ -89,7 +89,7 @@ Please cite both - LIBSVM and i.svm. - For i.svm.\* modules: Nartiss, M., & Melniks, R. (2023). Improving pixel-­based classification of GRASS GIS with support vector machine. Transactions - in GIS, 00, 1–16. https://doi.org/10.1111/tgis.13102 + in GIS, 00, 1–16. - For LIBSVM: Chang, C.-C., & Lin, C.-J. (2011). LIBSVM : a library for support vector machines. ACM Transactions on Intelligent Systems and diff --git a/imagery/i.topo.corr/i.topo.corr.md b/imagery/i.topo.corr/i.topo.corr.md index 48fd5d9f52f..19dc172414c 100644 --- a/imagery/i.topo.corr/i.topo.corr.md +++ b/imagery/i.topo.corr/i.topo.corr.md @@ -59,11 +59,11 @@ be calculated as ## NOTES -1. The illumination model (cos_i) with flag -i uses the actual region +1. The illumination model (cos_i) with flag -i uses the actual region as limits and the resolution of the elevation map. -2. The topographic correction use the full reflectance file (null +2. The topographic correction use the full reflectance file (null remain null) and its resolution. -3. The elevation map to calculate the illumination model should be +3. The elevation map to calculate the illumination model should be metric. ## EXAMPLES diff --git a/imagery/i.vi/i.vi.md b/imagery/i.vi/i.vi.md index ca305d88b30..728c2e6419b 100644 --- a/imagery/i.vi/i.vi.md +++ b/imagery/i.vi/i.vi.md @@ -520,7 +520,7 @@ Originally from kepler.gps.caltech.edu A FAQ on Vegetation in Remote Sensing Written by Terrill W. Ray, Div. of Geological and Planetary Sciences, -California Institute of Technology, email: terrill@mars1.gps.caltech.edu +California Institute of Technology, email: Snail Mail: Terrill Ray Division of Geological and Planetary Sciences diff --git a/imagery/i.zc/i.zc.md b/imagery/i.zc/i.zc.md index a6539bcd41b..49cdd59f5d8 100644 --- a/imagery/i.zc/i.zc.md +++ b/imagery/i.zc/i.zc.md @@ -11,13 +11,13 @@ discussed briefly below. The procedure to find the "edges" in the image is as follows: -1. The Fourier transform of the image is taken, -2. The Fourier transform of the Laplacian of a two-dimensional Gaussian +1. The Fourier transform of the image is taken, +2. The Fourier transform of the Laplacian of a two-dimensional Gaussian function is used to filter the transformed image, -3. The result is run through an inverse Fourier transform, -4. The resulting image is traversed in search of places where the image +3. The result is run through an inverse Fourier transform, +4. The resulting image is traversed in search of places where the image changes from positive to negative or from negative to positive, -5. Each cell in the map where the value crosses zero (with a change in +5. Each cell in the map where the value crosses zero (with a change in value greater than the threshold value) is marked as an edge and an orientation is assigned to it. The resulting raster map layer is output. diff --git a/imagery/imageryintro.md b/imagery/imageryintro.md index 891db9d6d47..6ed5f67ea05 100644 --- a/imagery/imageryintro.md +++ b/imagery/imageryintro.md @@ -68,9 +68,9 @@ along the edge of the map itself. As a general rule in GRASS: -1. Raster/imagery output maps have their bounds and resolution equal to +1. Raster/imagery output maps have their bounds and resolution equal to those of the current region. -2. Raster/imagery input maps are automatically cropped/padded and +2. Raster/imagery input maps are automatically cropped/padded and rescaled (using nearest-neighbor resampling) to match the current region. diff --git a/lib/htmldriver/htmldriver.md b/lib/htmldriver/htmldriver.md index c7283380a86..cd6a28e3fba 100644 --- a/lib/htmldriver/htmldriver.md +++ b/lib/htmldriver/htmldriver.md @@ -46,7 +46,7 @@ Several environment variables affect the operation of the HTML driver: type of image map to create (default is CLIENT): **`CLIENT`**    Netscape/IE client-side image map (NAME="map"). **`APACHE`**    Apache/NCSA server-side image map. - **`RAW`**         Raw url and polygon vertices (*url  x1  y1  x2  y2  + **`RAW`**         Raw url and polygon vertices (*url  x1  y1  x2  y2 .....*), suitable for conversion to CERN server format, or any other format with user supplied conversion program. - **GRASS_RENDER_FILE=filename** diff --git a/lib/init/grass.md b/lib/init/grass.md index a52250cd435..7f2f1c37237 100644 --- a/lib/init/grass.md +++ b/lib/init/grass.md @@ -7,7 +7,7 @@ EPSG:code\[:datum_trans\]**\] \| **-e** \| **-f** \| \[**--text** \| **--tmp-mapset**\] \[\[\[**\/**\]**\/**\] **\**\] \[**--exec EXECUTABLE**\] -### Flags: +### Flags **-h** \| **-help** \| **--help** Prints a brief usage message and exits @@ -67,7 +67,7 @@ with the --exec flag). The active mapset will be the PERMANENT mapset. Run using a temporary mapset which is created in the specified project and deleted at the end of the execution (use with the --exec flag). -### Parameters: +### Parameters **GISDBASE** Initial database directory which should be a fully qualified path (e.g., @@ -175,10 +175,10 @@ There is an order of precedence in the way *grass* determines the user interface to use. The following is the hierarchy from highest precedence to lowest. -1. Command line argument -2. Environment variable GRASS_GUI -3. Value set in `$HOME/.grass8/rc` (GUI) -4. Default value - `gui` +1. Command line argument +2. Environment variable GRASS_GUI +3. Value set in `$HOME/.grass8/rc` (GUI) +4. Default value - `gui` ### Python Environment Variables diff --git a/lib/init/helptext.md b/lib/init/helptext.md index df90b7d6ca8..37343fd7ad4 100644 --- a/lib/init/helptext.md +++ b/lib/init/helptext.md @@ -5,8 +5,6 @@ system. ![\[GRASS GIS after first startup\]](grass_start.png) - - The main component of the Data tab is the *Data Catalog* which shows the GRASS GIS hierarchical structure consisting of database ![\[GRASS Database\]](grassdb.png), project ![\[project\]](location.png) and diff --git a/lib/vector/rtree/test_suite/test.rtree.lib.md b/lib/vector/rtree/test_suite/test.rtree.lib.md index 8b137891791..e69de29bb2d 100644 --- a/lib/vector/rtree/test_suite/test.rtree.lib.md +++ b/lib/vector/rtree/test_suite/test.rtree.lib.md @@ -1 +0,0 @@ - diff --git a/misc/m.nviz.script/m.nviz.script.md b/misc/m.nviz.script/m.nviz.script.md index 4b427c17803..f288c840187 100644 --- a/misc/m.nviz.script/m.nviz.script.md +++ b/misc/m.nviz.script/m.nviz.script.md @@ -13,7 +13,7 @@ line (nviz script=script_name) or after NVIZ is started by selecting ## OPTIONS -### Flags: +### Flags **-f** Full render @@ -40,7 +40,7 @@ Render the animation in an off-screen context **-e** Enable vector and sites drawing -### Parameters: +### Parameters **input** The name of the GRASS raster map with elevation data. diff --git a/ps/ps.map/ps.map.md b/ps/ps.map/ps.map.md index 5936cb0b5a5..f414022baed 100644 --- a/ps/ps.map/ps.map.md +++ b/ps/ps.map/ps.map.md @@ -62,7 +62,7 @@ instructions while others are multiple line. Multiple line instructions consist of the main instruction followed by a subsection of one or more additional instructions and are terminated with an *end* instruction. -### Instruction keywords: +### Instruction keywords \[ [border](#border) \| [colortable](#colortable) \| [comments](#comments) \| [copies](#copies) \| [eps](#eps) \| @@ -92,7 +92,7 @@ zero, the default vertical location is used. **font** *font name* The name of the PostScript font. Fonts present in all PostScript implementations are: -` Times-Roman, Times-Italic, Times-Bold, Times-BoldItalic, Helvetica, Helvetica-Oblique, Helvetica-Bold, Helvetica-BoldOblique, Courier, Courier-Oblique, Courier-Bold, and Courier-BoldOblique`. +`Times-Roman, Times-Italic, Times-Bold, Times-BoldItalic, Helvetica, Helvetica-Oblique, Helvetica-Bold, Helvetica-BoldOblique, Courier, Courier-Oblique, Courier-Bold, and Courier-BoldOblique`. The default is Helvetica. **fontsize** *font size* @@ -112,8 +112,6 @@ For options that take a yes or no answer, you can simply use the letters is not case-sensitive. Typically the option with have a default answer and you only need to specify one if you wish to override it. - - ### Command usage @@ -704,6 +702,7 @@ EXAMPLE: paper a3 end ``` + ```sh EXAMPLE: paper @@ -955,17 +954,13 @@ USAGE: scale scale The scale can be selected either as: - a relative ratio, e.g. 1:25000; - an absolute width of the printed map, e.g. 10 inches; - the number of printed paper panels, e.g. 3 panels *.I* (at the present time, only 1 panel is supported); - the number of miles per inch, e.g. 1 inch equals 4 miles. This example would set the scale of the map to 1 unit = 25000 units. @@ -1133,7 +1128,6 @@ Entering **no** to the opaque option will allow the user to see any vectors which go through the text's background box. Otherwise, they will end at the box's edge. - The following example would place the text *SPEARFISH LAND COVER* at the coordinates E650000 N7365000. The text would be a total of 3 points wide (2 pixels of red text and 1 pixel black highlight), have a white @@ -1469,8 +1463,6 @@ Terminates input and begin painting the map. USAGE: end ``` - - ## EXAMPLES The following are examples of *ps.map* script files. diff --git a/python/grass/docs/_templates/oholosidebar.md b/python/grass/docs/_templates/oholosidebar.md index 8b137891791..e69de29bb2d 100644 --- a/python/grass/docs/_templates/oholosidebar.md +++ b/python/grass/docs/_templates/oholosidebar.md @@ -1 +0,0 @@ - diff --git a/raster/r.contour/r.contour.md b/raster/r.contour/r.contour.md index 1a5abbfce3b..5225f633fe6 100644 --- a/raster/r.contour/r.contour.md +++ b/raster/r.contour/r.contour.md @@ -66,4 +66,4 @@ r.contour input=elev_lid792_1m output=elev_lid792_1m_contours \ ## AUTHORS Terry Baker, U.S. Army Construction Engineering Research Laboratory -3/2001: cut parameter and fixes by Andrea Aime (aaime@libero.it) +3/2001: cut parameter and fixes by Andrea Aime () diff --git a/raster/r.cost/r.cost.md b/raster/r.cost/r.cost.md index 32770320563..cb7545bbafe 100644 --- a/raster/r.cost/r.cost.md +++ b/raster/r.cost/r.cost.md @@ -104,17 +104,17 @@ Example for solving multiple directions: Multiple directions can be solved as in the above example with the following steps: -1. Create multiple directions with **r.cost**/**r.walk** using the +1. Create multiple directions with **r.cost**/**r.walk** using the **-b** flag -2. Extract paths using **r.path format=bitmask** -3. Calculate the distance from NULL cells to paths using +2. Extract paths using **r.path format=bitmask** +3. Calculate the distance from NULL cells to paths using **r.grow.distance -n input=\** -4. Invert the sign of the distances with **r.mapcalc** because for the +4. Invert the sign of the distances with **r.mapcalc** because for the solver smaller is better, and here we want to get the center of an area with multiple directions -5. Use these negative distances as solver for a second pass of +5. Use these negative distances as solver for a second pass of **r.cost** -6. Extract paths again with **r.path** to get a geometrically optimized +6. Extract paths again with **r.path** to get a geometrically optimized solution ## NULL CELLS @@ -286,7 +286,7 @@ minimum cost path. Antony Awaida, Intelligent Engineering Systems Laboratory, M.I.T. James Westervelt, U.S.Army Construction Engineering Research Laboratory -Updated for Grass 5 by Pierre de Mouveaux (pmx@audiovu.com) +Updated for Grass 5 by Pierre de Mouveaux () Markus Metz Multiple path directions sponsored by [mundialis](https://www.mundialis.de) diff --git a/raster/r.fill.stats/r.fill.stats.md b/raster/r.fill.stats/r.fill.stats.md index 380b2fb2a22..1278a194464 100644 --- a/raster/r.fill.stats/r.fill.stats.md +++ b/raster/r.fill.stats/r.fill.stats.md @@ -308,6 +308,7 @@ Check that there are more non-NULL cells than NULL ("no data") cells: ```sh r.univar map=ground_raw ``` + ```sh total null and non-null cells: 2340900 total null cells: 639184 diff --git a/raster/r.geomorphon/r.geomorphon.md b/raster/r.geomorphon/r.geomorphon.md index 02e762a2db5..290360d4ab8 100644 --- a/raster/r.geomorphon/r.geomorphon.md +++ b/raster/r.geomorphon/r.geomorphon.md @@ -3,7 +3,7 @@ *r.geomorphon* calculates terrain forms using machine-vison technique called geomorphons. -### What is geomorphon: +### What is geomorphon What is geomorphon @@ -111,7 +111,7 @@ Returns geomorphic map with 10 most popular terrestrial forms. Legend for forms, its definition by the number of *+* and *-* and its idealized visualisation are presented at the image. -### Forms represented by geomorphons: +### Forms represented by geomorphons forms legend diff --git a/raster/r.gwflow/r.gwflow.md b/raster/r.gwflow/r.gwflow.md index 52653a5f6ee..29c9ef8cbc6 100644 --- a/raster/r.gwflow/r.gwflow.md +++ b/raster/r.gwflow/r.gwflow.md @@ -73,8 +73,6 @@ states are supportet: - 2 == Dirichlet - cells of this type will have a fixed piezometric head value which do not change over the time - - Note that all required raster maps are read into main memory. Additionally the linear equation system will be allocated, so the memory consumption of this module rapidely grow with the size of the input diff --git a/raster/r.horizon/r.horizon.md b/raster/r.horizon/r.horizon.md index 715451d2fbd..39a323de854 100644 --- a/raster/r.horizon/r.horizon.md +++ b/raster/r.horizon/r.horizon.md @@ -27,7 +27,7 @@ orientation (North=0, clockwise). Activating the **-l** flag allows additionally printing the distance to each horizon angle. -### Input parameters: +### Input parameters The *elevation* parameter is an input elevation raster map. If the buffer options are used (see below), this raster should extend over the diff --git a/raster/r.in.bin/r.in.bin.md b/raster/r.in.bin/r.in.bin.md index b98c1edc853..e9d3b8c9374 100644 --- a/raster/r.in.bin/r.in.bin.md +++ b/raster/r.in.bin/r.in.bin.md @@ -142,7 +142,7 @@ r.in.bin in=gpcp_v2.2_psg.1979 out=gpcp_1979. \ ## AUTHORS -Jacques Bouchard, France (bouchard@onera.fr) -Bob Covill, Canada (bcovill@tekmap.ns.ca) +Jacques Bouchard, France () +Bob Covill, Canada () Markus Metz -Man page: Zsolt Felker (felker@c160.pki.matav.hu) +Man page: Zsolt Felker () diff --git a/raster/r.in.mat/r.in.mat.md b/raster/r.in.mat/r.in.mat.md index 4388322042d..4c5cfee9398 100644 --- a/raster/r.in.mat/r.in.mat.md +++ b/raster/r.in.mat/r.in.mat.md @@ -70,7 +70,6 @@ information will be correct: ew_res = x_range/cols ``` - 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 @@ -91,8 +90,6 @@ In Octave, save with: save -mat4-binary filename.mat map_* ``` - - ## TODO Robust support for mixed-Endian importation. *(This is a work in diff --git a/raster/r.info/r.info.md b/raster/r.info/r.info.md index 3507ba0e9a9..6f8fc7d8532 100644 --- a/raster/r.info/r.info.md +++ b/raster/r.info/r.info.md @@ -125,6 +125,7 @@ Finally, the output from *r.info* can be output in JSON by passing the ```sh r.info slope format=json ``` + ```sh { "north": 228500, 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 244cea2f57e..fc25c4aeb68 100644 --- a/raster/r.li/r.li.cwed/r.li.cwed.md +++ b/raster/r.li/r.li.cwed/r.li.cwed.md @@ -52,7 +52,6 @@ r.li.cwed input=my_map conf=my_conf output=my_out \ path=/path/to/weights.csv ``` - Example for input "weights.csv" file: ```sh @@ -77,5 +76,5 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () Markus Metz diff --git a/raster/r.li/r.li.daemon/r.li.daemon.md b/raster/r.li/r.li.daemon/r.li.daemon.md index 01dba044822..0aa5d7d5c71 100644 --- a/raster/r.li/r.li.daemon/r.li.daemon.md +++ b/raster/r.li/r.li.daemon/r.li.daemon.md @@ -19,7 +19,7 @@ members are explained in the source code (doxygen) documentation. To write a new index only two steps are needed: -1. Define a function and insert its declaration on file **index.h** in +1. Define a function and insert its declaration on file **index.h** in *r.li.daemon* folder, which contains all index declarations. This function must be of this kind: @@ -38,7 +38,7 @@ To write a new index only two steps are needed: This function has to return 1 on success and 0 otherwise. This function type is defined using typedef named `rli_func`. -2. Create a main for command line arguments parsing, and call the +2. Create a main for command line arguments parsing, and call the function ```sh @@ -74,7 +74,6 @@ RLI_get_fcell_row(int, int, area_des) RLI_get_dcell_row(int, int, area_des) ``` - to use an ad hoc build memory management developed to speed up the system. The documentation is in doxygen files. diff --git a/raster/r.li/r.li.dominance/r.li.dominance.md b/raster/r.li/r.li.dominance/r.li.dominance.md index 64ba925817c..3f0105c0d14 100644 --- a/raster/r.li/r.li.dominance/r.li.dominance.md +++ b/raster/r.li/r.li.dominance/r.li.dominance.md @@ -70,5 +70,5 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () Markus Metz diff --git a/raster/r.li/r.li.edgedensity/r.li.edgedensity.md b/raster/r.li/r.li.edgedensity/r.li.edgedensity.md index f3d02fc9822..918b4e82379 100644 --- a/raster/r.li/r.li.edgedensity/r.li.edgedensity.md +++ b/raster/r.li/r.li.edgedensity/r.li.edgedensity.md @@ -89,5 +89,5 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () Markus Metz diff --git a/raster/r.li/r.li.md b/raster/r.li/r.li.md index 209e95cbbac..faeb7f9bccd 100644 --- a/raster/r.li/r.li.md +++ b/raster/r.li/r.li.md @@ -34,12 +34,12 @@ saving user from the need to specify all parameters over and over again. The general procedure to calculate an index from a raster map is two-fold: -1. run *g.gui.rlisetup*: create a configuration file selecting the +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. run one or more of the *r.li.**\[index\]*** modules (e.g., +2. run one or more of the *r.li.**\[index\]*** modules (e.g., *r.li.**patchdensity***) to calculate the selected index using on the areas selected on configuration file. @@ -48,47 +48,47 @@ two-fold: Calculate a patch density index on the entire 'geology' raster map in the Spearfish sample dataset, using a 5x5 moving window: -1. CREATE A NEW CONFIGURATION FILE - 1. run +1. CREATE A NEW CONFIGURATION FILE + 1. run ```sh g.gui.rlisetup ``` - 2. The main *g.gui.rlisetup* window is displayed, click on "New" + 2. The main *g.gui.rlisetup* window is displayed, click on "New" - 3. The new configuration window is now displayed, enter the + 3. The new configuration window is now displayed, enter the configuration file name (e.g., "my_conf", do not use absolute paths) - + Now the new configuration window is displayed. Enter the configuration file name (e.g., "my_conf", do not use absolute paths) and the name of raster map (e.g., "geology"). The other fields are not needed for this configuration. - 4. Click on "Setup sampling frame", select "Whole map layer" and + 4. Click on "Setup sampling frame", select "Whole map layer" and click "OK" - 5. Click on "Setup sampling areas", select "Moving window" and + 5. Click on "Setup sampling areas", select "Moving window" and click "OK" - 6. Click on "Use keyboard to enter moving window dimension" + 6. Click on "Use keyboard to enter moving window dimension" - 7. Select "Rectangle" and enter 5 in the "height" and "width" + 7. Select "Rectangle" and enter 5 in the "height" and "width" fields - 8. Click on "Save settings" + 8. Click on "Save settings" - 9. Close the *g.gui.rlisetup* window -2. CALCULATE PATCHDENSITY INDEX - 1. set the region settings to the "`geology`" raster map: + 9. Close the *g.gui.rlisetup* window +2. CALCULATE PATCHDENSITY INDEX + 1. set the region settings to the "`geology`" raster map: ```sh g.region raster=geology -p ``` - 2. run *r.li.patchdensity*: + 2. run *r.li.patchdensity*: ```sh r.li.patchdensity input=geology conf=my_conf out=patchdens diff --git a/raster/r.li/r.li.mpa/r.li.mpa.md b/raster/r.li/r.li.mpa/r.li.mpa.md index cd68e8a9e88..c9ef22e211b 100644 --- a/raster/r.li/r.li.mpa/r.li.mpa.md +++ b/raster/r.li/r.li.mpa/r.li.mpa.md @@ -82,5 +82,5 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () Markus Metz diff --git a/raster/r.li/r.li.richness/r.li.richness.md b/raster/r.li/r.li.richness/r.li.richness.md index e44a5173824..d82effb7dfb 100644 --- a/raster/r.li/r.li.richness/r.li.richness.md +++ b/raster/r.li/r.li.richness/r.li.richness.md @@ -67,4 +67,4 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () diff --git a/raster/r.li/r.li.shannon/r.li.shannon.md b/raster/r.li/r.li.shannon/r.li.shannon.md index 6a356c96576..d1b76ddbb2b 100644 --- a/raster/r.li/r.li.shannon/r.li.shannon.md +++ b/raster/r.li/r.li.shannon/r.li.shannon.md @@ -70,4 +70,4 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () diff --git a/raster/r.li/r.li.shape/r.li.shape.md b/raster/r.li/r.li.shape/r.li.shape.md index 050ebd1bbc5..ff35b5967c0 100644 --- a/raster/r.li/r.li.shape/r.li.shape.md +++ b/raster/r.li/r.li.shape/r.li.shape.md @@ -72,4 +72,4 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Claudio Porta and Lucio Davide Spano, students of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI) (www.faunalia.it) +Commission from Faunalia Pontedera (PI) () diff --git a/raster/r.li/r.li.simpson/r.li.simpson.md b/raster/r.li/r.li.simpson/r.li.simpson.md index 920393e5e5a..18c5ed80f09 100644 --- a/raster/r.li/r.li.simpson/r.li.simpson.md +++ b/raster/r.li/r.li.simpson/r.li.simpson.md @@ -70,4 +70,4 @@ Gen. Tech. Rep. PNW-351. ([PDF](https://doi.org/10.2737/PNW-GTR-351)) Serena Pallecchi, student of Computer Science University of Pisa (Italy). -Commission from Faunalia Pontedera (PI), Italy (www.faunalia.it) +Commission from Faunalia Pontedera (PI), Italy () diff --git a/raster/r.mapcalc/r.mapcalc.md b/raster/r.mapcalc/r.mapcalc.md index 48a4da44ad6..878a3d8d466 100644 --- a/raster/r.mapcalc/r.mapcalc.md +++ b/raster/r.mapcalc/r.mapcalc.md @@ -399,6 +399,7 @@ sqrt(x) square root of x F tan(x) tangent of x (x is in degrees) F xor(x,y) exclusive-or (XOR) of x and y I ``` + ```sh Internal variables: row() current row of moving window I diff --git a/raster/r.mapcalc/r3.mapcalc.md b/raster/r.mapcalc/r3.mapcalc.md index 9791c228a2f..4ae216b3226 100644 --- a/raster/r.mapcalc/r3.mapcalc.md +++ b/raster/r.mapcalc/r3.mapcalc.md @@ -261,6 +261,7 @@ sqrt(x) square root of x F tan(x) tangent of x (x is in degrees) F xor(x,y) exclusive-or (XOR) of x and y I ``` + ```sh Internal variables: row() current row of moving window I diff --git a/raster/r.neighbors/r.neighbors.md b/raster/r.neighbors/r.neighbors.md index 8ff7a42184e..e0571166759 100644 --- a/raster/r.neighbors/r.neighbors.md +++ b/raster/r.neighbors/r.neighbors.md @@ -181,7 +181,6 @@ The result will be the 90th percentile of neighborhood. **quantile** Any quantile as specified by "quantile" input parameter. - *Neighborhood Size:* The neighborhood **size** specifies which cells surrounding any given cell fall into the neighborhood for that cell. The **size** must be an odd integer and represent the length of one of @@ -336,8 +335,8 @@ dependent on the input data values.) The following logic has been implemented: For any aggregate, there are two factors affecting the output type: -1. Whether the input map is integer or floating-point. -2. Whether the weighted or unweighted version of the aggregate is used. +1. Whether the input map is integer or floating-point. +2. Whether the weighted or unweighted version of the aggregate is used. These combine to create four possibilities: @@ -368,13 +367,13 @@ meaningless. With the current aggregates, there are 5 cases: -1. Output is always float: average, variance, stddev, quantiles (with +1. Output is always float: average, variance, stddev, quantiles (with interpolation). -2. Output is always integer: diversity, interspersion. -3. Output is integer if unweighted, float if weighted: count. -4. Output matches input: minimum, maximum, range, mode (subject to note +2. Output is always integer: diversity, interspersion. +3. Output is integer if unweighted, float if weighted: count. +4. Output matches input: minimum, maximum, range, mode (subject to note 2 above), quantiles (without interpolation). -5. Output is integer for integer input and unweighted aggregate, +5. Output is integer for integer input and unweighted aggregate, otherwise float: sum. ### Performance diff --git a/raster/r.object.geometry/r.object.geometry.md b/raster/r.object.geometry/r.object.geometry.md index edd7f4517bd..606b32eb3d9 100644 --- a/raster/r.object.geometry/r.object.geometry.md +++ b/raster/r.object.geometry/r.object.geometry.md @@ -39,6 +39,7 @@ JSON: ```sh r.object.geometry input=zipcodes format=json ``` + ```sh [ { diff --git a/raster/r.out.mat/r.out.mat.md b/raster/r.out.mat/r.out.mat.md index 8e38a0091c8..30390d48e94 100644 --- a/raster/r.out.mat/r.out.mat.md +++ b/raster/r.out.mat/r.out.mat.md @@ -15,7 +15,6 @@ Specifically, the following array variables are created: - **map_eastern_edge** - **map_western_edge** - In addition, *r.out.mat* makes for a nice binary container format for transferring georeferenced maps around, even if you don't use Matlab or Octave. @@ -57,8 +56,6 @@ commands may be used to determine the map's resolution information: ew_res = x_range/cols ``` - - ## EXAMPLE In Matlab, plot with either: @@ -73,8 +70,6 @@ or contourf(map_data, 24), axis ij, axis equal, axis tight, colorbar ``` - - ## TODO Add support for exporting map history, category information, color map, diff --git a/raster/r.out.pov/r.out.pov.md b/raster/r.out.pov/r.out.pov.md index 09d6e3a75d0..e8b64c2e6ac 100644 --- a/raster/r.out.pov/r.out.pov.md +++ b/raster/r.out.pov/r.out.pov.md @@ -60,4 +60,4 @@ height_field { ## AUTHOR -Klaus D. Meyer, GEUM.tec GbR, eMail: *GEUM.tec@geum.de* +Klaus D. Meyer, GEUM.tec GbR, eMail: ** diff --git a/raster/r.profile/r.profile.md b/raster/r.profile/r.profile.md index 287f8bcc764..d62ece79517 100644 --- a/raster/r.profile/r.profile.md +++ b/raster/r.profile/r.profile.md @@ -78,8 +78,6 @@ This will extract a profile along the track defined by the three coordinate pairs. The output file "profile_points.csv" contains east,north,distance,value (here: elevation). - - ### Extraction of values along profile defined by coordinates (variant 2) Coordinate pairs can also be "piped" into *r.profile* (variant 2a): diff --git a/raster/r.proj/r.proj.md b/raster/r.proj/r.proj.md index ee43f83f722..0be910f9514 100644 --- a/raster/r.proj/r.proj.md +++ b/raster/r.proj/r.proj.md @@ -264,11 +264,11 @@ r.proj input=elevation.dem output=elevation.dem.reproj \ ## REFERENCES -1. Evenden, G.I. (1990) [Cartographic projection procedures for the +1. Evenden, G.I. (1990) [Cartographic projection procedures for the UNIX environment - a user's manual.](https://proj.org) USGS Open-File Report 90-284 (OF90-284.pdf) See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994). -2. Richards, John A. (1993), Remote Sensing Digital Image Analysis, +2. Richards, John A. (1993), Remote Sensing Digital Image Analysis, Springer-Verlag, Berlin, 2nd edition. [PROJ](https://proj.org): Projection/datum support library diff --git a/raster/r.reclass/r.reclass.md b/raster/r.reclass/r.reclass.md index 430b6c773aa..8acfcf69a47 100644 --- a/raster/r.reclass/r.reclass.md +++ b/raster/r.reclass/r.reclass.md @@ -11,9 +11,9 @@ redirected from a file, or piped through another program). Before using *r.reclass* the user must know the following: -1. The new categories desired; and, which old categories fit into which +1. The new categories desired; and, which old categories fit into which new categories. -2. The names of the new categories. +2. The names of the new categories. ## NOTES diff --git a/raster/r.recode/r.recode.md b/raster/r.recode/r.recode.md index 4d95f5d9744..6fc835bb919 100644 --- a/raster/r.recode/r.recode.md +++ b/raster/r.recode/r.recode.md @@ -25,14 +25,14 @@ DCELL to FCELL, etc). Standard floating point raster precision is float There are four basic routines that it accepts: -1. old-low to old-high is reclassed to new-low to new high , where the +1. old-low to old-high is reclassed to new-low to new high , where the user provides all four values. The program figures on the fly what type of raster should be created. -2. old-low to old-high is reclassed to a single new value. Anything +2. old-low to old-high is reclassed to a single new value. Anything outside the range is null. -3. \* to old-high will reclass everything less than old-high to a +3. \* to old-high will reclass everything less than old-high to a single new value. -4. old-low to \* will reclass everything greater than old-low to a +4. old-low to \* will reclass everything greater than old-low to a single new value. These four sets of arguments can be given on the command line, or piped diff --git a/raster/r.relief/r.relief.md b/raster/r.relief/r.relief.md index d60d428bb49..b07836895e4 100644 --- a/raster/r.relief/r.relief.md +++ b/raster/r.relief/r.relief.md @@ -6,22 +6,22 @@ values entered by the user. The parameters controlling the shading are: -1. An **input** raster map to provide elevation values for the shaded +1. An **input** raster map to provide elevation values for the shaded relief map. Typically, this would be a map layer of elevation; however, any raster map layer can be named. -2. The **altitude** of the sun in degrees above the horizon (a value +2. The **altitude** of the sun in degrees above the horizon (a value between 0 and 90 degrees). -3. The **azimuth** of the sun in degrees to the east of north (a value +3. The **azimuth** of the sun in degrees to the east of north (a value between 0 and 360 degrees; clockwise from north) -4. The scaling parameter, which compensates for a different horizontal +4. The scaling parameter, which compensates for a different horizontal **scale** than vertical scale. If **scale** is a number, then the ewres and nsres are multiplied by that scale to calculate the shading. (Default=1.0 for equivalent horizontal and vertical scales.) -5. The **zscale** exaggeration factor that changes the apparent relief +5. The **zscale** exaggeration factor that changes the apparent relief for the shaded relief map. This can be any positive (or negative) floating point value. (default=1.0) -6. Horizontal distances are calculated in meters, using geodesic +6. Horizontal distances are calculated in meters, using geodesic distances for a latitude-longitude projection. With an elevation map measured in feet, the **units** option can be set to automatically convert meters to international feet (0.3048 meters = 1 foot) or diff --git a/raster/r.report/r.report.md b/raster/r.report/r.report.md index 82d90ea5f7b..a64cff7db41 100644 --- a/raster/r.report/r.report.md +++ b/raster/r.report/r.report.md @@ -40,6 +40,7 @@ are not reported (see **-n** flag). ```sh r.report -n map=geology_30m units=mi,a sort=desc ``` + ```sh +-----------------------------------------------------------------------------+ | RASTER MAP CATEGORY REPORT | @@ -79,6 +80,7 @@ only part of the table): ```sh r.report map=zipcodes@PERMANENT,landclass96@PERMANENT units=h,p ``` + ```sh +-----------------------------------------------------------------------------+ | RASTER MAP CATEGORY REPORT | @@ -124,6 +126,7 @@ The output from *r.report* can be output in JSON by passing the ```sh r.report -n -a map=towns,elevation units=miles,meters,kilometers,acres,hectares,cells,percent nsteps=2 format=json ``` + ```sh { "location": "nc_spm_08_grass7", diff --git a/raster/r.resamp.rst/r.resamp.rst.md b/raster/r.resamp.rst/r.resamp.rst.md index c18b0d4106d..903c0a16872 100644 --- a/raster/r.resamp.rst/r.resamp.rst.md +++ b/raster/r.resamp.rst/r.resamp.rst.md @@ -164,7 +164,7 @@ Resampling](https://grasswiki.osgeo.org/wiki/Interpolation) in GRASS GIS *Original version of program (in FORTRAN):* Lubos Mitas, NCSA, University of Illinois at Urbana Champaign, Il -Helena Mitasova, US Army CERL, Champaign, Illinois  +Helena Mitasova, US Army CERL, Champaign, Illinois *Modified program (translated to C, adapted for GRASS , segmentation procedure):* diff --git a/raster/r.ros/r.ros.md b/raster/r.ros/r.ros.md index 06a04d6ef9a..02bf12ee4b7 100644 --- a/raster/r.ros/r.ros.md +++ b/raster/r.ros/r.ros.md @@ -73,12 +73,12 @@ r.ros -s model=fire_model moisture_1h=1hour_moisture moisture_live=live_moisture ## NOTES -1. *r.ros* is supposed to be run before running +1. *r.ros* is supposed to be run before running *[r.spread](r.spread.md)* module. The combination of these two modules forms a simulation of the spread of wildfires. -2. The user should be sure that the inputs to *r.ros* are in proper +2. The user should be sure that the inputs to *r.ros* are in proper units. -3. The output units for the base and maximum ROSes are in cm/minute +3. The output units for the base and maximum ROSes are in cm/minute rather than ft/minute, which is due to that a possible zero ft/minute base ROS value and a positive integer ft/minute maximum ROS would result in calculation failure in the diff --git a/raster/r.sim/r.sim.sediment/r.sim.sediment.md b/raster/r.sim/r.sim.sediment/r.sim.sediment.md index 95b2fd423bf..31f5999ec7e 100644 --- a/raster/r.sim/r.sim.sediment/r.sim.sediment.md +++ b/raster/r.sim/r.sim.sediment/r.sim.sediment.md @@ -86,9 +86,8 @@ GeoModel, s.r.o. Bratislava, Slovakia [hofierka@geomodel.sk](mailto:hofi@geomodel.sk) - Chris Thaxton North Carolina State University -csthaxto@unity.ncsu.edu + diff --git a/raster/r.solute.transport/r.solute.transport.md b/raster/r.solute.transport/r.solute.transport.md index 47ed6f4807b..dd93ad0cb1a 100644 --- a/raster/r.solute.transport/r.solute.transport.md +++ b/raster/r.solute.transport/r.solute.transport.md @@ -49,8 +49,6 @@ differential equation is of the following form: - q -- inner well sources/sinks \[m^3/s\] - nf -- the effective porosity \[-\] - - Three different boundary conditions are implemented, the Dirichlet, Transmission and Neumann conditions. The calculation and boundary status of single cells can be set with the status map. The following states are @@ -65,8 +63,6 @@ supported: - 3 == Transmission - cells of this type should be placed on out-flow boundaries to assure the flow of the solute stream out - - Note that all required raster maps are read into main memory. Additionally the linear equation system will be allocated, so the memory consumption of this module rapidely grow with the size of the input diff --git a/raster/r.spread/r.spread.md b/raster/r.spread/r.spread.md index 671b8afb009..07360ae84c7 100644 --- a/raster/r.spread/r.spread.md +++ b/raster/r.spread/r.spread.md @@ -9,9 +9,9 @@ with *r.spreadpath*. Spread phenomena usually show uneven movement over space. Such unevenness is due to two reasons: -1. the uneven conditions from location to location, which can be called +1. the uneven conditions from location to location, which can be called *spatial heterogeneity*, and -2. the uneven conditions in different directions, which can be called +2. the uneven conditions in different directions, which can be called *anisotropy*. The anisotropy of spread occurs when any of the determining factors have diff --git a/raster/r.spreadpath/r.spreadpath.md b/raster/r.spreadpath/r.spreadpath.md index 017201f9542..2cf6b0b46e3 100644 --- a/raster/r.spreadpath/r.spreadpath.md +++ b/raster/r.spreadpath/r.spreadpath.md @@ -19,7 +19,7 @@ The backlink inputs can be generated from another GRASS raster program on a raster setting. More information on *r.spread* and *r.spreadpath* can be found in Xu (1994). -## Parameters: +## Parameters **x_input=***name* Name of input raster map layer containing backlink UTM easting diff --git a/raster/r.sun/r.sun.md b/raster/r.sun/r.sun.md index cbcac0e2c20..d80e347b91d 100644 --- a/raster/r.sun/r.sun.md +++ b/raster/r.sun/r.sun.md @@ -139,6 +139,7 @@ NULL data are considered as no barrier with shadowing effect. The maps' history files are generated containing the following listed parameters used in the computation: + - Solar constant used W.m-2 - Extraterrestrial irradiance on a plane perpendicular to the solar beam \[W.m-2\] diff --git a/raster/r.surf.area/r.surf.area.md b/raster/r.surf.area/r.surf.area.md index 361a38be54a..7ad51329d3a 100644 --- a/raster/r.surf.area/r.surf.area.md +++ b/raster/r.surf.area/r.surf.area.md @@ -22,13 +22,13 @@ the diagonal used. Reported totals are: -1. "Plan" area of `NULL` values within the current GRASS region -2. "Plan" area within calculation region (`rows-1 * cols-1 * cellarea`) -3. Average of the minimum and maximum calculated 3d triangle area +1. "Plan" area of `NULL` values within the current GRASS region +2. "Plan" area within calculation region (`rows-1 * cols-1 * cellarea`) +3. Average of the minimum and maximum calculated 3d triangle area within this region -4. "Plan" area within current computational region +4. "Plan" area within current computational region (`rows * cols * cellarea`) -5. Scaling of calculated area to current region +5. Scaling of calculated area to current region *r.surf.area* works best when the surface being evaluated extends to the edges of the current region and the cell resolution is small. Surfaces diff --git a/raster/r.surf.contour/r.surf.contour.md b/raster/r.surf.contour/r.surf.contour.md index cbf6690df13..19652f53285 100644 --- a/raster/r.surf.contour/r.surf.contour.md +++ b/raster/r.surf.contour/r.surf.contour.md @@ -19,7 +19,7 @@ rasterized contour lines, thus ensuring that an uphill and downhill contour value will be the two values chosen. *r.surf.contour* interpolates from the uphill and downhill values by the true distance. -### Parameters: +### Parameters **input=***name* Name of an existing raster map that contains a set of initial category diff --git a/raster/r.terraflow/r.terraflow.md b/raster/r.terraflow/r.terraflow.md index 74019646b94..a3d0bdae540 100644 --- a/raster/r.terraflow/r.terraflow.md +++ b/raster/r.terraflow/r.terraflow.md @@ -170,6 +170,7 @@ r.terraflow elev=elevation.10m filled=elevation10m.filled \ dir=elevation10m.mfdir swatershed=elevation10m.watershed \ accumulation=elevation10m.accu tci=elevation10m.tci ``` + ```sh g.region raster=elevation.10m -p r.terraflow elev=elevation.10m filled=elevation10m.filled \ @@ -180,21 +181,21 @@ r.terraflow elev=elevation.10m filled=elevation10m.filled \ ## REFERENCES -1. The [TerraFlow](http://www.cs.duke.edu/geo*/terraflow/) project at +1. The [TerraFlow](http://www.cs.duke.edu/geo*/terraflow/) project at Duke University -2. I/O-efficient algorithms for problems on grid-based terrains. Lars Arge, Laura Toma, and Jeffrey S. Vitter. In *Proc. Workshop on Algorithm Engineering and Experimentation*, 2000. To appear in *Journal of Experimental Algorithms*. -3. Flow computation on massive grids. Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura Toma, Jeffrey S. Vitter, Dean Urban and Rajiv Wickremesinghe. In *Proc. ACM Symposium on Advances in Geographic Information Systems*, 2001. -4. Flow computation on massive grid terrains. Lars Arge, Jeffrey S. Chase, Patrick N. Halpin, Laura diff --git a/raster/r.topmodel/r.topmodel.md b/raster/r.topmodel/r.topmodel.md index 8aa607bba2a..457816147c2 100644 --- a/raster/r.topmodel/r.topmodel.md +++ b/raster/r.topmodel/r.topmodel.md @@ -79,7 +79,7 @@ Subcatchment 1 5000 1.0 ``` -**input** +**input** This file contains observed weather data. ```sh diff --git a/raster/r.viewshed/r.viewshed.md b/raster/r.viewshed/r.viewshed.md index d39592cb70d..ef596727eb0 100644 --- a/raster/r.viewshed/r.viewshed.md +++ b/raster/r.viewshed/r.viewshed.md @@ -187,6 +187,6 @@ Laura Toma (Bowdoin College): `ltoma@bowdoin.edu` Yi Zhuang (Carnegie-Mellon University): `yzhuang@andrew.cmu.edu` -William Richard (Bowdoin College): `willster3021@gmail.com ` +William Richard (Bowdoin College): `willster3021@gmail.com` Markus Metz diff --git a/raster/r.walk/r.walk.md b/raster/r.walk/r.walk.md index 1800657a129..c3be5f06eff 100644 --- a/raster/r.walk/r.walk.md +++ b/raster/r.walk/r.walk.md @@ -169,7 +169,7 @@ landcover* Antony Awaida, Intelligent Engineering, Systems Laboratory, M.I.T. James Westervelt, U.S.Army Construction Engineering Research Laboratory -Updated for Grass 5 by Pierre de Mouveaux (pmx@audiovu.com) +Updated for Grass 5 by Pierre de Mouveaux () **Initial version of r.walk:** Steno Fontanari, 2002 diff --git a/raster/r.watershed/front/r.watershed.md b/raster/r.watershed/front/r.watershed.md index 9faa9610db5..fd898dded0e 100644 --- a/raster/r.watershed/front/r.watershed.md +++ b/raster/r.watershed/front/r.watershed.md @@ -287,13 +287,13 @@ area for the region of interest is completely included. To isolate an individual river network using the output of this module, a number of approaches may be considered. -1. Use a resample of the basins catchment raster map as a raster +1. Use a resample of the basins catchment raster map as a raster mask. The equivalent vector map method is similar using *[v.select](v.select.md)* or *[v.overlay](v.overlay.md)*. -2. Use the *[r.cost](r.cost.md)* module with a point in the river as a +2. Use the *[r.cost](r.cost.md)* module with a point in the river as a starting point. -3. Use the *[v.net.iso](v.net.iso.md)* module with a node in the river +3. Use the *[v.net.iso](v.net.iso.md)* module with a node in the river as a starting point. All individual river networks in the stream segments output can be diff --git a/raster/r.what/r.what.md b/raster/r.what/r.what.md index 161d79898cc..b5c3af76783 100644 --- a/raster/r.what/r.what.md +++ b/raster/r.what/r.what.md @@ -124,6 +124,7 @@ EOF 633614.08|224125.12|site 1|2|209.5939 632972.36|225382.87|site 2|15|140.7571 ``` + ```sh echo "633614.08 224125.12" | r.what map=landuse96_28m,aspect diff --git a/raster/rasterintro.md b/raster/rasterintro.md index e7c5931c56a..e508c3f4563 100644 --- a/raster/rasterintro.md +++ b/raster/rasterintro.md @@ -14,11 +14,11 @@ bounds of all cells within the map. As a general rule in GRASS GIS: -1. Raster output maps have their bounds and resolution equal to those +1. Raster output maps have their bounds and resolution equal to those of the current computational region. -2. Raster input maps are automatically cropped/padded and rescaled +2. Raster input maps are automatically cropped/padded and rescaled (using nearest-neighbour resampling) to match the current region. -3. Raster input maps are automatically masked if a raster map named +3. Raster input maps are automatically masked if a raster map named MASK exists. The MASK is only applied when *reading* maps from the disk. diff --git a/raster3d/r3.mkdspf/r3.mkdspf.md b/raster3d/r3.mkdspf/r3.mkdspf.md index 7b46c92b39b..dd8a306bf21 100644 --- a/raster3d/r3.mkdspf/r3.mkdspf.md +++ b/raster3d/r3.mkdspf/r3.mkdspf.md @@ -7,7 +7,7 @@ polygons that represent isosurfaces of the data volume. If specific *max* may be used alone or together to specify a sub-range of the data. The *step* parameter is given precedence over *tnum*. -### Flags: +### Flags **-q** Suppress progress report & min/max information @@ -15,7 +15,7 @@ Suppress progress report & min/max information **-f** Use flat shading rather than gradient -### Parameters: +### Parameters **grid3** Name of an existing 3D raster map diff --git a/raster3d/r3.neighbors/r3.neighbors.md b/raster3d/r3.neighbors/r3.neighbors.md index 794911ca590..5de5cfb3740 100644 --- a/raster3d/r3.neighbors/r3.neighbors.md +++ b/raster3d/r3.neighbors/r3.neighbors.md @@ -57,7 +57,6 @@ The number of different values within the neighborhood. The percentage of voxels containing values which differ from the values assigned to the center voxel in the neighborhood, plus 1. - *Neighborhood Size:* The neighborhood moving **window** specifies which voxel surrounding any given voxel fall into the neighborhood for that voxel. The **window** must be three comma separated odd integers. The diff --git a/raster3d/r3.showdspf/r3.showdspf.md b/raster3d/r3.showdspf/r3.showdspf.md index 9a0fa50c164..0dfa681b0df 100644 --- a/raster3d/r3.showdspf/r3.showdspf.md +++ b/raster3d/r3.showdspf/r3.showdspf.md @@ -65,7 +65,7 @@ THE INTERACTIVE OPTIONS ARE: ``` -### Hints: +### Hints - To navigate around the data, use the *r* command, then place the mouse pointer in the graphics window and drag with the left mouse to rotate @@ -87,7 +87,7 @@ List available thresholds with *?*. Use *l* to select isosurfaces (available number can be adjusted with *r3.mkdspf*) and *L* to display: `l 1 2 3 4 5` -`L ` +`L` To select and display a single threshold (here: 2), use: `t 2` diff --git a/scripts/d.rast.edit/d.rast.edit.md b/scripts/d.rast.edit/d.rast.edit.md index 7aa81181194..ca969864a8a 100644 --- a/scripts/d.rast.edit/d.rast.edit.md +++ b/scripts/d.rast.edit/d.rast.edit.md @@ -96,8 +96,8 @@ to type in the new value). Perhaps method(s) for multiple or mass cell edits would be useful. This could be done by providing modes in which the user may: -1. edit a block of cells to a given value by drawing a box; -2. be able to choose a given value which is automatically used as the +1. edit a block of cells to a given value by drawing a box; +2. be able to choose a given value which is automatically used as the new value on each cell chosen until a different value is desired. There is no user-interrupt handling. This could leave files in .tmp or diff --git a/scripts/i.pansharpen/i.pansharpen.md b/scripts/i.pansharpen/i.pansharpen.md index aa7435cac5e..56bed9b98ba 100644 --- a/scripts/i.pansharpen/i.pansharpen.md +++ b/scripts/i.pansharpen/i.pansharpen.md @@ -208,8 +208,6 @@ alt="R, G, B composite of PCA sharpened image at 15m" />
- - ## REFERENCES - Original Brovey formula reference unknown, probably... diff --git a/scripts/i.tasscap/i.tasscap.md b/scripts/i.tasscap/i.tasscap.md index 8a5ebcd4eec..ebf7a9682cc 100644 --- a/scripts/i.tasscap/i.tasscap.md +++ b/scripts/i.tasscap/i.tasscap.md @@ -60,8 +60,6 @@ alt="'Atmospheric haze' Tasseled Cap component 4" />
- - ## REFERENCES - LANDSAT-4/LANDSAT-5: TC-factor changed to CRIST et al. 1986, Proc. diff --git a/scripts/r.fillnulls/r.fillnulls.md b/scripts/r.fillnulls/r.fillnulls.md index 400487bbe14..39634edbeec 100644 --- a/scripts/r.fillnulls/r.fillnulls.md +++ b/scripts/r.fillnulls/r.fillnulls.md @@ -18,7 +18,7 @@ The width of edge area can be adjusted by changing the edge parameter. During the interpolation following warning may occur when using the RST method: -` Warning: strip exists with insufficient data` +`Warning: strip exists with insufficient data` `Warning: taking too long to find points for interpolation--please change the region to area where your points are` This warning is generated if large data holes exist within the surface. diff --git a/scripts/r.in.wms/r.in.wms.md b/scripts/r.in.wms/r.in.wms.md index 8ed4f119b5e..d38efd862a1 100644 --- a/scripts/r.in.wms/r.in.wms.md +++ b/scripts/r.in.wms/r.in.wms.md @@ -51,6 +51,7 @@ g.region n=90 s=-90 w=-180 e=180 res=0:10:00 -p r.in.wms url="http://watzmann-geog.urz.uni-heidelberg.de/cached/osm" layers=osm_auto:all output=osm format=png r.info osm ``` + ```sh # OSM Overlay WMS (can be used as an overlay for other maps) r.in.wms url="http://ows.mundialis.de/services/service?" layer=OSM-Overlay-WMS output=osm_overlay format=png @@ -110,6 +111,7 @@ API](http://api.ign.fr/) website # using WMS_GRASS driver r.in.wms url="http://wms.cuzk.cz/wms.asp" layers=prehledka_kraju-linie srs=4326 output=kn format=png ``` + ```sh # using WMTS_GRASS driver r.in.wms url="http://geoportal.cuzk.cz/WMTS_ORTOFOTO/WMTService.aspx" layers=orto output=orthophoto \ diff --git a/scripts/r.mapcalc.simple/r.mapcalc.simple.md b/scripts/r.mapcalc.simple/r.mapcalc.simple.md index 0fc09a61b94..dd0ad328e25 100644 --- a/scripts/r.mapcalc.simple/r.mapcalc.simple.md +++ b/scripts/r.mapcalc.simple/r.mapcalc.simple.md @@ -55,9 +55,11 @@ r.mapcalc.simple expression="0" output=zeros r.mapcalc.simple expression="1" output=ones r.mapcalc.simple expression="2" output=twos ``` + ```sh r.mapcalc.simple expression="A + B + C" a=zeros b=ones c=twos output=result1 ``` + ```sh r.mapcalc.simple expression="(A * B) / 2 + 3 * C" a=zeros b=ones c=twos output=result2 ``` diff --git a/scripts/v.db.addcolumn/v.db.addcolumn.md b/scripts/v.db.addcolumn/v.db.addcolumn.md index e38c650ab5c..ffbf5fdc460 100644 --- a/scripts/v.db.addcolumn/v.db.addcolumn.md +++ b/scripts/v.db.addcolumn/v.db.addcolumn.md @@ -42,4 +42,4 @@ v.info -c myroads ## AUTHOR -Moritz Lennert (mlennert@club.worldonline.be) +Moritz Lennert () diff --git a/scripts/v.db.update/v.db.update.md b/scripts/v.db.update/v.db.update.md index 3cdeca3344b..3f7f4d14f10 100644 --- a/scripts/v.db.update/v.db.update.md +++ b/scripts/v.db.update/v.db.update.md @@ -100,4 +100,4 @@ jul|logjuly ## AUTHOR -Moritz Lennert (mlennert@club.worldonline.be) +Moritz Lennert () diff --git a/temporal/t.rast.list/t.rast.list.md b/temporal/t.rast.list/t.rast.list.md index 46cbe2b1024..4222626b31d 100644 --- a/temporal/t.rast.list/t.rast.list.md +++ b/temporal/t.rast.list/t.rast.list.md @@ -176,6 +176,7 @@ id|name|mapset|start_time|end_time|interval_length|distance_from_begin 2012_11_tempmean@climate_2009_2012|2012_11_tempmean|climate_2009_2012|2012-11-01 00:00:00|2012-12-01 00:00:00|30.0|1400.0 2012_12_tempmean@climate_2009_2012|2012_12_tempmean|climate_2009_2012|2012-12-01 00:00:00|2013-01-01 00:00:00|31.0|1430.0 ``` + ```sh t.rast.list method=gran input=tempmean_monthly gran="2 months" id|name|mapset|start_time|end_time|interval_length|distance_from_begin diff --git a/temporal/t.select/t.select.md b/temporal/t.select/t.select.md index f6837afc171..bbedea0d4fb 100644 --- a/temporal/t.select/t.select.md +++ b/temporal/t.select/t.select.md @@ -336,8 +336,6 @@ tshift(A, size) Shift STDS A with granule ("1 month" or 5) tsnap(A) Snap time instances and intervals of STDS A ``` - - #### Single map with temporal extent The temporal algebra can also handle single maps with time stamps in the diff --git a/temporal/t.vect.algebra/t.vect.algebra.md b/temporal/t.vect.algebra/t.vect.algebra.md index a95f005b281..4083133f5dc 100644 --- a/temporal/t.vect.algebra/t.vect.algebra.md +++ b/temporal/t.vect.algebra/t.vect.algebra.md @@ -274,7 +274,6 @@ aggregation operator: {"comparison operator", "topological relations", aggregation operator, "temporal operator"} ``` - This aggregation operator (\| or &) define the behaviour if a map is related the more than one map, e.g for the topological relations 'contains'. Should all (&) conditions for the related maps be true or is @@ -402,7 +401,7 @@ C = B {&, during} A --> c1 = b1 & a1 c3 = b3 & a1 ``` -### Examples: +### Examples Spatio-temporal intersect all maps from space time dataset A with all maps from space time dataset B which have equal time stamps and are diff --git a/vector/v.distance/v.distance.md b/vector/v.distance/v.distance.md index 679ea8d9be4..42ca31138ed 100644 --- a/vector/v.distance/v.distance.md +++ b/vector/v.distance/v.distance.md @@ -216,6 +216,7 @@ from_cat to_cat dist ```sh v.distance -p from=busroute_a to=busstopsall upload=dist,to_attr to_column=routes format=json ``` + ```sh [ { diff --git a/vector/v.external/v.external.md b/vector/v.external/v.external.md index 4a73aa9befe..7999c14c64f 100644 --- a/vector/v.external/v.external.md +++ b/vector/v.external/v.external.md @@ -72,6 +72,7 @@ v.external input="PG:host=localhost user=postgres dbname=postgis" -l polymap ... ``` + ```sh v.external input="PG:host=localhost user=postgres dbname=postgis" layer=polymap ``` diff --git a/vector/v.extract/v.extract.md b/vector/v.extract/v.extract.md index 1ea36cf7bc4..2633e60df1b 100644 --- a/vector/v.extract/v.extract.md +++ b/vector/v.extract/v.extract.md @@ -22,7 +22,7 @@ or use **layer=-1**. The examples are intended for the North Carolina sample dataset: -### Extract areas by category number with dissolving \#1: +### Extract areas by category number with dissolving \#1 ```sh v.extract -d cats=1,2,3,4 input=soils_wake output=soil_groupa type=area new=0 @@ -33,7 +33,7 @@ vector **soils** which have category numbers **1 thru 4**; any common boundaries are dissolved, and all areas in the new map will be assigned category number 0. -### Extract areas by category number with dissolving \#2: +### Extract areas by category number with dissolving \#2 ```sh v.extract -d cats=1-4 input=soils_wake output=soil_groupa type=area new=-1 @@ -44,7 +44,7 @@ vector **soils** which have categories **1 thru 4**. Any common boundaries are dissolved, all areas in the new map will retain their original category numbers 1 thru 4, since **new** was set to -1. -### Extract all areas and assign the same category to all: +### Extract all areas and assign the same category to all ```sh v.extract input=soils_wake output=soil_groupa type=area new=1 @@ -54,7 +54,7 @@ produces a new vector map **soil_groupa** containing all areas from **soils**. No common boundaries are dissolved, all areas of the new map will be assigned category number 1. -### Extract vectors with SQL: +### Extract vectors with SQL ```sh v.extract input=markveggy.shp output=markveggy.1 new=13 \ @@ -64,19 +64,19 @@ v.extract input=markveggy.shp output=markveggy.1 new=13 \ produces a new vector map with category number 13 if the SQL statement is fulfilled. -### Extract vector features which have the given field empty: +### Extract vector features which have the given field empty ```sh v.extract input=lakes output=lakes_gaps where="FTYPE is NULL" ``` -### Extract vector features which have the given field not empty: +### Extract vector features which have the given field not empty ```sh v.extract input=lakes output=lakes_ftype where="FTYPE not NULL" ``` -### Reverse extracting (behaves like selective vector objects deleting): +### Reverse extracting (behaves like selective vector objects deleting) Remove meteorological stations from map which are located above 1000m: @@ -92,7 +92,7 @@ v.extract -r input=precip_30ynormals output=precip_30ynormals_lowland \ v.db.select precip_30ynormals_lowland ``` -### Dissolving based on column attributes: +### Dissolving based on column attributes ```sh # check column names: diff --git a/vector/v.info/v.info.md b/vector/v.info/v.info.md index e7fd18e54dc..bb996ef5291 100644 --- a/vector/v.info/v.info.md +++ b/vector/v.info/v.info.md @@ -122,6 +122,7 @@ areas=1832 islands=907 primitives=5481 ``` + ```sh v.info -g map=geology diff --git a/vector/v.kcv/v.kcv.md b/vector/v.kcv/v.kcv.md index ea3e87df6b8..8009b765918 100644 --- a/vector/v.kcv/v.kcv.md +++ b/vector/v.kcv/v.kcv.md @@ -33,6 +33,7 @@ All examples are based on the North Carolina sample dataset. g.copy vect=geonames_wake,my_geonames_wake v.kcv map=my_geonames_wake column=part npartitions=10 ``` + ```sh g.copy vect=geodetic_pts,my_geodetic_pts v.kcv map=my_geodetic_pts column=part npartitions=10 diff --git a/vector/v.label/v.label.md b/vector/v.label/v.label.md index abb4d7db23f..1f85cd5b200 100644 --- a/vector/v.label/v.label.md +++ b/vector/v.label/v.label.md @@ -15,7 +15,7 @@ A description of the labels file follows. The file is located in `$MAPSET/paint/labels/`. The file is a plain-text ASCII file containing the following fields: -#### Caution: The following information may be incomplete, out of date, and wrong! +#### Caution: The following information may be incomplete, out of date, and wrong The label information that must be provided in the *labels* file is: @@ -84,11 +84,11 @@ 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: -1. By color name: +1. By color name: `aqua black blue brown cyan gray green grey indigo magenta orange purple red violet white yellow` -2. As red, green, blue component values. (0-255) +2. As red, green, blue component values. (0-255) for example: `128:100:200` -3. Specify "`none`" to suppress the lettering. +3. Specify "`none`" to suppress the lettering. **WIDTH**: This determines the line thickness of the border box. diff --git a/vector/v.net.bridge/v.net.bridge.md b/vector/v.net.bridge/v.net.bridge.md index d162f33bbce..6ef3795a7e3 100644 --- a/vector/v.net.bridge/v.net.bridge.md +++ b/vector/v.net.bridge/v.net.bridge.md @@ -17,7 +17,6 @@ input map to the output map. On the other hand, for **method=articulation**, points are created on the positions of articulation points. - In GRASS GIS, *line* is not always a single line segment. It might be, and often is, a sequence of line segments between two intersections. Also, articulation point is a standard graph theoretic terminology which diff --git a/vector/v.net.connectivity/v.net.connectivity.md b/vector/v.net.connectivity/v.net.connectivity.md index b4be871e3ee..6ad94febca6 100644 --- a/vector/v.net.connectivity/v.net.connectivity.md +++ b/vector/v.net.connectivity/v.net.connectivity.md @@ -23,6 +23,7 @@ separating roads on the left bank from roads on the right bank. v.net.connectivity input=roads output=roads_conn set1_where="bank=left" \ set2_where="bank=right" ``` + ```sh v.net.connectivity input=airtraffic output=connectivity \ set1_where="name=JFK" set2_where="name=Heathrow" node_column=capacity diff --git a/vector/v.net.iso/v.net.iso.md b/vector/v.net.iso/v.net.iso.md index 58943d85e96..657c51533d2 100644 --- a/vector/v.net.iso/v.net.iso.md +++ b/vector/v.net.iso/v.net.iso.md @@ -61,7 +61,7 @@ Isonetwork using time: v.net.iso example with traveling time -#### Subdivision of a network using distance: +#### Subdivision of a network using distance ```sh # Spearfish @@ -101,7 +101,7 @@ d.vect myroads_net_iso col=magenta cats=4 d.vect myroads_net col=red icon=basic/triangle fcol=green size=12 layer=2 ``` -#### Subdivision of a network using traveling time: +#### Subdivision of a network using traveling time Prepare the network as above: diff --git a/vector/v.net/v.net.md b/vector/v.net/v.net.md index 750159f7e9e..059296f7bea 100644 --- a/vector/v.net/v.net.md +++ b/vector/v.net/v.net.md @@ -21,7 +21,7 @@ layer 1) and nodes are stored in a different data layer (normally layer *v.net* offers two ways to add nodes to a network of arcs and one method to add arcs to a set of nodes: -1. Use the *connect* operation to create nodes from a vector points +1. Use the *connect* operation to create nodes from a vector points file and add these nodes to an existing vector network of arcs (i.e., lines/boundaries). This is useful when the goal is to analyze a set of places (points) in relation to a network--for example @@ -37,14 +37,14 @@ to add arcs to a set of nodes: `v.category input=yourmap option=add cat=1 step=1 layer=3 output=newmap` followed by `v.db.addtable map=newmap layer=3 table=tablename`. -2. Create nodes and arcs from a vector line/boundary file using the +2. Create nodes and arcs from a vector line/boundary file using the *node* operation. This is useful if you are mostly interested in the network itself and thus you can use intersections of the network as start and end points. Nodes will be created at all intersections of two or more lines. For an *arc* that consists of several segments connected by vertices (the typical case), only the starting and ending vertices are treated as network nodes. -3. Create straight-line arcs between pairs of nodes with the *arcs* +3. Create straight-line arcs between pairs of nodes with the *arcs* option. This produces networks like those of airline flights between airports. It is also similar to the kind of network created with social networking software, making it possible to create diff --git a/vector/v.normal/v.normal.md b/vector/v.normal/v.normal.md index 6aabcce42f8..b40e98ebf79 100644 --- a/vector/v.normal/v.normal.md +++ b/vector/v.normal/v.normal.md @@ -8,15 +8,15 @@ The tests that *v.normal* performs are indexed below. The tests that are performed are specified by giving an index, ranges of indices, or multiple thereof. -1. Sample skewness and kurtosis -2. Geary's a-statistic and an approximate normal transformation -3. Extreme normal deviates -4. D'Agostino's D-statistic -5. Modified Kuiper V-statistic -6. Modified Watson U^2-statistic -7. Durbin's Exact Test (modified Kolmogorov) -8. Modified Anderson-Darling statistic -9. Modified Cramer-Von Mises W^2-statistic +1. Sample skewness and kurtosis +2. Geary's a-statistic and an approximate normal transformation +3. Extreme normal deviates +4. D'Agostino's D-statistic +5. Modified Kuiper V-statistic +6. Modified Watson U^2-statistic +7. Durbin's Exact Test (modified Kolmogorov) +8. Modified Anderson-Darling statistic +9. Modified Cramer-Von Mises W^2-statistic 10. Kolmogorov-Smirnov D-statistic (modified for normality testing) 11. Chi-Square test statistic (equal probability classes) and the number of degrees of freedom diff --git a/vector/v.out.pov/v.out.pov.md b/vector/v.out.pov/v.out.pov.md index 07497924b13..85107d55652 100644 --- a/vector/v.out.pov/v.out.pov.md +++ b/vector/v.out.pov/v.out.pov.md @@ -1,7 +1,7 @@ ## DESCRIPTION *v.out.pov* converts GRASS vector data to POV-Ray format -(www.povray.com) +() ## EXAMPLE diff --git a/vector/v.patch/v.patch.md b/vector/v.patch/v.patch.md index bb904644167..6c3177707ca 100644 --- a/vector/v.patch/v.patch.md +++ b/vector/v.patch/v.patch.md @@ -42,7 +42,6 @@ Patch together two maps with mixed feature types: v.patch input=geology,streams out=geol_streams ``` - Append one map to another: ```sh diff --git a/vector/v.proj/v.proj.md b/vector/v.proj/v.proj.md index 6b7bfc786f3..20136272280 100644 --- a/vector/v.proj/v.proj.md +++ b/vector/v.proj/v.proj.md @@ -54,11 +54,11 @@ v.proj in=mymap project=latlong mapset=user1 ## REFERENCES -1. Evenden, G.I. (1990) [Cartographic projection procedures for the +1. Evenden, G.I. (1990) [Cartographic projection procedures for the UNIX environment - a user's manual.](https://proj.org) USGS Open-File Report 90-284 (OF90-284.pdf) See also there: Interim Report and 2nd Interim Report on Release 4, Evenden 1994). -2. Richards, John A. (1993), Remote Sensing Digital Image Analysis, +2. Richards, John A. (1993), Remote Sensing Digital Image Analysis, Springer-Verlag, Berlin, 2nd edition. [PROJ](https://proj.org): Projection/datum support library. diff --git a/vector/v.surf.rst/v.surf.rst.md b/vector/v.surf.rst/v.surf.rst.md index b42c140a01f..11867ed8dca 100644 --- a/vector/v.surf.rst/v.surf.rst.md +++ b/vector/v.surf.rst/v.surf.rst.md @@ -124,7 +124,7 @@ There are two options how **tension** can be applied in relation to density so that the size of segments with **segmax=**40 points is around 1 - this ensures the numerical stability of the computation): -1. Default: the given **tension** is applied to normalized data +1. Default: the given **tension** is applied to normalized data (*x/dnorm*), that means that the distances are multiplied (rescaled) by *tension/dnorm*. If density of points is changed, e.g., by using higher **dmin**, the **dnorm** changes and **tension** needs to be @@ -133,7 +133,7 @@ density so that the size of segments with **segmax=**40 points is around 10-100 range and does not depend on the actual scale (distances) of the original data (which can be km for regional applications or cm for field experiments). -2. Flag**-t**: The given **tension** is applied to un-normalized data +2. Flag**-t**: The given **tension** is applied to un-normalized data (rescaled *tension = tension\*dnorm/1000* is applied to normalized data (*x/dnorm*) and therefore **dnorm** cancels out) so here **tension** truly works as a rescaling parameter. For regional diff --git a/vector/v.to.db/v.to.db.md b/vector/v.to.db/v.to.db.md index caa176211e4..eba5dc51c00 100644 --- a/vector/v.to.db/v.to.db.md +++ b/vector/v.to.db/v.to.db.md @@ -110,7 +110,7 @@ v.db.select mysoils layer=2 Compute DL, the Fractal Dimension (Mandelbrot, 1982), of the boundary defining a polygon based on the formula: -` D = 2 * (log perimeter) / (log area):` +`D = 2 * (log perimeter) / (log area):` ```sh g.copy vect=soils,mysoils diff --git a/vector/v.to.rast/v.to.rast.md b/vector/v.to.rast/v.to.rast.md index ba902beb72d..15079110b2c 100644 --- a/vector/v.to.rast/v.to.rast.md +++ b/vector/v.to.rast/v.to.rast.md @@ -77,6 +77,7 @@ Column 1: CAT Column 2: SPEED Column 3: WIDTH ``` + ```sh v.to.rast input=vect_map output=raster_map attribute_column=SPEED type=line ``` diff --git a/vector/v.vol.rst/v.vol.rst.md b/vector/v.vol.rst/v.vol.rst.md index 822304ebb6f..ca9a5c46cba 100644 --- a/vector/v.vol.rst/v.vol.rst.md +++ b/vector/v.vol.rst/v.vol.rst.md @@ -235,7 +235,7 @@ Mitas L., Brown W. M., Mitasova H., 1997, [Role of dynamic cartography in simulations of landscape processes based on multi-variate fields.](http://fatra.cnr.ncsu.edu/~hmitaso/gmslab/lcgfin/cg-mitas.html) Computers and Geosciences, Vol. 23, No. 4, pp. 437-446 (includes CDROM -and WWW: www.elsevier.nl/locate/cgvis) +and WWW: ) Mitasova H., Mitas L.,  Brown W.M.,  D.P. Gerdes, I. Kosinovsky, Baker, T.1995, Modeling spatially and temporally distributed phenomena: New diff --git a/vector/vectorintro.md b/vector/vectorintro.md index 90bed6aa1f8..c309f641083 100644 --- a/vector/vectorintro.md +++ b/vector/vectorintro.md @@ -143,7 +143,7 @@ table linked to a vector map. objects can be added to the geometry file with category numbers. Using [v.category](v.category.md), category numbers can be printed or maintained. - + - **Layers** Layers are a characteristic of the vector feature (geometries) file. As mentioned above, categories allow the user to give either a unique