rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
A side-by-side editorial comparison of dbparser and timetk — release velocity, themes, recent moves, and the top alternatives to consider.
dbparser shed its database and CSV writers to become just a DrugBank parser.
dbparser reads DrugBank's XML release into R tibbles. Its 2.0 line removed the persistence features that defined 1.x, writing to a database or to CSV, in favour of returning a dvobject the caller handles. Releases since have been column-naming normalization and test updates against newer DrugBank versions.
timetk swallowed anomalize whole, then went quiet for two years
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
dbparser reads DrugBank's XML release into R tibbles. Its 2.0 line removed the persistence features that defined 1.x, writing to a database or to CSV, in favour of returning a dvobject the caller handles. Releases since have been column-naming normalization and test updates against newer DrugBank versions.
The arc is scope reduction. Version 1.2.0 was the high-water mark of ambition, adding collective parsers, an R6 redesign and progress bars; 2.0.1 then deprecated the database and CSV writers and the old public methods outright. What remains is a narrower package whose ongoing work is keeping column names consistent and tests current with DrugBank's schema.
The last two releases track DrugBank data versions rather than adding features, so the next is most likely another compatibility pass against a newer DrugBank release.
timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.
The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.
The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.
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 dbparser or timetk.
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all dbparser alternatives → · See all timetk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dbparser and timetk 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. dbparser and timetk 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 dbparser alternatives in Analytics are ranked by recent ship velocity. Browse the "dbparser alternatives" section above for the current picks, or visit /alternatives/dbparser for the full list with editorial commentary on each.
Top timetk alternatives in Analytics are ranked by recent ship velocity. Browse the "timetk alternatives" section above for the current picks, or visit /alternatives/timetk for the full list with editorial commentary on each.