ggpointless
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
A side-by-side editorial comparison of glcdp and Rmonize — release velocity, themes, recent moves, and the top alternatives to consider.
glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.
glcdp imports light-logger data packages published to the GLC standard, driven by declared schemas rather than format-specific readers. 0.9.3 added glc_explore(), a Shiny application for browsing the registry and exporting an annotated reproducible script. 1.0.0 promotes schema 3.0.2 to the default and primary stable import contract and makes schema-declared variable types and factor-level order drive the import itself.
Collapsed a pile of parameters into one object and renamed every report column
Rmonize supports data harmonization: taking heterogeneous input datasets, applying processing rules against a DataSchema, and producing a harmonized dossier with assessment, summary and visual reports. Version 2.0.0 reshaped how that is driven — the evaluate, summarize and visualize functions now take the dossier alone rather than six or seven parallel arguments — and renamed every column in the assessment and summary outputs into plain language. The package is closely coupled to madshapR, whose changes the notes warn may require updates to existing user code.
glcdp imports light-logger data packages published to the GLC standard, driven by declared schemas rather than format-specific readers. 0.9.3 added glc_explore(), a Shiny application for browsing the registry and exporting an annotated reproducible script. 1.0.0 promotes schema 3.0.2 to the default and primary stable import contract and makes schema-declared variable types and factor-level order drive the import itself.
The package is serving two audiences from one model. Programmatic users get glc_collect(), extract_metadata() and add_metadata(), with imports that reject file groups whose factor labels or level order disagree. Interactive users get an Explorer that filters by device, wearing position, modality, role and data state, pages large inventories at 100 rows, and caches remote metadata for immutable revisions. Schemas 1.0.0 and 2.0.0 stay reachable as barebones legacy paths.
With 3.0.2 named the primary stable contract and the older schemas explicitly labelled legacy, retiring the barebones paths is the most likely next structural move. The notes give no indication of work beyond the current schema line.
Rmonize supports data harmonization: taking heterogeneous input datasets, applying processing rules against a DataSchema, and producing a harmonized dossier with assessment, summary and visual reports. Version 2.0.0 reshaped how that is driven — the evaluate, summarize and visualize functions now take the dossier alone rather than six or seven parallel arguments — and renamed every column in the assessment and summary outputs into plain language. The package is closely coupled to madshapR, whose changes the notes warn may require updates to existing user code.
The arc runs from correctness toward interface. Version 1.0.1 was bug fixes found on real data, 1.1.0 added a debug parameter so harmonization could be tested with incomplete inputs, and 2.0.0 is a deliberate simplification that breaks existing code in exchange for a smaller surface. Renaming outputs from expressions like 'Categories::missing' and 'Nb. non-valid values' to 'Non-valid categories' and 'Number of non-valid values' points at reports being read by people who are not the person who wrote the harmonization rules.
Expect the superseded parameters and the renamed demo object to be removed outright rather than left superseded, and continued work on the visual reports, which carry the largest volume of referenced issues across all three versions.
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 glcdp or Rmonize.
ggpointless keeps adding the ggplot2 layers nobody else bothered to write.
mpactr spent two spring releases normalizing case in metadata after users kept tripping on it.
surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.
surveycore declared its API stable with every survey design type covered.
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
prospectr spent its biggest release in years fixing spectra it had been quietly mangling.
See all glcdp alternatives → · See all Rmonize alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. glcdp is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. glcdp is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top glcdp alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "glcdp alternatives" section above for the current picks, or visit /alternatives/glcdp for the full list with editorial commentary on each.
Top Rmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rmonize alternatives" section above for the current picks, or visit /alternatives/rmonize for the full list with editorial commentary on each.