poppr
A population-genetics workhorse in long-term maintenance, shipping only what CRAN demands.
A side-by-side editorial comparison of flightsbr and jmastats — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A Japan Meteorological Agency client whose real product is keeping its bundled datasets current.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
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.
jmastats pulls weather and climate data from the Japan Meteorological Agency into R, and most of its releases exist to refresh the station and reference datasets it ships. Three of the four versions on record are dataset updates, dated by the month they were cut. The exception is 0.3.0, which taught jma_collect() to retrieve climatological normals derived from past observations.
The package treats bundled data as the thing that must not go stale, and the retrieval API as broadly finished. Where code does change, it is about being a well-behaved client — request intervals to reduce server load, messages when returned data contains missing values, corrected station coordinates. Capability growth happens in single steps, roughly once a year.
The next release is most likely another dated dataset refresh; a further extension of jma_collect() to a new observation type is plausible but the entries show no specific one being prepared.
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 flightsbr or jmastats.
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 project-bound modelling package that shipped its final scenario workflow and stopped.
A Facebook Marketing API client for R whose release schedule belongs to Meta, not its author.
See all flightsbr alternatives → · See all jmastats alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. flightsbr and jmastats 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. flightsbr and jmastats 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 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.
Top jmastats alternatives in Analytics are ranked by recent ship velocity. Browse the "jmastats alternatives" section above for the current picks, or visit /alternatives/jmastats for the full list with editorial commentary on each.