← Back to home
Comparison · Infra & APIs

melodi vs surveytidy

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

melodi vs surveytidy: at a glance

Featuremelodisurveytidy
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesofficial-statistics, api-client, insee, francesurvey-statistics, tidyverse, dplyr-verbs, metadata-tracking
Last editorial update37m ago1h ago
WebsiteVisit →Visit →

What is melodi?

INSEE's statistics API gets a French R client that keeps meeting its edge cases

Rmelodi is InseeFrLab's R client for the Melodi APIs, which serve French official statistics. It reached 1.0.0 in February 2026 with the technical call parameters moved out of function arguments and into options(), and a per-request row limit raised to 100,000 on the server side. Everything since has been dataset-specific: field names that vary between datasets, geography labels, performance.

Read the full melodi trajectory →

What is surveytidy?

surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.

surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.

Read the full surveytidy trajectory →

melodi vs surveytidy: editorial side-by-side

M
melodi
INFRA · APIS
0.0

INSEE's statistics API gets a French R client that keeps meeting its edge cases

◆ Current state

Rmelodi is InseeFrLab's R client for the Melodi APIs, which serve French official statistics. It reached 1.0.0 in February 2026 with the technical call parameters moved out of function arguments and into options(), and a per-request row limit raised to 100,000 on the server side. Everything since has been dataset-specific: field names that vary between datasets, geography labels, performance.

◆ Where it's heading

The work is convergence with an API that is still moving. Version 0.3.0 added label lookups so codes become readable; 1.0.0 centralised configuration; 1.0.1 and 1.0.2 each fix a place where a real dataset does not match the assumed shape — get_range_geo() needing an extra label field, then the consumer price index series naming its value column differently from every other dataset. Release notes are in French, which is consistent with the audience.

◆ Prediction

The 1.0.x pattern is one dataset-shape exception per release, which suggests the client is still discovering how much the Melodi datasets vary rather than converging on a general parser. Expect more of the same until the variation is handled generically.

S
surveytidy
INFRA · APIS
0.0

surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.

◆ Current state

surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.

◆ Where it's heading

The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.

◆ Prediction

Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.

Alternatives to melodi and surveytidy

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 melodi or surveytidy.

See all melodi alternatives → · See all surveytidy alternatives →

Recent activity from melodi and surveytidy

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

  1. 2mo agosurveytidymutate() syncs metadata for across() recodes
  2. 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
  3. 5mo agomelodiget_data() handles value columns not named OBS_VALUE_NIVEAU
  4. 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
  5. 6mo agomelodiGeography labels added and the lookup loop vectorised
  6. 6mo agomelodiCall parameters move from arguments into options()
  7. 7mo agomelodiBroken documentation examples and vcr 2 test migration
  8. 8mo agomelodiCode label lookups for geography and every other dimension

Frequently asked questions

What is the difference between melodi and surveytidy?

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

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

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

What are the best alternatives to surveytidy?

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