TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of impIndicator and qualpalr — release velocity, themes, recent moves, and the top alternatives to consider.
Biodiversity impact indicators settle their vocabulary before 1.0
impIndicator computes indicators of alien-species impact from GBIF-style occurrence cubes, producing species-level, site-level and regional measures with visualisation. The latest release renames the three headline functions to compute_species_indicator(), compute_site_indicator() and compute_regional_indicator(), drops the division by total occupied sites, and fixes the exponential transformation of impact categories into scores. It is part of the b-cubed-eu family and leans on sibling tooling rather than reimplementing it.
A palette generator became a palette platform — and changed the metric behind every color it picks.
qualpalr generates maximally distinct categorical color palettes by optimizing perceptual distance, with adaptation for color vision deficiency built in from early on. Version 1.0.0 in August 2025 ended an eight-year stretch of small maintenance releases: the color-difference metric became selectable, existing palettes from ColorBrewer and Tableau became usable as input, and functions arrived to list, retrieve, extend and analyze palettes rather than only generate them. The C++ backend was rewritten as part of the same release.
impIndicator computes indicators of alien-species impact from GBIF-style occurrence cubes, producing species-level, site-level and regional measures with visualisation. The latest release renames the three headline functions to compute_species_indicator(), compute_site_indicator() and compute_regional_indicator(), drops the division by total occupied sites, and fixes the exponential transformation of impact categories into scores. It is part of the b-cubed-eu family and leans on sibling tooling rather than reimplementing it.
Two threads run through the recent releases. One is uncertainty: 0.6.0 wires in dubicube for cross-validation and uncertainty estimation on the indicators, moving output from point estimates toward quantified confidence. The other is scoping and naming — user-supplied sf regions in 0.4.0, occurrence-cube construction in 0.5.0, then the 0.6.1 rename — the pattern of a package tightening its public vocabulary as it approaches a stable release.
With the naming settled and uncertainty estimation in place, the next step is most likely consolidation toward a 1.0 — documentation and vignettes against the renamed functions rather than further indicator types.
qualpalr generates maximally distinct categorical color palettes by optimizing perceptual distance, with adaptation for color vision deficiency built in from early on. Version 1.0.0 in August 2025 ended an eight-year stretch of small maintenance releases: the color-difference metric became selectable, existing palettes from ColorBrewer and Tableau became usable as input, and functions arrived to list, retrieve, extend and analyze palettes rather than only generate them. The C++ backend was rewritten as part of the same release.
The package is moving from a generator to a toolkit that also works on palettes it did not create. Accepting a named palette as input, extending an existing one, and analyzing an arbitrary categorical palette all point the optimization machinery outward at the palettes people already use. The color-vision-deficiency handling followed the same path, consolidating from a single cvd_severity scalar to a named vector giving protan, deuter and tritan their own severities.
Two deprecations are explicitly staged for the next major release — autopal(), with no replacement offered, and cvd_severity — so removal is the most likely next structural step. The 1.0.1 release already tracks the underlying qualpal C++ library separately, suggesting future changes may arrive from there.
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 impIndicator or qualpalr.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all impIndicator alternatives → · See all qualpalr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. impIndicator and qualpalr 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. impIndicator and qualpalr 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 impIndicator alternatives in Analytics are ranked by recent ship velocity. Browse the "impIndicator alternatives" section above for the current picks, or visit /alternatives/impindicator for the full list with editorial commentary on each.
Top qualpalr alternatives in Analytics are ranked by recent ship velocity. Browse the "qualpalr alternatives" section above for the current picks, or visit /alternatives/qualpalr for the full list with editorial commentary on each.