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 to be a spatial object #30

Closed
LDalby opened this issue May 30, 2019 · 0 comments · Fixed by #40
Closed

Allow bounds to be a spatial object #30

LDalby opened this issue May 30, 2019 · 0 comments · Fixed by #40

Comments

@LDalby
Copy link
Contributor

LDalby commented May 30, 2019

The get_inat_obs function accepts a bounds argument where the user can specify a bounding box within which to search for observations.

I wonder if it would be possible to allow this to be a spatial object, say a simple feature (sf)? I guess that you often have some kind of spatial object (country or state boundary for example) that you'd use for visualization after having downloaded the observations.

The downside would be that it adds sf as a dependency, but on the other hand if sf were imported, then inat_map could be modified to use geom_sf.

Just a suggestion, please feel free to close this issue if you think it is a bad idea. I'm happy to take a shot at a PR implementing it if you'd like.

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 a pull request may close this issue.

1 participant