Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update package to use the "terra" package instead of "raster" #14

Open
calvinkflee opened this issue Sep 19, 2022 · 2 comments
Open

Update package to use the "terra" package instead of "raster" #14

calvinkflee opened this issue Sep 19, 2022 · 2 comments
Assignees

Comments

@calvinkflee
Copy link
Collaborator

While updating the package to use 'sf' instead of 'sp', it is probably also worth updating it to use terra instead of raster.

Will likely be able to improve the performance of some of the slower functions as well.

@AMBarbosa
Copy link

Hi,
Note that 'terra' can also be used for spatial vector data, instead of 'sf'. It's probably easier (thus faster) to update everything for 'terra', rather than for 'terra' (for raster maps) plus 'sf' (for vector maps), which implies loading / depending on more packages and using different syntaxes. See e.g. here.

@calvinkflee
Copy link
Collaborator Author

Terra can now be used for the input for most functions. gridUncertainty still uses raster, as it'll take a lot more time playing with that to update it.

I agree that it's probably more straightforward to stick with terra throughout the package, though having sf as an additional option if some users want it can also be beneficial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants