Computational region

The current region or computational region is the actual setting of the region boundaries and the actual raster resolution.

As a general rule in GRASS:

1. Raster maps are always imported completely at their own resolution (exception: WMS imported layers).
2. Vector maps are always imported completely.
3. In computations,
   1. raster input maps are automatically cropped/padded and rescaled (using nearest neighbour resampling) to match the current region in order to produce the output raster map or to query values.
   2. Raster output maps have their bounds and resolution equal to those of the current computational region.
   3. Vector maps are always considered completely.

FAQs

Q: I don't see anything!

A: Typically the computational region is set to an area not covering the raster map of interest. Use g.region to adjust the computational region settings, e.g. by setting it to the raster map:

 g.region rast=myrastermap -p

Using the graphical user interface:

Set display to selected map:

wxGUI: set map display to selected map (right mouse button context menu on map name)

Set computational region to selected map:

wxGUI: set computational region to selected map (right mouse button context menu on map name)

Q: The raster map looks ugly.

A: The resolution of the computational region does not match the resolution of the raster map. Use g.region to adjust the resolution settings of the computational region or set it to the raster map (see above).

Q: I get "xyz module: G_malloc error"

A: You likely try to use more memory than your computer offers which is commonly caused by a too high raster resolution (or too large computational region). E.g., it is pointless to calculate common DEM data at nanometer raster resolution. Set the region extent and raster resolution properly with g.region (in the wxGUI: menu Settings -> Region -> Display Region | Set Region).