WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
openair vs traits.build
A side-by-side editorial comparison of openair and traits.build — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
openair vs traits.build: at a glance
What is openair?
Air quality analysis rebuilt on ggplot2, twenty years of lattice plotting dropped in one release.
openair is the reference toolkit for UK and European air quality data analysis, covering import from national monitoring networks, time averaging, polar and trajectory plots, and trend estimation. Version 3.0.0 rewrote every plotting function in ggplot2 and removed lattice, latticeExtra, hexbin, and mapproj from the dependency tree; 3.1.0 followed six weeks later to settle how parameters reach those functions, remapping base and lattice graphics arguments to ggplot2 equivalents with a warning rather than failing outright.
What is traits.build?
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
traits.build is the harmonisation workflow extracted from AusTraits and generalised so other groups can assemble trait databases from heterogeneous sources. Its schema and ontology reached 1.0.0 in late 2024, and the package now leans on austraits itself for the functions that belong to database consumption rather than construction. The 2025 release extends the data model with identifiers and methods tables.
openair vs traits.build: editorial side-by-side
openair
0.0INFRA · APIS
Air quality analysis rebuilt on ggplot2, twenty years of lattice plotting dropped in one release.
◆ Current state
openair is the reference toolkit for UK and European air quality data analysis, covering import from national monitoring networks, time averaging, polar and trajectory plots, and trend estimation. Version 3.0.0 rewrote every plotting function in ggplot2 and removed lattice, latticeExtra, hexbin, and mapproj from the dependency tree; 3.1.0 followed six weeks later to settle how parameters reach those functions, remapping base and lattice graphics arguments to ggplot2 equivalents with a warning rather than failing outright.
◆ Where it's heading
Two threads run through these releases. The first is the rendering migration and its long tail — deprecated arguments rehomed into breakOpts(), graphical parameters standardized on ggplot2 conventions, trajectory projections collapsed from three arguments into a single crs. The second is data access decaying underneath the package: importEurope() now errors for recent years because the database behind it was retired, while importUKAQ() gained automatic source detection and steadily more careful ratification handling. Correctness fixes keep landing in the analytical core too, including a corrected TheilSen intercept and more consistent bin boundaries in multi-period time averaging.
◆ Prediction
The migration is not finished — 3.1.0 is still remapping legacy graphics arguments with warnings — so expect a release that turns those deprecations into removals, and continued churn around European data import while the replacement service settles.
traits.build
0.0INFRA · APIS
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
◆ Current state
traits.build is the harmonisation workflow extracted from AusTraits and generalised so other groups can assemble trait databases from heterogeneous sources. Its schema and ontology reached 1.0.0 in late 2024, and the package now leans on austraits itself for the functions that belong to database consumption rather than construction. The 2025 release extends the data model with identifiers and methods tables.
◆ Where it's heading
The project's direction is toward provenance and interoperability rather than throughput. Value types grew to carry standard error and standard deviation, the methods table now records what kind of source each dataset came from, and the identifiers table lets a trait value point at a herbarium sheet, a museum accession or a GenBank record. Alongside that, responsibilities have been split with the sibling austraits package, with shared functions moved out under deprecation shims. A published paper and a versioned ontology mark it as infrastructure meant for outside adoption, not just for AusTraits.
◆ Prediction
Expect further schema extensions in the same provenance direction, since the last two releases both added structure for describing where a measurement came from rather than new processing capability.
Alternatives to openair and traits.build
Other Infra & APIs 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 openair or traits.build.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all openair alternatives → · See all traits.build alternatives →
Recent activity from openair and traits.build
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agoopenairggplot2 parameter conventions settled; timeAverage bins fixed
- 4mo agoopenairAll plotting rewritten in ggplot2; lattice dropped ⚡
- 11mo agoopenairEuropean import deprecated; UK network source auto-detection
- 1y agotraits.buildTrait values gain specimen and GenBank identifiers ⚡
- 1y agotraits.buildFunctions move to austraits as the ontology reaches 1.0.0
- 2y agotraits.buildFixes to dataset testing, reports and name standardisation
- 2y agotraits.buildAusTraits workflow generalised into a reusable package
Frequently asked questions
What is the difference between openair and traits.build?
Both compete on the same themes — r-package — within Infra & APIs. openair and traits.build 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.
Is openair better than traits.build?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. openair and traits.build 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to openair?
Top openair alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "openair alternatives" section above for the current picks, or visit /alternatives/openair for the full list with editorial commentary on each.
What are the best alternatives to traits.build?
Top traits.build alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "traits.build alternatives" section above for the current picks, or visit /alternatives/traits-build for the full list with editorial commentary on each.