osrm.backend 0.4.0
CRAN release: 2026-07-11
Major Changes
- Now shipping self-built, self-contained, immutable OSRM releases for all supported platforms — macOS (Intel x86_64 & Apple Silicon arm64 — Mac computers), Linux (x86_64 & arm64), and Windows (x86_64). Binaries are bundled with required runtime libraries (e.g., Intel TBB), fully tested and validated by the package maintainer and available via the default binaries provider to simplify secure installs.
- Introduced
osrm_binaries_providerargument toosrm_install()(default: “default”). This automatically fetches static, highly-compatible binaries built directly by this package’s maintainer (e-kotov/osrm-binaries). These binaries provide native arm64 and x86_64 builds where available across Linux, macOS (Apple Silicon and Intel) and Windows, and bundle required runtime libraries (e.g., Intel TBB) to avoid legacy runtime hacks and reduce overhead by dropping unnecessary NodeJS wrappers. The original upstream binaries remain fully supported viaosrm_binaries_provider = "official". - Added
download_urlandfile_pathparameters toosrm_install()to support advanced/manual installations from a supplied archive URL or a local tarball path. These parameters are intended for advanced users who need explicit control over the installation source. - Switched binary integrity verification to use GitHub release asset digests first, with
checksums.txtas a fallback, ensuring installation security without requiring R package updates when new binary builds are released. - Marked all currently published immutable OSRM binary releases through
v26.7.3as validated byosrm.backend.
Bug fixes
- Heavily optimized GitHub API rate limit handling during installation. When fetching known versions from the default provider, the package now bypasses API checks entirely by directly constructing asset URLs.
- Increased stability of the live integration tests against custom routing instances and proxy-blocked networks.
- Fixes for install process of OSRM binaries v26+ on Windows.
- Added weekly cross-provider integration tests (
tests/testthat/test-compatibility.R) to automatically verify that custom binaries produce identical routing results and are fully cross-compatible with official releases.
osrm.backend 0.3.0
CRAN release: 2026-04-19
New features
- Added
osrm_gui(), an interactive Shiny web application for exploring and visualizing the loaded OSRM routing network. It comes with auto-centering logic to reliably detect the source OSM PBF file or retrieve the extent from the server registry or server object for auto extent.
Improvements
Improved
osrm_servers()with a custom S3 print method for better interactive readability and a newoutputargument to return raw metadata as a list.Simplified server IDs in the registry to
osrm-{port}-{pid}format for better readability and programmatic access.OSRM servers and running OSRM servers registry maintained by the package pre-save the extent info for
osrm_gui()to use it for auto-centering.Added a helpful hint to
osrm_start()error messages when a graph is detected to be incompatible with the currently installed OSRM version.Validated and added official support for OSRM
v26.4.0andv26.4.1releases, ensuring the necessary runtime libraries (TBB and BZip2) are correctly fetched and patched across all supported platforms (macOS, Windows, and Linux).Weekly live tests to check for potential regressions, successful OSRM binaries installation and possible issues when new versions of OSRM backend binaries.
osrm.backend 0.2.0
CRAN release: 2026-02-06
Breaking Changes
The
osrm.server.log_fileoption no longer accepts a list for separate stdout/stderr files. This feature has been removed due to potential deadlock issues. Use a single character path instead:options(osrm.server.log_file = "path/to/logfile.log"). If a list is provided, it will silently fall back to the default temporary file behavior.Default logging behavior changed:
osrm_start_server()now writes logs to a temporary file by default instead of using pipes. This prevents deadlocks in R’s single-threaded environment while preserving logs for debugging. Useverbose = TRUEto see output in the console.
