simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of anyflights and invasimapr — release velocity, themes, recent moves, and the top alternatives to consider.
A nycflights13 generator whose recent work is all about the data being right.
anyflights builds nycflights13-style datasets for any US airport and year, downloading flight, weather, airline, airport, and plane tables and optionally packaging them. The four visible releases span 2022 to 2025 and are dominated by keeping those downloads working. The most recent fixes a timezone leak and gaps in hourly weather data.
invasimapr halved its install size and became citable; the science stayed put.
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
anyflights builds nycflights13-style datasets for any US airport and year, downloading flight, weather, airline, airport, and plane tables and optionally packaging them. The four visible releases span 2022 to 2025 and are dominated by keeping those downloads working. The most recent fixes a timezone leak and gaps in hourly weather data.
The function surface has been stable since 0.3; everything since concerns the fragility of the upstream sources. Broken URLs for airline data, download failures needing a session-timeout hint, planes data that stopped resolving, and weather values recorded only once an hour have each taken a release. Contributions come from teaching-adjacent users, which fits a package whose main use is generating course datasets.
Expect the next release to follow another upstream data-source change rather than to add a table or an argument.
invasimapr estimates species invasiveness and site invasibility from trait, environmental and resident-community data, exposing a traits → competition → invasion-fitness pipeline behind seven high-level wrappers. Its three releases are all packaging and standards work: a first citable archive in June 2026, then a maturity release bringing it in line with the B-Cubed software development guide. The one behavioral addition in that release is an opt-in standardise_inputs argument on compute_invasion_fitness(), off by default.
The pressure is toward being installable and auditable rather than more capable — install slimmed from roughly 100 MB to 56 MB, R CMD check warnings and notes resolved, sp moved to Suggests, a Darwin Core-aligned data dictionary added, and a Zenodo concept DOI with CITATION.cff, codemeta.json and .zenodo.json. The package moves in lockstep with its B-Cubed sibling dissmapr, tagged within minutes of each other at both 0.1.0 and 0.2.1, which points at project-level standards deadlines rather than independent release decisions. Trait dispersion metrics and scenario exploration remain on the roadmap.
Standards compliance is now complete and the roadmap names functional trait dispersion metrics and scenario exploration tools, so the next release is the first that can plausibly be about invasion ecology rather than packaging.
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 anyflights or invasimapr.
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 raster-to-terra migration is the only readable change in a feed of merge notes.
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 anyflights alternatives → · See all invasimapr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. anyflights and invasimapr 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. anyflights and invasimapr 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 anyflights alternatives in Analytics are ranked by recent ship velocity. Browse the "anyflights alternatives" section above for the current picks, or visit /alternatives/anyflights for the full list with editorial commentary on each.
Top invasimapr alternatives in Analytics are ranked by recent ship velocity. Browse the "invasimapr alternatives" section above for the current picks, or visit /alternatives/invasimapr for the full list with editorial commentary on each.