simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of ibis.iSDM and rATTAINS — release velocity, themes, recent moves, and the top alternatives to consider.
A raster-to-terra migration is the only readable change in a feed of merge notes.
ibis.iSDM fits integrated species distribution models in R. Its release notes are GitHub's auto-generated pull-request lists, so most tags say only which branch was merged and by whom. The one release with a written note, 0.0.5, records the migration from raster to terra across the whole package, with an explicit warning that established code may break.
The R client for EPA water quality data spent two releases undoing its own promises about data shape.
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
ibis.iSDM fits integrated species distribution models in R. Its release notes are GitHub's auto-generated pull-request lists, so most tags say only which branch was merged and by whom. The one release with a written note, 0.0.5, records the migration from raster to terra across the whole package, with an explicit warning that established code may break.
Direction cannot be read from this feed with any confidence - three of the four visible tags carry nothing beyond merge titles and a full-changelog link. What is visible is a 2023 spent on dependency modernisation and dev-branch merges, ending with a 0.1.1 tag that December and nothing since.
These entries do not support a prediction; the notes would have to carry written content before a direction could be read from them.
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
The direction is toward a thinner, lower-maintenance wrapper. Caching went in 0.1.4 when hoardr was archived, tidyjson and janitor went earlier, tibblify went in 1.1.0, and each removal handed a little more data-shaping responsibility back to the user — the current advice is to pass .unnest = FALSE and rectangle the results with whatever tidying package you prefer. Release cadence is slow and mostly reactive: upstream API terms, archived dependencies, and compatibility with test tooling account for most of the log. The package's centre of gravity is staying installable and honest about what ATTAINS returns rather than smoothing it over.
Given the pattern, the next release is likelier to be a compatibility or upstream-driven fix than new endpoint coverage; how the API key requirement affects users in scripted and CI contexts is the obvious open question the entries do not yet answer.
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 ibis.iSDM or rATTAINS.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all ibis.iSDM alternatives → · See all rATTAINS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. ibis.iSDM and rATTAINS 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. ibis.iSDM and rATTAINS 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 ibis.iSDM alternatives in Analytics are ranked by recent ship velocity. Browse the "ibis.iSDM alternatives" section above for the current picks, or visit /alternatives/ibis-isdm for the full list with editorial commentary on each.
Top rATTAINS alternatives in Analytics are ranked by recent ship velocity. Browse the "rATTAINS alternatives" section above for the current picks, or visit /alternatives/rattains for the full list with editorial commentary on each.