tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
forcis vs riem
A side-by-side editorial comparison of forcis and riem — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packageropensci
forcis vs riem: at a glance
What is forcis?
A foraminifera data-access package whose entire release history is the rOpenSci review process.
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
What is riem?
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
forcis vs riem: editorial side-by-side
forcis
0.0ANALYTICS
A foraminifera data-access package whose entire release history is the rOpenSci review process.
◆ Current state
forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.
◆ Where it's heading
The package is moving from research artifact to reviewed, distributable infrastructure — submitted to rOpenSci at 0.1.0, integrated review feedback at 1.0.0, cleared CRAN at 1.0.1. That arc is complete, so the next phase should be the first release driven by users rather than reviewers.
◆ Prediction
With review and CRAN acceptance both behind it, the next release is most likely to track upstream FORCIS database changes or add query conveniences; the entries themselves say nothing about planned features.
riem
0.0ANALYTICS
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
◆ Current state
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
◆ Where it's heading
The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.
◆ Prediction
With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing again.
Alternatives to forcis and riem
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 forcis or riem.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
Recent activity from forcis and riem
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agoforcisPost-CRAN-review example and practice cleanup
- 1y agoforcis1.0.0 incorporates rOpenSci review feedback
- 1y agoriem1.0.0 removes defaults and adds query arguments
- 1y agoriemDrops the last vcr usage in favour of httptest2
- 1y agoforcisFirst stable release, submitted to rOpenSci
- 2y agoriemTimezone and timestamp-parsing fixes
- 4y agoriemMoves to httr2 and httptest2
- 4y agoriemSwitches to newer IEM metadata web services
- 9y agoriemReduces dependencies to tibble alone
Frequently asked questions
What is the difference between forcis and riem?
Both compete on the same themes — r-package, ropensci — within Analytics. forcis and riem 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 forcis better than riem?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forcis and riem 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 forcis?
Top forcis alternatives in Analytics are ranked by recent ship velocity. Browse the "forcis alternatives" section above for the current picks, or visit /alternatives/forcis for the full list with editorial commentary on each.
What are the best alternatives to riem?
Top riem alternatives in Analytics are ranked by recent ship velocity. Browse the "riem alternatives" section above for the current picks, or visit /alternatives/riem for the full list with editorial commentary on each.