edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of flightsbr and hubVis — 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.
The hubverse plotting layer spends its releases absorbing upstream churn, not adding charts.
hubVis is the visualization component of the hubverse stack, centred on plot_step_ahead_model_output() for static and interactive forecast plots. Since the stable 0.1.0 in late 2024 it has shipped three patch releases, every one of them a single referenced issue fix. The plotting surface itself has not grown.
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.
hubVis is the visualization component of the hubverse stack, centred on plot_step_ahead_model_output() for static and interactive forecast plots. Since the stable 0.1.0 in late 2024 it has shipped three patch releases, every one of them a single referenced issue fix. The plotting surface itself has not grown.
The pattern across all four releases is narrow and reactive: a legend construction fix, a palette assignment fix, and most recently a compatibility change for ggplot2 4.0.0 written to keep working with earlier versions too. Two of the three fixes concern colour and legend handling, which suggests palette assignment is the fragile part of the codebase. As a thin layer over ggplot2 inside a larger stack, the package's release triggers come from below it rather than from its own roadmap.
Expect continued single-issue patches driven by upstream ggplot2 changes and by whatever the sibling hubverse packages emit, rather than new plot types.
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 hubVis.
A grammar for experimental design that learned to compose designs and track its own provenance.
A Swiss clinical-trial data reader that surfaces once every couple of years to clear check notes.
A star-schema modelling package grew a query language, a deployment path, and then a map layer.
A water-research lab's ODBC helper, still fighting Windows database drivers a decade in.
PACTA's loan-book matcher opened up to sector taxonomies other than its own.
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
See all flightsbr alternatives → · See all hubVis alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. flightsbr and hubVis 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 hubVis 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 hubVis alternatives in Analytics are ranked by recent ship velocity. Browse the "hubVis alternatives" section above for the current picks, or visit /alternatives/hubvis for the full list with editorial commentary on each.