← Back to home
Comparison · Analytics

sdtm.oak vs sftime

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

Shared themes:r-package

sdtm.oak vs sftime: at a glance

Featuresdtm.oaksftime
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-trials, sdtm, pharmaverse, r-packagespatiotemporal, r-spatial, interoperability, tidyverse-integration
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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 →

What is sftime?

The spatiotemporal companion to sf, moving at the pace of the packages around it.

sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.

Read the full sftime trajectory →

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

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.

S
sftime
ANALYTICS
0.0

The spatiotemporal companion to sf, moving at the pace of the packages around it.

◆ Current state

sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.

◆ Where it's heading

The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.

◆ Prediction

Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.

Alternatives to sdtm.oak and sftime

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

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

Recent activity from sdtm.oak and sftime

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

  1. 3mo agosftimeExamples switched to the native R pipe
  2. 11mo agosftimeFixes the cubble namespace version check
  3. 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release
  4. 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
  5. 1y agosftimeConverts from spatstat, sftrack and cubble objects
  6. 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
  7. 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
  8. 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
  9. 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)

Frequently asked questions

What is the difference between sdtm.oak and sftime?

Both compete on the same themes — r-package — within Analytics. sdtm.oak and sftime 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 sdtm.oak better than sftime?

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

What are the best alternatives to sftime?

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