---
title: "Sheet Geometry"
output: rmarkdown::html_vignette
vignette: >
  %\VignetteIndexEntry{Sheet Geometry}
  %\VignetteEngine{knitr::rmarkdown}
  %\VignetteEncoding{UTF-8}
---

```{r include = FALSE}
knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>"
)
options(tibble.print_min = 4, tibble.print_max = 4)
```

```{r setup}
library(readxl)
```

`readxl::read_excel()` brings data from a rectangle of cells into R as a data frame or, more specifically, a [tibble](https://tibble.tidyverse.org/reference/tibble.html).

The extent of the data rectangle can be determined in various ways:

  * **Discovered**: By default, `read_excel()` uses the smallest rectangle that contains the non-empty cells. It "shrink wraps" the data.
  * **Bounded**: The `skip` and `n_max` arguments constrain `read_excel()`'s discovery process with respect to rows. At least `skip` spreadsheet rows will be skipped or ignored and at most `n_max` spreadsheet rows will be considered as data. Compared to the default of **discovery**, these arguments can only lead to making the output tibble smaller.
  * **Set**: The `range` argument is taken literally, even if that means you will have leading or trailing rows or columns filled with `NA`. If you ask for `range = "A1:D4"`, you are guaranteed to get a tibble with 4 columns (A through D) and either 3 rows (`col_names = TRUE`, default) or 4 rows (`col_names = FALSE`).
  * **Mixed**: In typical use, `read_excel()`'s geometry arguments often imply that certain limits are **discovered** while others are **bounded** or **set**. This will be more clear in the concrete examples below.

For now, here are a few ways `read_excel()` can look when you take control of the geometry:

```{r eval = FALSE}
read_excel("yo.xlsx", skip = 5)
read_excel("yo.xlsx", n_max = 100)
read_excel("yo.xlsx", skip = 5, n_max = 100)
read_excel("yo.xlsx", range = "C1:E7")
read_excel("yo.xlsx", range = cell_rows(6:23))
read_excel("yo.xlsx", range = cell_cols("B:D"))
read_excel("yo.xlsx", range = anchored("C4", dim = c(3, 2)))
```

## Little known Excel facts

readxl's behavior and interface may be easier to understand if you understand this about Excel:

> Cells you can see don't necessarily exist. Cells that look blank aren't necessarily so.

Among lots of other information, Excel files obviously must contain information on each cell. Let's use the word "item" to denote one cell's-worth of info.

Just because you see a cell on the screen in Excel, that doesn't mean there's a corresponding item on file. Why? Because Excel presents a huge gridded canvas for you to write on. Until you actually populate a cell, though, it doesn't really exist.

The stream of cell items describes the existing cells, going from upper left to lower right, travelling by row. Blank cells simply do not exist in it.

Ah, but what is a blank cell? Some cells appear blank to the naked eye but are not considered so by Excel and, indeed, are represented by a cell item. This happens when a cell has no content but does have an associated format. This format could have been applied directly to a single cell or, more often, indirectly via formatting applied to an entire row or column. Once a human has spent some quality time with a spreadsheet, many seemingly empty cells will bear a format and will thus have an associated cell item.

### Implications for readxl

readxl only reads cell items that have content. It ignores cell items that exist strictly to convey formatting.

The tibble returned by readxl will often cover cells that are empty in the spreadsheet, filled with `NA`. But only because there was some other reason for the associated row or column to exist: actual data or user-specified geometry.

## `skip` and `n_max`

`skip` and `n_max` are the "entry-level" solution for controlling the data rectangle. They work only in the row direction. Column-wise, you're letting readxl discover which columns are populated.

If you specify `range` (covered below), `skip` and `n_max` are ignored.

### `skip`

The `skip` argument tells `read_excel()` to start looking for populated cells after skipping at least `skip` rows. If the new start point begins with 1 or more empty rows, `read_excel()` will skip even more before it starts reading from the sheet.

Here's a screen shot of the `geometry.xlsx` example sheet that ships with readxl, accessible via `readxl_example("geometry.xlsx")`.

```{r out.width = '70%', echo = FALSE}
#| fig-alt: Screenshot of the 'geometry.xlsx' example spreadsheet. The cells in
#|     the range B3:D6 are populated, each with the string of the cell's
#|     address. For example, the cell B3 contains the string 'B3'.
knitr::include_graphics("img/geometry.png")
```

By default, `read_excel()` just discovers the data rectangle:

```{r}
read_excel(readxl_example("geometry.xlsx"))
```

If you explicitly skip one row, note that `read_excel()` still skips row 2, which is also empty, leading to the same result as before:

```{r}
read_excel(readxl_example("geometry.xlsx"), skip = 1)
```

You can also use `skip` to skip over populated cells. In real life, this is a mighty weapon against the explanatory text that people like to include at the top of spreadsheets.

```{r}
read_excel(readxl_example("geometry.xlsx"), skip = 3)
```

Summary: `skip` tells `read_excel()` to skip *at least this many* spreadsheet rows before reading anything.

### `n_max`

The `n_max` argument tells `read_excel()` to read at most `n_max` rows, once it has found the data rectangle. Note that `n_max` is specifically about *the data*. You still use `col_names` to express whether the first spreadsheet row should be used to create column names (default is `TRUE`).

`n_max = 2` causes us to ignore the last data row -- the 3rd one -- in `geometry.xlsx`.

```{r}
read_excel(readxl_example("geometry.xlsx"), n_max = 2)
```

`n_max` is an upper bound. It will never cause empty rows to be included in the tibble. Note how we get 3 data rows here, even though `n_max` is much greater.

```{r}
read_excel(readxl_example("geometry.xlsx"), n_max = 1000)
```

## `range`

The `range` argument is the most flexible way to control geometry and is powered by the [cellranger](https://github.com/rsheets/cellranger#readme) package. 

One huge difference from `skip` and `n_max` is that `range` is taken literally! Even if it means the returned tibble will have entire rows or columns consisting of `NA`.

You can describe cell limits in a variety of ways:

**Excel-style range**: Specify a fixed rectangle with `range = "A1:D4"` or `range = "R1C1:R4C4"`. You can even prepend the worksheet name like so: `range = "foofy!A1:D4"` and it will be passed along to the `sheet` argument.

The `deaths.xlsx` example sheet features junk rows both before and after the data rectangle. The payoff for specifying the data rectangle precisely is that we get the data frame we want, with correct guesses for the column types.

```{r}
read_excel(readxl_example("deaths.xlsx"), range = "arts!A5:F15")
```

We repeat the screenshot of `geometry.xlsx` as a visual reference.

```{r out.width = '70%', echo = FALSE}
#| fig-alt: Screenshot of the 'geometry.xlsx' example spreadsheet. The cells in
#|     the range B3:D6 are populated, each with the string of the cell's
#|     address. For example, the cell B3 contains the string 'B3'.
knitr::include_graphics("img/geometry.png")
```

Going back to `geometry.xlsx`, here we specify a rectangle that only partially overlaps the data. Note the use of default column names, because the first row of cells is empty, and the leading column of `NA`s.

```{r}
read_excel(readxl_example("geometry.xlsx"), range = "A2:C4")
```

**Specific range of rows or columns**: Set exact limits on just the rows or just the columns and allow the limits in the other direction to be discovered. Example calls:

```{r eval = FALSE}
## rows only
read_excel(..., range = cell_rows(1:10))
## is equivalent to
read_excel(..., range = cell_rows(c(1, 10)))

## columns only
read_excel(..., range = cell_cols(1:26))
## is equivalent to all of these
read_excel(..., range = cell_cols(c(1, 26)))
read_excel(..., range = cell_cols("A:Z"))
read_excel(..., range = cell_cols(LETTERS))
read_excel(..., range = cell_cols(c("A", "Z"))
```

We use `geometry.xlsx` to demonstrate setting hard limits on the rows, running past the data, while allowing column limits to discovered. Note the trailing rows of `NA`.

```{r}
read_excel(readxl_example("geometry.xlsx"), range = cell_rows(4:8))
```

**Anchored rectangle**: Helper functions `anchored()` and `cell_limits()` let you specify limits via the corner(s) of the rectangle.

Here we get a 3 by 4 rectangle with cell C5 as the upper left corner:

```{r}
read_excel(
  readxl_example("geometry.xlsx"),
  col_names = paste("var", 1:4, sep = "_"),
  range = anchored("C5", c(3, 4))
)
```

Here we set C5 as the upper left corner and allow the other limits to be discovered:

```{r}
read_excel(
  readxl_example("geometry.xlsx"),
  col_names = FALSE,
  range = cell_limits(c(5, 3), c(NA, NA))
)
```

