datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
sftime vs taxizedb
A side-by-side editorial comparison of sftime and taxizedb — release velocity, themes, recent moves, and the top alternatives to consider.
sftime vs taxizedb: at a glance
What is sftime?
The spatiotemporal companion to sf, moving at the pace of the packages around it.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
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.
sftime vs taxizedb: editorial side-by-side
sftime
0.0ANALYTICS
The spatiotemporal companion to sf, moving at the pace of the packages around it.
◆ Current state
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
◆ Where it's heading
The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.
◆ Prediction
Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.
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 sftime 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 sftime 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 sftime alternatives → · See all taxizedb alternatives →
Recent activity from sftime and taxizedb
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agosftimeExamples switched to the native R pipe
- 9mo agotaxizedbDatabases now built locally from raw data, not the cloud
- 11mo agosftimeFixes the cubble namespace version check
- 1y agosftimeConverts from spatstat, sftrack and cubble objects
- 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 sftime and taxizedb?
They serve adjacent needs but don't currently overlap on shipped themes. sftime 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 sftime better than taxizedb?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sftime 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 sftime?
Top sftime alternatives in Analytics are ranked by recent ship velocity. Browse the "sftime alternatives" section above for the current picks, or visit /alternatives/sftime 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.