ANALYTICS
Adding chemical databases with one hand while public ones close programmatic access with the other.
Alternatives · analytics tools
sftime alternatives
The best sftime alternatives in analytics tools, ranked by Sparkpulse's velocity_score.
Updated Aug 14, 2026
Looking for the best alternatives to sftime? Sparkpulse tracks and ranks 12 alternatives in analytics tools by shipping velocity — how frequently each ships meaningful updates, verified from official changelogs. For reference, sftime shipped 0 meaningful updates in the last 30 days and carries a velocity score of 0.0 out of 10 in 2026. The alternatives below are ranked the same way, so you're comparing real release momentum, not marketing claims.
About 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.
Velocity 0.0 · Last update 38m ago
Top 12 alternatives to sftime
Ranked by recent ship velocity. Tap any card for the full editorial breakdown, or pivot to a head-to-head.
ANALYTICS
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
ANALYTICS
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
ANALYTICS
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
ANALYTICS
Went from estimating felling dates to doing the crossdating that produces them.
ANALYTICS
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
ANALYTICS
Added the HTTP client everyone moved to, then deleted a decade of its own public surface.
ANALYTICS
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
ANALYTICS
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
ANALYTICS
Reorganised its parsers by vendor, then opened the parser slot to users.
ANALYTICS
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
ANALYTICS
Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.
sftime vs alternatives — shipping velocity at a glance
Velocity score (0–10) and meaningful releases shipped in the last 30 days, from official changelogs. Higher = shipping faster.
| Product | Velocity | Sparks · 30d | Focus areas | Latest release |
|---|---|---|---|---|
| sftime (baseline) | 0.0 | 0 | spatiotemporalr-spatialinteroperability | — |
| webchem | 0.0 | 0 | cheminformaticsweb-apisdata-access | ChemIDplus and PAN queries removed as sources shut down |
| ReLTER | 0.0 | 0 | ecologyresearch-infrastructureropensci | ReLTER v1.0.0 |
| waywiser | 0.0 | 0 | spatial-statisticsmodel-assessmenttidymodels | — |
| taxizedb | 0.0 | 0 | taxonomybiodiversity-datasqlite | SQLite everywhere, three new sources, taxize verbs ported |
| fellingdater | 0.0 | 0 | dendrochronologycrossdatingarchaeology | Adds a full crossdating and tree-ring analysis toolkit |
| textshaping | 0.0 | 0 | typographytext-shapingbidi | Shaping engine rewritten to honour global text direction |
| vcr | 0.0 | 0 | testinghttp-mockingbreaking-change | 2.0 removes the logging API and the exported R6 classes |
| parzer | 0.0 | 0 | geospatialstring-parsingcoordinates | — |
| dfms | 0.0 | 0 | nowcastingstate-space-modelseconometrics | 1.0: rOpenSci review passed, news decomposition added |
| lightr | 0.0 | 0 | spectrometryfile-parsersbreaking-change | Parsers renamed by vendor; Avantes binary support restored |
| sass | 0.0 | 0 | csssassr-package | — |
| sdtm.oak | 0.0 | 0 | clinical-trialssdtmpharmaverse | sdtm.oak v0.2.0 CRAN release |
The 12 best sftime alternatives, in depth
1. webchem · velocity 0.0
Adding chemical databases with one hand while public ones close programmatic access with the other.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “ChemIDplus and PAN queries removed as sources shut down”.
Where sftime leans on spatiotemporal, r spatial and interoperability, webchem focuses on cheminformatics, web apis and data access.
webchem and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
2. ReLTER · velocity 0.0
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “ReLTER v1.0.0”.
Where sftime leans on spatiotemporal, r spatial and interoperability, ReLTER focuses on ecology, research infrastructure and ropensci.
ReLTER and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
3. waywiser · velocity 0.0
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sftime leans on spatiotemporal, r spatial and interoperability, waywiser focuses on spatial statistics, model assessment and tidymodels.
waywiser and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
4. taxizedb · velocity 0.0
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “SQLite everywhere, three new sources, taxize verbs ported”.
Where sftime leans on spatiotemporal, r spatial and interoperability, taxizedb focuses on taxonomy, biodiversity data and sqlite.
taxizedb and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
5. fellingdater · velocity 0.0
Went from estimating felling dates to doing the crossdating that produces them.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Adds a full crossdating and tree-ring analysis toolkit”.
Where sftime leans on spatiotemporal, r spatial and interoperability, fellingdater focuses on dendrochronology, crossdating and archaeology.
fellingdater and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full fellingdater trajectory → · Compare sftime vs fellingdater →
6. textshaping · velocity 0.0
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Shaping engine rewritten to honour global text direction”.
Where sftime leans on spatiotemporal, r spatial and interoperability, textshaping focuses on typography, text shaping and bidi.
textshaping and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Full textshaping trajectory → · Compare sftime vs textshaping →
7. vcr · velocity 0.0
Added the HTTP client everyone moved to, then deleted a decade of its own public surface.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “2.0 removes the logging API and the exported R6 classes”.
Where sftime leans on spatiotemporal, r spatial and interoperability, vcr focuses on testing, http mocking and breaking change.
vcr and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
8. parzer · velocity 0.0
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sftime leans on spatiotemporal, r spatial and interoperability, parzer focuses on geospatial, string parsing and coordinates.
parzer and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
9. dfms · velocity 0.0
Peer-reviewed, feature-complete, and now able to hand its models to other forecasting engines.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “1.0: rOpenSci review passed, news decomposition added”.
Where sftime leans on spatiotemporal, r spatial and interoperability, dfms focuses on nowcasting, state space models and econometrics.
dfms and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
10. lightr · velocity 0.0
Reorganised its parsers by vendor, then opened the parser slot to users.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “Parsers renamed by vendor; Avantes binary support restored”.
Where sftime leans on spatiotemporal, r spatial and interoperability, lightr focuses on spectrometry, file parsers and breaking change.
lightr and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
11. sass · velocity 0.0
Nine releases of compiler warnings and CRAN checks — the Sass binding is in pure upkeep.
Its velocity score of 0.0/10 reflects longer-term release cadence.
Where sftime leans on spatiotemporal, r spatial and interoperability, sass focuses on css, sass and r package.
sass and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
12. sdtm.oak · velocity 0.0
Two releases in, the open-source SDTM toolkit now covers the domains it originally excluded.
Its velocity score of 0.0/10 reflects longer-term release cadence; its most recent meaningful update was “sdtm.oak v0.2.0 CRAN release”.
Where sftime leans on spatiotemporal, r spatial and interoperability, sdtm.oak focuses on clinical trials, sdtm and pharmaverse.
sdtm.oak and sftime have shipped at a similar pace over the last 30 days, so the decision comes down to fit and feature depth.
Frequently asked questions
What are the best alternatives to sftime?
The top sftime alternatives we currently track in analytics tools are webchem, ReLTER, waywiser, taxizedb, fellingdater, ranked by recent ship velocity.
How is this list of sftime alternatives ranked?
Alternatives are ranked by Sparkpulse's velocity_score — release cadence + 30-day spark count + sector-relative ship rate.
Can I compare sftime directly with one of these alternatives?
Yes — every card has a "Compare with sftime" link to a side-by-side /compare page.