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

consider moving {sf} to Suggests #47

Open
JosiahParry opened this issue Apr 27, 2024 · 0 comments
Open

consider moving {sf} to Suggests #47

JosiahParry opened this issue Apr 27, 2024 · 0 comments

Comments

@JosiahParry
Copy link
Collaborator

{sf} vendors GDAL, GEOS, and PROJ making it a massive R package. The {wk} package is very small and very lightweight and can operate on different geometry types.

It could be used instead of {sf} in many places. Where it is not possible to replace it, we can guard code execution with rlang::check_installed().

Working on {arcgisplaces}, I am thinking about how it may be used in production grade shiny applications. Since it is build mostly on Rust and httr2 it is fairly lightweight and it returns sf objects without actually having to have the package available (thank you S3 class system).

{sf} could be suggested, but shouldn't be required. Adding 300mb to a Docker container can be a limiting factor for creating a production ready application.

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

No branches or pull requests

1 participant