Dan Baston
Dan Baston
Currently you'd need to either loop through the bands or use the R package.
I think the assumption of "each feature has a single ID field" is pretty baked in. Of course that can be changed, but I'm not sure it's worth the complexity....
This is available in `exactextractr` (https://github.com/isciences/exactextractr/blob/master/NEWS.md) but has not been exposed in the CLI.
The syntax in the example is correct, though there's clearly room for improvement in the documentation. `exactextract` uses brackets to indicate a band number with a raster (e.g. `prec_december:prec.tif[12]`) or...
It seems to cause an infinite loop in MSVC for some reason. (https://github.com/libgeos/geos/runs/4477323616?check_suite_focus=true)
The "infinite loop" turned out to be the result of MSVC trying to pop up an "assertion failed" dialog box on an Azure server somewhere with nobody to click "OK."...
> Instead of a one-line call I don't think it has to be an either/or - you can cover common cases with functions like `GEOSBuffer` and use a params object...
However you prefer to do it is good by me. Thanks!
Thanks! Here are my suggestions: - instead of creating local variables for the test geometries, use the built-in member variables `geom1_`, `geom2_`, etc. These will be automatically cleaned up, so...
I see the appeal but am not sure it's worth it, since the non-`_r` functions are just trivial wrappers around the `_r` versions.