← Back to home
Comparison · Analytics

riem vs sftime

A side-by-side editorial comparison of riem and sftime — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

riem vs sftime: at a glance

Featureriemsftime
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesweather-data, api-client, r-package, ropenscispatiotemporal, r-spatial, interoperability, tidyverse-integration
Last editorial update56m ago4h ago
WebsiteVisit →Visit →

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.

Read the full riem trajectory →

What is 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.

Read the full sftime trajectory →

riem vs sftime: editorial side-by-side

R
riem
ANALYTICS
0.0

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.

S
sftime
ANALYTICS
0.0

The spatiotemporal companion to sf, moving at the pace of the packages around it.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to riem and sftime

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 riem or sftime.

See all riem alternatives → · See all sftime alternatives →

Recent activity from riem and sftime

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agosftimeExamples switched to the native R pipe
  2. 11mo agosftimeFixes the cubble namespace version check
  3. 1y agoriem1.0.0 removes defaults and adds query arguments
  4. 1y agoriemDrops the last vcr usage in favour of httptest2
  5. 1y agosftimeConverts from spatstat, sftrack and cubble objects
  6. 2y agoriemTimezone and timestamp-parsing fixes
  7. 4y agoriemMoves to httr2 and httptest2
  8. 4y agoriemSwitches to newer IEM metadata web services
  9. 9y agoriemReduces dependencies to tibble alone

Frequently asked questions

What is the difference between riem and sftime?

Both compete on the same themes — r-package — within Analytics. riem and sftime 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 riem better than sftime?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. riem and sftime 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 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.

What are the best alternatives to sftime?

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.