OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A side-by-side editorial comparison of n2khab and treeshap — release velocity, themes, recent moves, and the top alternatives to consider.
n2khab keeps retracting interpretations of habitat data it can't actually support
n2khab reads and prepares the standardised Flemish Natura 2000 habitat data sources — habitat maps, water surfaces, GRTS master grids — for reproducible analysis. Releases track the publication of new versioned data sources on Zenodo, but the more consequential ones change how the package interprets what it reads. The latest removes an argument outright after the reasoning behind it was found to be wrong.
treeshap keeps widening its tree-model coverage while the SHAP math stays put.
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
n2khab reads and prepares the standardised Flemish Natura 2000 habitat data sources — habitat maps, water surfaces, GRTS master grids — for reproducible analysis. Releases track the publication of new versioned data sources on Zenodo, but the more consequential ones change how the package interprets what it reads. The latest removes an argument outright after the reasoning behind it was found to be wrong.
Two forces shape the package. The first is external: each new habitatmap or watersurfaces vintage needs a supported reader, and the package has absorbed a steady stream of them. The second is a willingness to break its own API when the ecology does not support what the code claimed — the interpreted argument removed because type 3130 occurrences cannot be resolved to a single subtype, the rbbvos+ type dropped as too loosely defined, the collapse default changed to match how users actually need the output shaped. Return structures are also being normalised so element names no longer vary with data source version.
The package has said it expects future watersurfaces_hab versions to implement collapsing in the data source itself, so the corresponding argument is a candidate for removal once that lands — the same path the interpreted argument took.
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
The direction is breadth of model support rather than new explanation methods: every release since the first CRAN submission adds or repairs a unify() backend. Maintenance is community-driven, with named contributors fixing the framework they personally use. Nothing in these entries points at work on the SHAP algorithms themselves.
Expect the next release to add or repair another unify() adapter as a contributor brings their own framework, rather than to change how explanations are computed.
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 n2khab or treeshap.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
A discrete global grid generator grew cell traversal and became a usable spatial index.
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all n2khab alternatives → · See all treeshap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. n2khab and treeshap 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. n2khab and treeshap 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 n2khab alternatives in Analytics are ranked by recent ship velocity. Browse the "n2khab alternatives" section above for the current picks, or visit /alternatives/n2khab for the full list with editorial commentary on each.
Top treeshap alternatives in Analytics are ranked by recent ship velocity. Browse the "treeshap alternatives" section above for the current picks, or visit /alternatives/treeshap for the full list with editorial commentary on each.