accessibility
An urban accessibility toolkit that grew into a distributional-equity toolkit.
A side-by-side editorial comparison of jmastats and poppr — release velocity, themes, recent moves, and the top alternatives to consider.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
poppr analyses populations with mixed clonal and sexual reproduction, and its recent history is almost entirely upkeep. Four of the last six releases state outright that they contain no user-visible changes — CRAN nit-picks, URL formatting, a clang13 build failure. The last release with real content was 2.9.0, which added bruvo.between() for comparing a query dataset against a reference database and began deprecating the blacklist argument in favour of exclude.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
The package treats bundled data as the thing that must not go stale, and the retrieval API as broadly finished. Where code does change, it is about being a well-behaved client — request intervals to reduce server load, messages when returned data contains missing values, corrected station coordinates. Capability growth happens in single steps, roughly once a year.
The next release is most likely another dated dataset refresh; a further extension of jma_collect() to a new observation type is plausible but the entries show no specific one being prepared.
poppr analyses populations with mixed clonal and sexual reproduction, and its recent history is almost entirely upkeep. Four of the last six releases state outright that they contain no user-visible changes — CRAN nit-picks, URL formatting, a clang13 build failure. The last release with real content was 2.9.0, which added bruvo.between() for comparing a query dataset against a reference database and began deprecating the blacklist argument in favour of exclude.
This is a mature package being kept installable rather than developed. The deprecation promised in 2.9.0 — removing blacklist in 2.10 — has not arrived across three years and four releases, which is the clearest sign that no feature line is currently active. What movement exists comes from outside contributors and from the toolchain moving underneath the package.
The next release is most likely another CRAN or compiler-compatibility fix; the promised 2.10 removal of blacklist would be the first sign of active development resuming, but nothing in these entries indicates it is being prepared.
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 jmastats or poppr.
An urban accessibility toolkit that grew into a distributional-equity toolkit.
A Google Ads API client for R that exists to stay one step ahead of deprecation.
The Carpentries' lesson skin, rebuilt on Bootstrap 5 with dark mode and a wider reach.
A project-bound modelling package that shipped its final scenario workflow and stopped.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
The utility layer under KWB's R packages, growing by accretion one helper at a time.
See all jmastats alternatives → · See all poppr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. jmastats and poppr 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. jmastats and poppr 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 jmastats alternatives in Analytics are ranked by recent ship velocity. Browse the "jmastats alternatives" section above for the current picks, or visit /alternatives/jmastats for the full list with editorial commentary on each.
Top poppr alternatives in Analytics are ranked by recent ship velocity. Browse the "poppr alternatives" section above for the current picks, or visit /alternatives/poppr for the full list with editorial commentary on each.