← Back to home
Comparison · Analytics

sdtm.oak vs USAboundaries

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

sdtm.oak vs USAboundaries: at a glance

Featuresdtm.oakUSAboundaries
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-trials, sdtm, pharmaverse, r-packagegeospatial, census-data, sf, boundary-data
Last editorial update3h ago51m 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 USAboundaries?

Seven years dormant, then two releases dragging every census boundary from 2020 to 2024

USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.

Read the full USAboundaries trajectory →

sdtm.oak vs USAboundaries: 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.

U
USAboundaries
ANALYTICS
0.0

Seven years dormant, then two releases dragging every census boundary from 2020 to 2024

◆ Current state

USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.

◆ Where it's heading

For a data package the release cycle is the data vintage, and the 0.3.0 split into a separate data package was designed precisely so those refreshes would not require a code release. That the 2024 update still arrived as two package versions seven years later says the mechanism is being used sparingly. Nothing in the feed shows work on the API itself since us_cities() gained an sf return type and a states argument in 2018.

◆ Prediction

The next release is most likely another vintage refresh when the census data moves again, rather than new geographies or functions. The split of 0.5.0 and 0.5.1 suggests state boundaries are handled on a separate path from the rest and may lag again.

Alternatives to sdtm.oak and USAboundaries

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

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

Recent activity from sdtm.oak and USAboundaries

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

  1. 9mo agoUSAboundariesState boundaries updated to the 2024 census vintage
  2. 10mo agoUSAboundariesCensus data refreshed to 2024, states excepted
  3. 1y agosdtm.oaksdtm.oak v0.2.0 CRAN release
  4. 1y agosdtm.oaksdtm.oak v0.1.1 CRAN release
  5. 1y agosdtm.oaksdtm.oak v0.1.0 CRAN release
  6. 1y agosdtm.oakv0.1.0rc4: [skip vbump] 90 cran comments (#91)
  7. 2y agosdtm.oakv0.1.0rc2: Fix CRAN Comments (#84)
  8. 2y agosdtm.oakv0.1.0: [skip vbump] Bump version for cran release (#77)
  9. 8y agoUSAboundariesus_cities() returns sf and gains a states argument
  10. 9y agoUSAboundariesData split into a companion package; all boundaries become sf
  11. 9y agoUSAboundariesContemporary state, county and district boundaries added

Frequently asked questions

What is the difference between sdtm.oak and USAboundaries?

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

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

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