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

Allow bounds as objects of class Spatial #40

Merged
merged 4 commits into from
Jul 19, 2020

Conversation

LDalby
Copy link
Contributor

@LDalby LDalby commented Aug 9, 2019

Closes #30

This PR builds upon the chunk added in c591d0d by Martin Jung. Only addition is to allow objects of class Spatial (essentially from the {sp} package) also.
This also removes the call to as.vector as this is not needed. A few code formatting changes also.

@stragu
Copy link
Collaborator

stragu commented Jul 19, 2020

Merging this one as it looks good to me and I can see it being very useful.
It throws a warning when running devtools::check(), about sf not being imported, but I will add it as a simple Suggests as we can assume that sf is available if someone has an object of class sf.

@stragu stragu merged commit e13118b into ropensci:master Jul 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow bounds to be a spatial object
2 participants