You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{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.
The text was updated successfully, but these errors were encountered:
{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.
The text was updated successfully, but these errors were encountered: