n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A side-by-side editorial comparison of citeme and mapSpain — release velocity, themes, recent moves, and the top alternatives to consider.
Citation metadata machinery breaks out of INBO's checklist package to stand on its own.
citeme handles citation metadata for research software and organisations — building citation files, validating ORCIDs, RORs, licenses and URLs, and prompting for the pieces interactively. It was extracted from the checklist package in 0.1.0 and has spent the four releases since fleshing out organisational roles, most visibly publishers.
mapSpain's 1.0.0 broke every user cache to get the package onto modern foundations.
mapSpain provides administrative boundaries, tile providers and geographic dictionaries for Spain, pulling from GISCO, SIANE, INE and IGN sources. The 1.0.0 release in January 2026 rebuilt it: requests moved to httr2, the cache reorganized into topic-based subfolders under tools::R_user_dir() instead of rappdirs, R 4.1 became the floor, and every function now returns tidy objects. Existing caches are explicitly incompatible and must be rebuilt.
citeme handles citation metadata for research software and organisations — building citation files, validating ORCIDs, RORs, licenses and URLs, and prompting for the pieces interactively. It was extracted from the checklist package in 0.1.0 and has spent the four releases since fleshing out organisational roles, most visibly publishers.
Development is running in tight monthly increments along two tracks: modelling who is attached to a piece of research software, and smoothing the interactive prompts that collect it. The publisher role added in 0.1.1 propagated through validation, community detection and YAML handling over the next two releases, which is how this package tends to land a concept — introduce the class field, then follow it everywhere it needs to reach.
Expect the interactive ask_* family to keep growing alongside whatever metadata field is being modelled next, and further alignment with the checklist package it was carved out of.
mapSpain provides administrative boundaries, tile providers and geographic dictionaries for Spain, pulling from GISCO, SIANE, INE and IGN sources. The 1.0.0 release in January 2026 rebuilt it: requests moved to httr2, the cache reorganized into topic-based subfolders under tools::R_user_dir() instead of rappdirs, R 4.1 became the floor, and every function now returns tidy objects. Existing caches are explicitly incompatible and must be rebuilt.
The package has finished its modernization and moved into consolidation. 1.1.0 added a configurable query timeout and pinned httr2 for compatibility with giscoR, the sibling package it shares plumbing with; 1.2.0 was a declared internal-only refactor with the public API held fixed and the work described as AI-assisted with human review. The data-source expansion that characterized the 0.9.x and 0.10.x line — comarcas by type, simplified INE geometries, SIANE vintages — has paused while the foundations settle.
Expect a return to source coverage now that the refactor is done: new SIANE or INE vintages and additional boundary types are the pattern this package has repeated. The entries show no further architectural work queued.
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 citeme or mapSpain.
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all citeme alternatives → · See all mapSpain alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. citeme and mapSpain 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. citeme and mapSpain 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 Analytics products to evaluate alongside.
Top citeme alternatives in Analytics are ranked by recent ship velocity. Browse the "citeme alternatives" section above for the current picks, or visit /alternatives/citeme-r for the full list with editorial commentary on each.
Top mapSpain alternatives in Analytics are ranked by recent ship velocity. Browse the "mapSpain alternatives" section above for the current picks, or visit /alternatives/mapspain for the full list with editorial commentary on each.