arcgisutils
R-ArcGIS Bridge Utility Functions
Description
Developer oriented utility functions designed to be used as the building blocks of R packages that work with ArcGIS Location Services. It provides functionality for authorization, Esri JSON construction and parsing, as well as other utilities pertaining to geometry and Esri type conversions. To support 'ArcGIS Pro' users, authorization can be done via 'arcgisbinding'. Installation instructions for 'arcgisbinding' can be found at <https://developers.arcgis.com/r-bridge/installation/>.
Downloads
2.1K
Last 30 days
2866th
4.6K
Last 90 days
14.7K
Last year
Trend: +53% (30d vs prior 30d)
CRAN Check Status
Show all 14 flavors
| Flavor | Status |
|---|---|
| r-devel-linux-x86_64-debian-clang | NOTE |
| r-devel-linux-x86_64-debian-gcc | NOTE |
| r-devel-linux-x86_64-fedora-clang | NOTE |
| r-devel-linux-x86_64-fedora-gcc | NOTE |
| r-devel-macos-arm64 | OK |
| r-devel-windows-x86_64 | NOTE |
| r-oldrel-macos-arm64 | NOTE |
| r-oldrel-macos-x86_64 | NOTE |
| r-oldrel-windows-x86_64 | NOTE |
| r-patched-linux-x86_64 | NOTE |
| r-release-linux-x86_64 | OK |
| r-release-macos-arm64 | OK |
| r-release-macos-x86_64 | OK |
| r-release-windows-x86_64 | OK |
Check details (9 non-OK)
compiled code
File ‘arcgisutils/libs/arcgisutils.so’: Found non-API call to R: ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
compiled code
File ‘arcgisutils/libs/arcgisutils.so’: Found non-API call to R: ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
compiled code
File ‘arcgisutils/libs/arcgisutils.so’: Found non-API call to R: ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
compiled code
File ‘arcgisutils/libs/arcgisutils.so’: Found non-API call to R: ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
compiled code
File 'arcgisutils/libs/x64/arcgisutils.dll': Found non-API call to R: 'R_UnboundValue' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points.
package dependencies
Package suggested but not available for checking: ‘arcgisbinding’
package dependencies
Package suggested but not available for checking: ‘arcgisbinding’
package dependencies
Package suggested but not available for checking: 'arcgisbinding'
compiled code
File ‘arcgisutils/libs/arcgisutils.so’: Found non-API calls to R: ‘R_MissingArg’, ‘R_UnboundValue’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points.
Check History
NOTE 11 OK · 3 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Mar 10, 2026
package dependencies
Package suggested but not available for checking: ‘arcgisbinding’
package dependencies
Package suggested but not available for checking: ‘arcgisbinding’
package dependencies
Package suggested but not available for checking: 'arcgisbinding'