← Back to home
Comparison · Analytics

climaemet vs vellum

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

climaemet vs vellum: at a glance

Featureclimaemetvellum
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesweather-data, aemet, spain, rate-limitingr-graphics, rendering-engine, linting, accessibility
Last editorial update1h ago52m ago
WebsiteVisit →Visit →

What is climaemet?

climaemet added weather alerts and wildfire risk, then spent two years managing rate limits.

climaemet wraps Spain's AEMET meteorological API — station data, historical climate series, forecasts, and the plotting helpers that go with them. Its capability surface widened decisively in 1.4.0 with meteorological alerts and wildfire risk rasters. Everything since has been about surviving the API rather than extending it: multiple API keys, quota-aware key selection, and httr2 throttling pinned to AEMET's stated 40-connections-per-minute policy.

Read the full climaemet trajectory →

What is vellum?

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.

Read the full vellum trajectory →

climaemet vs vellum: editorial side-by-side

C
climaemet
ANALYTICS
0.0

climaemet added weather alerts and wildfire risk, then spent two years managing rate limits.

◆ Current state

climaemet wraps Spain's AEMET meteorological API — station data, historical climate series, forecasts, and the plotting helpers that go with them. Its capability surface widened decisively in 1.4.0 with meteorological alerts and wildfire risk rasters. Everything since has been about surviving the API rather than extending it: multiple API keys, quota-aware key selection, and httr2 throttling pinned to AEMET's stated 40-connections-per-minute policy.

◆ Where it's heading

Two forces shape this package, and neither is feature demand. The first is AEMET's own churn — new response codes, a fires endpoint that switched to six risk levels returned as named factors, municipality datasets refreshed annually. The second is the maintainer's cross-package modernization, visible here as the API key store moving to tools::R_user_dir() with automatic migration, a configurable timeout, cli messaging, and an R 4.1 floor. The 1.6.0 refactor is stated as AI-assisted, matching the maintainer's other packages.

◆ Prediction

Expect the next release to track another AEMET endpoint change rather than add a data domain; the throttling and multi-key machinery suggests quota pressure is the constraint the maintainer keeps returning to.

V
vellum
ANALYTICS
5.0

vellum's bugs are now found by using it, not testing it — the downstream grammar is doing the QA.

◆ Current state

The rendering engine shipped nine releases in the two weeks around the end of July, six of them on a single day. Almost every entry is a correctness fix in a capability that worked when drawn and failed when measured, or worked in isolation and failed in composition. The release notes are unusually forensic: each one states the mechanism, the observable symptom, and why the fix mirrors the draw path rather than reimplementing it.

◆ Where it's heading

The pivotal detail is stated outright in 0.6.3 — the first bug in the series found by using the engine from vellumplot rather than testing it in isolation. Every release since names the downstream as the source: the contrast rule's false positives, the lint rules that fired on all five sample plots, the keyed roundrect batch. A rendering engine with a real grammar built on top of it is now getting the integration coverage that unit tests structurally cannot provide, and the fixes are converging on one theme: the measurement path and the draw path must not drift.

◆ Prediction

Expect the release rate to fall as the vellumplot integration surface is exhausted, with remaining work concentrated in the lint rule set now that it is meant to gate builds rather than just inform.

Alternatives to climaemet and vellum

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 climaemet or vellum.

See all climaemet alternatives → · See all vellum alternatives →

Recent activity from climaemet and vellum

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

  1. 11d agovellumLinter grows to 20 rules and stops firing on every plot
  2. 13d agovellumAnimated SVGs no longer blink once and vanish or play in reverse
  3. 13d agovellumPick table now reports device pixels instead of two coordinate systems
  4. 14d agovellumContrast rule stops flagging every plot; gridlines become PDF artifacts
  5. 14d agovellumgrobwidth and grobheight now measure wrapped text, not the unwrapped line
  6. 14d agovellumKeyed roundrect becomes a real batch after downstream integration exposes it
  7. 2mo agoclimaemetAPI keys move to R_user_dir; fire risk returns named factors
  8. 4mo agoclimaemetVignettes migrated to Quarto
  9. 7mo agoclimaemetRequest throttling pinned to AEMET's 40-per-minute policy
  10. 1y agoclimaemetggwindrose rebuilt on coord_radial
  11. 1y agoclimaemetHighest-quota API key now chosen per call
  12. 1y agoclimaemetWeather alerts and wildfire risk rasters added

Frequently asked questions

What is the difference between climaemet and vellum?

They serve adjacent needs but don't currently overlap on shipped themes. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is climaemet better than vellum?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. vellum is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to climaemet?

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

What are the best alternatives to vellum?

Top vellum alternatives in Analytics are ranked by recent ship velocity. Browse the "vellum alternatives" section above for the current picks, or visit /alternatives/vellum-r for the full list with editorial commentary on each.