You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fasterize is a great package and I used it intensively with the couple sf/raster. But raster became terra. I checked for different cases, and fasterize is still very competitive in runtime with terra:rasterize (see an example below). But all of the fasterize time savings (and more) are lost in conversions between classes. Thus, it would be useful if fasterize could accept indifferently a vector of sf or SpatVector type, and a raster of raster or terra flavor as input. Is this conceivable?
it will take a fair bit of work to set up the writing out of blocks to a file. It's on my radar but with no timeline.
I'd prefer to fold the fasterize logic into GDAL itself, then it would be available to terra and other packages automatically also with memory management.
fasterize
is a great package and I used it intensively with the couplesf/raster
. Butraster
becameterra
. I checked for different cases, andfasterize
is still very competitive in runtime withterra:rasterize
(see an example below). But all of the fasterize time savings (and more) are lost in conversions between classes. Thus, it would be useful iffasterize
could accept indifferently a vector ofsf
orSpatVector
type, and a raster ofraster
orterra
flavor as input. Is this conceivable?The text was updated successfully, but these errors were encountered: