← Back to home
Comparison · Analytics

osmapiR vs sdtm.oak

A side-by-side editorial comparison of osmapiR and sdtm.oak — release velocity, themes, recent moves, and the top alternatives to consider.

osmapiR vs sdtm.oak: at a glance

FeatureosmapiRsdtm.oak
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, api-client, r-language, geospatialclinical-trials, sdtm, pharmaverse, r-package
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is osmapiR?

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`.

Read the full osmapiR trajectory →

What is sdtm.oak?

Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.

sdtm.oak builds SDTM datasets — the tabulation standard clinical trial submissions are filed in — from raw collected data. The 0.1.0 release shipped the mapping algorithm functions and derived-variable helpers but explicitly excluded DM, trial design domains, and several others. Version 0.2.0 closes the largest of those gaps, adding DM domain support via calc_min_max_date() and oak_calc_ref_dates(), plus generate_sdtm_supp() for supplemental qualifier domains.

Read the full sdtm.oak trajectory →

osmapiR vs sdtm.oak: editorial side-by-side

O
osmapiR
ANALYTICS
0.0

osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.

◆ Current state

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`.

◆ Where it's heading

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.

◆ Prediction

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.

S
sdtm.oak
ANALYTICS
0.0

Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.

◆ Current state

sdtm.oak builds SDTM datasets — the tabulation standard clinical trial submissions are filed in — from raw collected data. The 0.1.0 release shipped the mapping algorithm functions and derived-variable helpers but explicitly excluded DM, trial design domains, and several others. Version 0.2.0 closes the largest of those gaps, adding DM domain support via calc_min_max_date() and oak_calc_ref_dates(), plus generate_sdtm_supp() for supplemental qualifier domains.

◆ Where it's heading

This is the pharmaverse pattern of building submission tooling in the open, one domain class at a time, with the release history running through GitHub release-candidate tags before each CRAN submission. The direction is clear from the domain checklist: start with the mechanically simple Findings and Events domains, then work toward the ones with cross-dataset dependencies. DM and SUPP were the two that most often forced teams back to bespoke code.

◆ Prediction

The remaining exclusions from the 0.1.0 scope — trial design domains, SV, SE, RELREC and the EPOCH variable — are the obvious next targets, with EPOCH likely first since it depends on the reference dates 0.2.0 just added. Expect the same rhythm of release candidates ahead of each CRAN submission.

Alternatives to osmapiR and sdtm.oak

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 sdtm.oak.

See all osmapiR alternatives → · See all sdtm.oak alternatives →

Recent activity from osmapiR and sdtm.oak

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5mo agoosmapiRbbox arguments accept sf and terra objects
  2. 0y agoosmapiRNote search defaults to creation order; JSON for GPX metadata
  3. 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release
  4. 1y agoosmapiRNote subscriptions and user block endpoints added
  5. 1y agoosmapiRChangeset queries gain from and to parameters
  6. 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
  7. 1y agoosmapiRJOSS citation added; single-tag conversion fixed
  8. 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
  9. 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
  10. 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
  11. 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)
  12. 2y agoosmapiRComplete OSM API coverage arrives in one release

Frequently asked questions

What is the difference between osmapiR and sdtm.oak?

They serve adjacent needs but don't currently overlap on shipped themes. osmapiR and sdtm.oak 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.

Is osmapiR better than sdtm.oak?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmapiR and sdtm.oak 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.

What are the best alternatives to osmapiR?

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.

What are the best alternatives to sdtm.oak?

Top sdtm.oak alternatives in Analytics are ranked by recent ship velocity. Browse the "sdtm.oak alternatives" section above for the current picks, or visit /alternatives/sdtm-oak for the full list with editorial commentary on each.