r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of osmapiR and ReLTER — release velocity, themes, recent moves, and the top alternatives to consider.
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
ReLTER provides programmatic access to the eLTER network — the European long-term ecosystem research infrastructure — pulling site metadata, datasets and activities from DEIMS-SDR and enriching them with taxonomic resolution via PESI and WORMS and raster layers from European OpenDataScience. Version 1.0.0 consolidated the function surface and passed into rOpenSci review; 1.1.0 addressed the reviewers' feedback and added vignettes and a Docker install path. Version 2.0.0 was tagged in late 2022 with release notes consisting only of a merge commit message, and nothing has shipped since.
osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.
Four consecutive releases open with the same line — documentation and code updated for server-side changes, cited by OSM wiki revision range. That is a maintainer treating an evolving remote API as a versioned contract and auditing against it each cycle, which is unusual discipline and the main reason to trust this client over a hand-rolled wrapper. The second thread is fitting into R's spatial conventions rather than exposing OSM's, visible in the bbox coercion work and the httr2 upgrades landing with upstream help.
The pattern is stable enough to call: another release synchronised to the next OSM wiki revision range, adding whatever endpoints appeared and adjusting whatever changed shape.
ReLTER provides programmatic access to the eLTER network — the European long-term ecosystem research infrastructure — pulling site metadata, datasets and activities from DEIMS-SDR and enriching them with taxonomic resolution via PESI and WORMS and raster layers from European OpenDataScience. Version 1.0.0 consolidated the function surface and passed into rOpenSci review; 1.1.0 addressed the reviewers' feedback and added vignettes and a Docker install path. Version 2.0.0 was tagged in late 2022 with release notes consisting only of a merge commit message, and nothing has shipped since.
The visible arc runs from a scattered set of getSite* functions to a reviewed, documented package, and then stops. The absence of notes on the 2.0.0 tag makes it impossible to say from this feed what that major version changed, and the three-year silence afterwards is the more informative signal. What the package does remains useful — the eLTER data it wraps has no other R interface — but the release history gives no evidence of active development.
Nothing in these entries supports a confident prediction about future releases; the feed shows a major version with no notes followed by silence. Whether the package is dormant or simply publishing releases elsewhere cannot be determined from what is here.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either osmapiR or ReLTER.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all osmapiR alternatives → · See all ReLTER alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. osmapiR and ReLTER are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmapiR and ReLTER are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top osmapiR alternatives in Analytics are ranked by recent ship velocity. Browse the "osmapiR alternatives" section above for the current picks, or visit /alternatives/osmapir for the full list with editorial commentary on each.
Top ReLTER alternatives in Analytics are ranked by recent ship velocity. Browse the "ReLTER alternatives" section above for the current picks, or visit /alternatives/relter for the full list with editorial commentary on each.