← Back to home
Comparison · Analytics

fillpattern vs soilDBdata

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

fillpattern vs soilDBdata: at a glance

FeaturefillpatternsoilDBdata
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesggplot2, data-visualization, accessibility, graphicssoil data, test fixtures, nasis, data package
Last editorial update1h ago5h ago
WebsiteVisit →Visit →

What is fillpattern?

Pattern fills for ggplot2, hardened against the ways users write sizes

fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.

Read the full fillpattern 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 →

fillpattern vs soilDBdata: editorial side-by-side

F
fillpattern
ANALYTICS
0.0

Pattern fills for ggplot2, hardened against the ways users write sizes

◆ Current state

fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.

◆ Where it's heading

Development is slow and entirely reactive to how the string-based size interface fails. The pattern across releases is the same: a user hits an edge — very small fill areas in 1.0.2, malformed unit strings in 1.0.3 — and the fix is either a graceful fallback or a clearer error. Leaning on R's newer graphics engine rather than reimplementing pattern rendering keeps the package small at the cost of raising its version floor.

◆ Prediction

Expect further releases to stay in the same register: parsing and validation fixes for the size and unit interface, with the pattern set itself unlikely to change.

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

See all fillpattern alternatives → · See all soilDBdata alternatives →

Recent activity from fillpattern and soilDBdata

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

  1. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  2. 6mo agofillpatternSize string parsing fixed; invalid units now report instead of crash
  3. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  4. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  5. 2y agofillpatternSmall fill areas no longer crash; min_size falls back to solid
  6. 2y agofillpatternfillpattern 1.0.1
  7. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  8. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between fillpattern and soilDBdata?

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

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

Top fillpattern alternatives in Analytics are ranked by recent ship velocity. Browse the "fillpattern alternatives" section above for the current picks, or visit /alternatives/fillpattern 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.