poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of flextreat.hydrus1d and flightsbr — release velocity, themes, recent moves, and the top alternatives to consider.
A project-bound modelling package that shipped its final scenario workflow and stopped.
flextreat.hydrus1d is the R workflow KWB used to build, run and analyse HYDRUS-1D soil water balance and solute transport scenarios for the FlexTreat project. Its three releases track the project's own milestones rather than a product roadmap: a snapshot for a project meeting, a correction before a knowledge exchange with a partner project, and v0.2.0 carrying the scenario set used in the FlexTreat final report.
Brazil's flight-data package keeps working around what ANAC publishes and when.
flightsbr downloads Brazilian civil aviation data — flights, airport movements, aircraft registrations, air fares — straight from ANAC into R. Its read_ functions now default to the latest available date rather than requiring one, and read_aircrafts() has been renamed to read_aircraft(). The published feed jumps from 0.1.2 to 0.3.0 to 1.1.0, so intermediate releases are not visible here.
flextreat.hydrus1d is the R workflow KWB used to build, run and analyse HYDRUS-1D soil water balance and solute transport scenarios for the FlexTreat project. Its three releases track the project's own milestones rather than a product roadmap: a snapshot for a project meeting, a correction before a knowledge exchange with a partner project, and v0.2.0 carrying the scenario set used in the FlexTreat final report.
This is research code with a defined end, and v0.2.0 reads as that end — the workflow is documented in a scenario-analysis article and the scenarios match the published report. The most consequential change in its history was not a feature but a fix: the irrigation area was overestimated in the first snapshot, which made the status quo scenario wrong until v0.1.0 corrected it.
With the final report delivered, further releases are unlikely unless a follow-on project reuses the workflow; nothing in the entries points to continued development.
flightsbr downloads Brazilian civil aviation data — flights, airport movements, aircraft registrations, air fares — straight from ANAC into R. Its read_ functions now default to the latest available date rather than requiring one, and read_aircrafts() has been renamed to read_aircraft(). The published feed jumps from 0.1.2 to 0.3.0 to 1.1.0, so intermediate releases are not visible here.
This is a package defined by its upstream. Its releases are mostly reactions to how ANAC serves data: a download path that broke on 2022 data, URLs with inconsistent .CSV casing that hid available dates, a broken data dictionary link, and an air fares reader that had to be pulled entirely when the source became unworkable. The 2025 release is the first that reads like product design rather than repair — defaulting to the latest data and fixing a typo in a function name at the cost of a deprecation. Availability of the source, not developer intent, sets the release cadence.
The most likely next move is another adjustment to a changed ANAC endpoint or the return of the suspended air fares reader, since upstream availability has driven every release visible here.
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 flextreat.hydrus1d or flightsbr.
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
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 Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
See all flextreat.hydrus1d alternatives → · See all flightsbr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. flextreat.hydrus1d and flightsbr 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. flextreat.hydrus1d and flightsbr 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 flextreat.hydrus1d alternatives in Analytics are ranked by recent ship velocity. Browse the "flextreat.hydrus1d alternatives" section above for the current picks, or visit /alternatives/flextreat-hydrus1d for the full list with editorial commentary on each.
Top flightsbr alternatives in Analytics are ranked by recent ship velocity. Browse the "flightsbr alternatives" section above for the current picks, or visit /alternatives/flightsbr for the full list with editorial commentary on each.