rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of CatastRo and epiflows — release velocity, themes, recent moves, and the top alternatives to consider.
Spain's cadastre client spent 1.0.0 breaking its own cache to become a tidy, httr2-native package.
CatastRo pulls parcels, buildings, addresses and WMS map layers from the Spanish Cadastre into R. The 1.0.0 line rebuilt the codebase on httr2, reorganized the cache into topic-based subfolders and moved persistent storage from rappdirs to tools::R_user_dir(), a change that invalidates every pre-1.0.0 cache. The two releases since are documentation and an AI-assisted internal refactor.
epiflows has shipped four releases in eight years, none of which changed the code.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
CatastRo pulls parcels, buildings, addresses and WMS map layers from the Spanish Cadastre into R. The 1.0.0 line rebuilt the codebase on httr2, reorganized the cache into topic-based subfolders and moved persistent storage from rappdirs to tools::R_user_dir(), a change that invalidates every pre-1.0.0 cache. The two releases since are documentation and an AI-assisted internal refactor.
The arc is consolidation, not expansion: the retrieval surface has been stable since 0.3.0 added street names to addresses, while the maintainer has spent the releases since standardizing transport, output types and messaging. All functions now return tibbles or sf objects with tibble data, and cli handles user-facing output. The same modernization is being applied across the maintainer's other Spanish-data packages.
Expect the next releases to stay in the 1.0.x patch range — documentation, cli wording and CRAN upkeep — unless the Cadastre publishes a new service worth wrapping.
epiflows predicts the spread of infectious disease along population flows between locations, and it is effectively dormant. The whole visible history spans 2018 to 2026 in four entries: the first CRAN release, a Zenodo archival tag, a Roxygen patch whose notes state the functionality is unchanged, and a 2026 release replacing deprecated ggplot2 and tibble calls. No entry describes new epidemiological capability.
The package is being kept installable rather than developed. The one recent release is dependency maintenance contributed from outside, which is the pattern for RECON-era epidemiology packages that have outlived their original project funding. Two separate entries are both labelled version 0.2.1, so even the version history is not a reliable guide to what changed.
Any further releases will most likely be more deprecation cleanup to keep the package on CRAN; there is nothing in the record suggesting active development has resumed.
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 CatastRo or epiflows.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
See all CatastRo alternatives → · See all epiflows alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CatastRo and epiflows 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. CatastRo and epiflows 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 CatastRo alternatives in Analytics are ranked by recent ship velocity. Browse the "CatastRo alternatives" section above for the current picks, or visit /alternatives/catastro for the full list with editorial commentary on each.
Top epiflows alternatives in Analytics are ranked by recent ship velocity. Browse the "epiflows alternatives" section above for the current picks, or visit /alternatives/epiflows-r for the full list with editorial commentary on each.