Noam Ross

Implement remaining raster::rasterize options

2

- [ ] mask, update, updateValue - [ ] getCover

Other output targets

1

If there were standardized/widely adopted targets for these, I would consider - [ ] hexagonal grid output - [ ] sparse grid output

It would be good to export a C++ API so that functions and algorithms herein could be used for different reasons, like other output formats (e.g., #11 ). This requires...

Return appropriate types

1

Right now `ratsterize()` data is always `double` it should be integer, vector, or logical if the input data is.

contourize() and polygonize()

1

Functions to convert rasters/stars/matrices to sf. - Use marching squares as implemented in https://github.com/d3/d3-contour/blob/85cd144ce28a0bb5cb5c282604e8c24e23e7c772/src/contours.js - `contourize()`: produce LINESTRINGS with value equal to threshold - `closed=TRUE`: close contours at edges of...

Not in-memory formats to read/write

1

Possibilities: - Raster native and other on-disk formats. If they are straight on-disk binary without compression, should be doable to write without too much effort. Probably would be much enhanced...

Basically, a different version of "sum", per #13, we just need to be clear what happens with NAs. We can also do running variance: https://www.johndcook.com/blog/standard_deviation/ It would not be that...

Errors such as #13 could have more informative error messages, especially when faterize behavior does diverge from rasterize. This might be useful in error message writing: http://style.tidyverse.org/error-messages.html We want to...

In some ways fasterize does diverge from rasterize (e.g., #13). These should be tersely described in the README/vignette and function documentation.

Outputs are not identical to raster::rasterize()

6

Due to some rounding inconsistency, outputs from `fasterize()` are not exactly the same as `rasterize()`, as in the example below. This could be in the implementation of `std::ceil` as opposed...