Lightdash
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A side-by-side editorial comparison of maplegend and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | maplegend | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | cartography, legends, base-graphics, spatial | reporting, agencies, integrations, reliability |
| Last editorial update | 5d ago | 57m ago |
| Website | Visit → | — |
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Whatagraph is working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removed live API calls from render time in the Basis rebuild, connection failover keeps widgets alive when one teammate's token expires, and report shortcuts let a heavy report be split into a hub with supporting detail. Presentation control arrives steadily alongside — automatic conditional formatting, per-metric decimal places, chosen comparison colors. The newest change moves unified-field mapping into the Source Group builder, so a cross-channel group can be fixed in place instead of rebuilt.
maplegend draws the legends for base-R thematic maps, extracted from mapsf so both packages could evolve the legend vocabulary independently. It has been catching up to the map types it has to serve: 0.6.0 added choro_point, choro_line, and choro_symb for choropleth legends rendered on circles, lines, and symbols, following the histogram legend type in 0.4.0. Considerable effort has gone into behaving correctly when the plot aspect ratio is not 1, which required refactoring most of the package in 0.4.0 and still produced a proportional-symbol segment sizing fix in 0.6.3.
This is a support library whose backlog is defined by its caller. Every legend type mapsf can produce needs a matching legend renderer, and the release notes are dominated by spacing, offset, and border details — box_cex for symbol spacing, NA box placement in horizontal choropleth legends, text overflow when no_data is set. The shared vocabulary with mapsf is being maintained deliberately, with val_rnd, val_big, and val_dec propagating through legend types release by release. Version numbering is not monotonic in this feed, with 0.4.0 published seconds after 0.5.0.
Expect the remaining combined map types to acquire matching legends and the val_* formatting arguments to reach the types that still lack them.
Whatagraph is working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removed live API calls from render time in the Basis rebuild, connection failover keeps widgets alive when one teammate's token expires, and report shortcuts let a heavy report be split into a hub with supporting detail. Presentation control arrives steadily alongside — automatic conditional formatting, per-metric decimal places, chosen comparison colors. The newest change moves unified-field mapping into the Source Group builder, so a cross-channel group can be fixed in place instead of rebuilt.
The through-line is reliability and workflow cost at agency scale, where one account runs hundreds or thousands of sources across several people. Each release picks a specific moment where that scale used to force a detour — a dead token, a forty-widget report, a half-built source group — and removes the detour rather than adding a capability. Integration work stays additive and named: Ahrefs Rank Tracker, WhatConverts, Snowflake, bol., each filling a stated reporting gap rather than broadening a connector catalog.
Expect the same volume-driven treatment applied to the remaining multi-step setup flows, and further integrations chosen to close named gaps rather than to grow the connector count.
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 maplegend or Whatagraph.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
See all maplegend alternatives → · See all Whatagraph alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Whatagraph 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Whatagraph 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.
Top maplegend alternatives in Analytics are ranked by recent ship velocity. Browse the "maplegend alternatives" section above for the current picks, or visit /alternatives/maplegend for the full list with editorial commentary on each.
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.