datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of sftime and simulist — release velocity, themes, recent moves, and the top alternatives to consider.
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.
simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.
simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.
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.
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.
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.
simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.
The scope moved outward in two steps. 0.5.0 added truncate_linelist() and messy_linelist() to produce right-truncated snapshots and data with missingness and inconsistencies; 0.6.0 added censor_linelist() for grouping dates into intervals with a weekend-reporting effect. The simulation core has meanwhile settled — 0.7.0's changes are interface polish: weighted sex sampling and <epiparameter> objects accepted for reporting_delay.
Post-processing is where the recent work is, so further realism controls — additional reporting artefacts or interval schemes — are a likelier next step than new epidemic model structures.
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 simulist.
The messy-date parser rewrote its core in Rust and came out 300x faster.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
R help pages translated on demand by whichever LLM you point it at.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all sftime alternatives → · See all simulist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. sftime and simulist 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. sftime and simulist 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 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.
Top simulist alternatives in Analytics are ranked by recent ship velocity. Browse the "simulist alternatives" section above for the current picks, or visit /alternatives/simulist for the full list with editorial commentary on each.