datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
fellingdater vs taxizedb
A side-by-side editorial comparison of fellingdater and taxizedb — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropensci
fellingdater vs taxizedb: at a glance
What is fellingdater?
Went from estimating felling dates to doing the crossdating that produces them.
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
What is taxizedb?
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.
fellingdater vs taxizedb: editorial side-by-side
fellingdater
0.0ANALYTICS
Went from estimating felling dates to doing the crossdating that produces them.
◆ Current state
fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.
◆ Where it's heading
The package has expanded backwards along the workflow. It began at the last step — given dated series, estimate the felling date — and 1.2.0 added the step before it, establishing those dates by crossdating in the first place. Version 1.2.1 is early polish on that new surface: axis control, non-syntactic column names, encoding safety in read_fh(). The direction is a single package covering the chain from raw ring widths to a felling-date estimate.
◆ Prediction
Expect the trs_* family to keep accumulating polish and additional crossdating statistics, since it is barely a year old and 1.2.1 was already fixing its plotting and top_n behaviour. Whether the two halves of the package get unified into one workflow interface is the open question the entries do not answer.
taxizedb
0.0ANALYTICS
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
◆ Current state
taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.
◆ Where it's heading
The package is trading convenience for independence. Each release removes another thing that has to be working elsewhere for the package to function: hosted database preparation is gone, and where a provider disappears the package documents it rather than pretending otherwise — db_download_tpl() is now defunct because The Plant List no longer exists, though previously downloaded copies still query fine. Release cadence is slow, with multi-year gaps and a maintainer handover in 2023.
◆ Prediction
Expect further releases to track data sources appearing and disappearing rather than adding features, since that has driven every recent change. Local conversion also shifts cost onto users, so build time and memory for the larger sources are the plausible next thing to need attention.
Alternatives to fellingdater and taxizedb
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 fellingdater or taxizedb.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all fellingdater alternatives → · See all taxizedb alternatives →
Recent activity from fellingdater and taxizedb
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agofellingdaterPolish for the crossdating plots and file reader
- 9mo agotaxizedbDatabases now built locally from raw data, not the cloud
- 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit ⚡
- 1y agofellingdaterUser-supplied sapwood data works across all functions
- 1y agofellingdaterFixes fd_report() with user-defined sapwood files
- 2y agofellingdaterJOSS paper accepted; citation updated
- 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
- 3y agotaxizedbPatch release for a maintainer change
- 5y agotaxizedbtaxa_at() retrieves ancestors at a named rank
- 5y agotaxizedbFixes failing tests
- 6y agotaxizedbSQLite everywhere, three new sources, taxize verbs ported ⚡
- 9y agotaxizedbTracks the dplyr split that introduced dbplyr
Frequently asked questions
What is the difference between fellingdater and taxizedb?
Both compete on the same themes — ropensci — within Analytics. fellingdater and taxizedb 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 fellingdater better than taxizedb?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fellingdater and taxizedb 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 fellingdater?
Top fellingdater alternatives in Analytics are ranked by recent ship velocity. Browse the "fellingdater alternatives" section above for the current picks, or visit /alternatives/fellingdater for the full list with editorial commentary on each.
What are the best alternatives to taxizedb?
Top taxizedb alternatives in Analytics are ranked by recent ship velocity. Browse the "taxizedb alternatives" section above for the current picks, or visit /alternatives/taxizedb for the full list with editorial commentary on each.