tm_facets_wrap()
specify facets for one grouping variable (so one faceting dimension).tm_facets_(hv)stack()
stacks the facets either horizontally or vertically (one grouping variable).tm_facets_grid()
supports up to three faceting dimensions.tm_facets_pagewise()
can be used to replace the oldalong
argument.tm_facets_flip()
can be used to flip facets.tm_facets()
is the core function, but it is recommended to use the other functions.
Usage
tm_facets(
by = NULL,
rows = NULL,
columns = NULL,
pages = NULL,
as.layers = FALSE,
nrow = NA,
ncol = NA,
byrow = TRUE,
orientation = NA,
free.coords = NA,
drop.units = TRUE,
drop.empty.facets = TRUE,
drop.NA.facets = FALSE,
sync = TRUE,
na.text = NA,
scale.factor = 2,
type = NA,
along = NULL,
free.scales = NULL,
...
)
tm_facets_grid(rows = NULL, columns = NULL, pages = NULL, ...)
tm_facets_wrap(by = "VARS__", nrow = NA, ncol = NA, byrow = TRUE, ...)
tm_facets_pagewise(by = "VARS__", nrow = 1, ncol = 1, byrow = TRUE, ...)
tm_facets_stack(by = "VARS__", orientation = NA, ...)
tm_facets_hstack(by = "VARS__", ...)
tm_facets_vstack(by = "VARS__", ...)
tm_facets_flip(...)
Arguments
- by
Group by variable (only for a facet wrap or facet stack)
- rows
Variable that specifies the rows (only for a facet grid)
- columns
Variable that specifies the columns (only for a facet grid)
- pages
Variable that specifies the pages (only for a facet grid)
- as.layers
show facets as layers?
- nrow
Number of rows
- ncol
Number of columns
- byrow
Should facets be wrapped by row?
- orientation
For facet stack: horizontal or vertical?
- free.coords
Logical. If the
by
argument is specified, should each map has its own coordinate ranges? By defaultTRUE
, unless facets are shown in as different layers (as.layers = TRUE
)- drop.units
Logical. If the
by
argument is specified, should non-selected spatial units be dropped? IfFALSE
, they are plotted where mapped aesthetics are regarded as missing values. Not applicable for raster shapes. By defaultTRUE
.- drop.empty.facets
Logical. If the
by
argument is specified, should empty facets be dropped? Empty facets occur when theby
-variable contains unused levels. WhenTRUE
and twoby
-variables are specified, empty rows and columns are dropped.- drop.NA.facets
Logical. If the
by
argument is specified, and all data values for specific facets are missing, should these facets be dropped?FALSE
by default. In v3, it was calledshowNA
.- sync
Logical. Should the navigation in view mode (zooming and panning) be synchronized? By default
TRUE
if the facets have the same bounding box. This is generally the case when rasters are plotted, or whenfree.coords
isFALSE
.- na.text
Text used for facets of missing values. In v3, it was
textNA
.- scale.factor
Number that determines how the elements (e.g. font sizes, symbol sizes, line widths) of the small multiples are scaled in relation to the scaling factor of the shapes. The elements are scaled to the
scale.factor
th root of the scaling factor of the shapes. So, forscale.factor=1
, they are scaled proportional to the scaling of the shapes. Since elements, especially text, are often too small to read, a higher value is recommended. By default,scale.factor=2
.- type
"grid"
,"wrap"
or"stack"
- along
deprecated Please use
tm_facets_pagewisse()
- free.scales
deprecated. Please use the
.free
arguments in the layer functions, e.g.fill.free
intm_polygons
.- ...
passed on to
tm_facets()