← Back to home
Comparison · Infra & APIs

ggInterval vs phyloatlas

A side-by-side editorial comparison of ggInterval and phyloatlas — release velocity, themes, recent moves, and the top alternatives to consider.

ggInterval vs phyloatlas: at a glance

FeatureggIntervalphyloatlas
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessymbolic-data-analysis, interval-data, ggplot2, data-visualizationphylogenetics, research-data, data-provenance, open-science
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is ggInterval?

Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.

ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.

Read the full ggInterval trajectory →

What is phyloatlas?

An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.

This is a curated deposit of species-level phylogenies — 264 trees across 62 partitions, 247 of them time-calibrated — paired with a species-name dictionary of roughly 638,000 standardized labels and per-tree provenance. It is moving through peer review at Methods in Ecology and Evolution, and the release stream is essentially a public erratum log: eight releases in five weeks, each reconciling the deposit against source papers, the manuscript, and its own metadata. The most recent replaced the turtle canonical with a 274-tip ultrametric chronogram after the previous tree failed time-calibration integrity checks.

Read the full phyloatlas trajectory →

ggInterval vs phyloatlas: editorial side-by-side

G
ggInterval
INFRA · APIS
0.0

Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.

◆ Current state

ggInterval visualizes symbolic interval-valued data — observations recorded as ranges rather than points — with a family of plot functions in the ggplot2 idiom. The plot catalogue grew most recently with interval correlation heatmaps and interval line plots compatible with time-series input. The three releases before that were corrections: seven plot functions renamed for consistency, examples switched from dontrun to donttest at CRAN's request, and a vignette rewritten to demonstrate every function in one place.

◆ Where it's heading

The package is consolidating an interface that had drifted. Renaming seven functions in a single release is the clearest signal — the naming was inconsistent enough to be worth breaking, and the vignette rewrite that followed suggests discoverability was the underlying complaint. Underneath that, the additions are steady and narrow: each release brings interval-aware versions of plot types that already exist for point data, which is the whole premise of the package.

◆ Prediction

The pattern of porting one more standard plot type into interval-aware form each release is the most likely continuation; the tsplot compatibility in the latest version hints that time-series interval data is the direction attracting attention.

P
phyloatlas
INFRA · APIS
0.0

An atlas of the tree of life that keeps publishing what it got wrong, and stopped shipping the trees it does not own.

◆ Current state

This is a curated deposit of species-level phylogenies — 264 trees across 62 partitions, 247 of them time-calibrated — paired with a species-name dictionary of roughly 638,000 standardized labels and per-tree provenance. It is moving through peer review at Methods in Ecology and Evolution, and the release stream is essentially a public erratum log: eight releases in five weeks, each reconciling the deposit against source papers, the manuscript, and its own metadata. The most recent replaced the turtle canonical with a 274-tip ultrametric chronogram after the previous tree failed time-calibration integrity checks.

◆ Where it's heading

The project's defining decision is that it archives the recipe rather than the corpus. Since 1.0.3 the Zenodo deposit holds metadata, provenance, and standardization code while the tree files live at their original sources, and the same principle was applied again when the TimeTree-of-Life was removed at the TimeTree project's request and reduced to a citation. What makes the correction log unusual is its direction: partitions keep getting reclassified from dated to undated as verification confirms the source papers described chronograms they never deposited. The atlas is being built to be honest about archival uncertainty rather than to maximize coverage.

◆ Prediction

The release cadence is driven by the manuscript review cycle, so expect corrections to continue until MEE acceptance and then slow sharply; the open thread most likely to produce the next one is the remaining recoverable archival uncertainty flagged across non-Condamine dated source trees.

Alternatives to ggInterval and phyloatlas

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 ggInterval or phyloatlas.

See all ggInterval alternatives → · See all phyloatlas alternatives →

Recent activity from ggInterval and phyloatlas

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1mo agophyloatlasv1.0.8 — turtle chronogram canonical; MEE integrity pass
  2. 1mo agophyloatlasv1.0.7 — restore species-name dictionary
  3. 1mo agophyloatlasv1.0.6 — data-integrity corrections + TimeTree de-redistribution
  4. 2mo agophyloatlasv1.0.5 — consistency corrections
  5. 2mo agophyloatlasv1.0.4 — data corrections + canonical succession (Supplementary Table S7)
  6. 2mo agophyloatlasv1.0.3 — title alignment, LICENSE, three-category framework, sensitivity bounds
  7. 3mo agoggIntervalInterval correlation heatmaps and time-series-compatible line plots
  8. 6mo agoggIntervalExamples switched to donttest per CRAN review
  9. 6mo agoggIntervalVignette rewritten to cover every plot function
  10. 6mo agoggIntervalSeven plot functions renamed for consistency

Frequently asked questions

What is the difference between ggInterval and phyloatlas?

They serve adjacent needs but don't currently overlap on shipped themes. ggInterval and phyloatlas 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 ggInterval better than phyloatlas?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ggInterval and phyloatlas 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 ggInterval?

Top ggInterval alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggInterval alternatives" section above for the current picks, or visit /alternatives/gginterval for the full list with editorial commentary on each.

What are the best alternatives to phyloatlas?

Top phyloatlas alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "phyloatlas alternatives" section above for the current picks, or visit /alternatives/phylo-species-atlas for the full list with editorial commentary on each.