← Back to home
Comparison · Analytics

qualpalr vs soilDBdata

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

qualpalr vs soilDBdata: at a glance

FeaturequalpalrsoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themescolor-palettes, accessibility, color-vision-deficiency, optimizationsoil data, test fixtures, nasis, data package
Last editorial update45m ago6h ago
WebsiteVisit →Visit →

What is qualpalr?

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.

Read the full qualpalr trajectory →

What is soilDBdata?

soilDBdata exists so soilDB's tests can run without a NASIS connection.

soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.

Read the full soilDBdata trajectory →

qualpalr vs soilDBdata: editorial side-by-side

Q
qualpalr
ANALYTICS
0.0

A palette generator became a palette platform — and changed the metric behind every color it picks.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

S
soilDBdata
ANALYTICS
0.0

soilDBdata exists so soilDB's tests can run without a NASIS connection.

◆ Current state

soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.

◆ Where it's heading

Development follows soilDB rather than leading it: assets get bumped when a soilDB version changes, and purpose lists are updated when soilDB adds a table. The one release that changed what testing is possible was v0.1.1, which added selected-set _View_1 tables alongside whole tables so both SS=TRUE and SS=FALSE code paths could be exercised. Four-year gaps between releases are normal here and do not indicate abandonment — a fixture package only needs to move when the fixtures go stale.

◆ Prediction

The recent addition is a new geography rather than a new table structure, so further releases most likely continue broadening dataset coverage as soilDB gains regions to test against.

Alternatives to qualpalr and soilDBdata

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 qualpalr or soilDBdata.

See all qualpalr alternatives → · See all soilDBdata alternatives →

Recent activity from qualpalr and soilDBdata

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

  1. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  2. 10mo agoqualpalrJOSS citation added and C++ library bumped to 3.3.0
  3. 0y agoqualpalrSelectable difference metric, palette input, and a rewritten backend
  4. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  5. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  6. 2y agoqualpalrRcppParallel dropped and n_threads deprecated
  7. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  8. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures
  9. 7y agoqualpalrThreaded distance-matrix computation via a new n_threads argument
  10. 8y agoqualpalrPalette generation becomes deterministic
  11. 9y agoqualpalrautopal() fixed after a zero-difference bug

Frequently asked questions

What is the difference between qualpalr and soilDBdata?

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

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

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.

What are the best alternatives to soilDBdata?

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