← Back to home
Comparison · Infra & APIs

onemap vs sdcHierarchies

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

onemap vs sdcHierarchies: at a glance

FeatureonemapsdcHierarchies
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesgenetic-mapping, linkage-analysis, genotyping-by-sequencing, mappolydisclosure-control, hierarchies, rcpp, performance
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is onemap?

A genetic-mapping mainstay that now points new users toward MAPpoly at load time

OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.

Read the full onemap trajectory →

What is sdcHierarchies?

Hierarchy tooling for statistical disclosure control keeps trading R for Rcpp.

sdcHierarchies builds and manipulates the nested code hierarchies that statistical disclosure control depends on. Its release history is dominated by one theme: moving tree work into C++ and reporting the speedup. The March 2026 release adds hier_create_ids() for mapping microdata onto hierarchy levels by integer index, and extends hier_grid() with contributing-cell aggregation.

Read the full sdcHierarchies trajectory →

onemap vs sdcHierarchies: editorial side-by-side

O
onemap
INFRA · APIS
0.0

A genetic-mapping mainstay that now points new users toward MAPpoly at load time

◆ Current state

OneMap constructs genetic linkage maps for experimental crosses, and its 3.x line turned it into a hub in a wider mapping toolchain: export functions for VIEWpoly and QTLpoly, summary and interactive ordering functions adapted from MAPpoly, and retention of reference and alternative allele information from imported VCFs. The most recent release, 3.2.0 in January 2025, adds an announcement about MAPpoly to the README and the package load message, fixes a subscript-out-of-bounds warning in rf_2pts and refreshes vignettes and tests.

◆ Where it's heading

Versions 3.0.0 and 3.1.0 were driven by a benchmarking preprint on genotyping-by-sequencing best practice, and their content follows directly: marker filtering from two-point estimates, memory reduction after filtering, and optimisation of find_bins and map_avoid_unlinked. What has happened since is signposting rather than capability — a package that spent two releases integrating with MAPpoly now tells users about it every time it loads. The pre-3.0 tags are backfilled, with versions 2.3 through 2.7 sharing a single August 2021 timestamp, so their order carries no information.

◆ Prediction

The load-message announcement suggests attention is flowing toward the MAPpoly side of the toolchain; expect maintenance and compatibility releases here rather than new mapping algorithms.

S
sdcHierarchies
INFRA · APIS
0.0

Hierarchy tooling for statistical disclosure control keeps trading R for Rcpp.

◆ Current state

sdcHierarchies builds and manipulates the nested code hierarchies that statistical disclosure control depends on. Its release history is dominated by one theme: moving tree work into C++ and reporting the speedup. The March 2026 release adds hier_create_ids() for mapping microdata onto hierarchy levels by integer index, and extends hier_grid() with contributing-cell aggregation.

◆ Where it's heading

Four of the last five releases are performance releases, and each names the specific function that got faster: hier_convert(), then hier_codes(), then the core tree traversal itself. The direction is toward handling hierarchies large enough that the R-level implementation stopped being viable, with the new integer-indexed ID mapping pointing the same way. Feature work rides along with the optimisation rather than driving it.

◆ Prediction

Expect the remaining R-level tree operations to follow hier_convert() and hier_codes() into Rcpp, and the new hier_grid() arguments to accumulate defaults as the aggregation path gets exercised.

Alternatives to onemap and sdcHierarchies

Other Infra & APIs 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 onemap or sdcHierarchies.

See all onemap alternatives → · See all sdcHierarchies alternatives →

Recent activity from onemap and sdcHierarchies

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

  1. 5mo agosdcHierarchieshier_create_ids() maps microdata to hierarchy levels by integer index
  2. 1y agosdcHierarchieshier_codes() rewritten for speed
  3. 1y agosdcHierarchieshier_import() gains keep_order to preserve node order
  4. 1y agoonemapMAPpoly announcement added to README and load message
  5. 3y agosdcHierarchieshier_convert() rewritten for speed
  6. 3y agoonemapExports to VIEWpoly and QTLpoly; marker ordering and map summaries
  7. 3y agoonemapTwo-point marker filtering and memory reduction
  8. 4y agosdcHierarchiesBogus-code computation fixed
  9. 4y agoonemapPSOCK and FORK parallelization choice; vcfR as an import
  10. 5y agoonemaphmm=FALSE option for ordering algorithms
  11. 5y agoonemapMDSMap dependency removed

Frequently asked questions

What is the difference between onemap and sdcHierarchies?

They serve adjacent needs but don't currently overlap on shipped themes. onemap and sdcHierarchies 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 onemap better than sdcHierarchies?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. onemap and sdcHierarchies 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to onemap?

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

What are the best alternatives to sdcHierarchies?

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