Jakub
Jakub
For now, it fixes my issue -- I will play with the tick argument. I do not have any strong suggestions here.
My general thinking is that `raster.max.cells` should relate to each panel separately (that would be my expectation as a user). Currently, when you have one panel, the map is fine;...
Hi @mtennekes -- I mainly use the default style, so I do not have strong feelings about other styles. The `"bw"` one is also nice, as it may show how...
@mtennekes close?
@JeremyGelb thanks for opening the new issue. Could you propose a pull request adding this package to the task view?
- Keeping up with the naming of the other layers' functions -- `tm_paths()` seems good (plural) - I think that, in general, it would be preferable to put such functions...
@maltenform It seems to be working when you remove `encapsulate = "evaluate"` (however, I cannot explain why this happens; maybe relates to https://github.com/mlr-org/mlr3/pull/1109/files ??, @jannes-m ) ```r progressr::with_progress(expr = {...
@jannes-m I do not fully understand the discussion in the related issue... Do we need to change anything in the book?
Thanks @mtennekes -- I just looked at each use of `tm_facets` in geocompr and we consistently use "nrow" and "ncol" there (nrows and ncols were not used). Update: actually --...
@mtennekes -- what should be the default in such cases? I (for aesthetic reasons mostly) prefer the first map. Also see the following examples (especially in the last two cases,...