← Back to home
Comparison · Analytics

crossmap vs gdverse

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

Shared themes:r package

crossmap vs gdverse: at a glance

Featurecrossmapgdverse
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themespurrr extension, functional programming, deprecations, furrrspatial statistics, geographical detector, confidence intervals, reticulate
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is crossmap?

crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.

A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.

Read the full crossmap trajectory →

What is gdverse?

gdverse is turning geographical detector methods into inference, not just point estimates.

A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.

Read the full gdverse trajectory →

crossmap vs gdverse: editorial side-by-side

C
crossmap
ANALYTICS
0.0

crossmap's roadmap is set by purrr and furrr — it deprecates what upstream deprecates.

◆ Current state

A small package for mapping over combinations of arguments, following purrr and furrr conventions. Its own functional additions stopped after xpluck() in 2023 and the cross_fit() clustering work in 2022. Everything since tracks upstream: xmap_raw() and future_xmap_raw() are now defunct because purrr removed map_raw() and furrr removed future_pmap_raw(), and re-exported parallel helpers now come from parallelly rather than future.

◆ Where it's heading

The package has settled into being a compatible extension rather than an independent one — its release notes read as a mirror of purrr's and furrr's deprecation schedules. Note that the release stamps are unreliable here: several versions were backfilled minutes apart and the 0.3.x tags carry timestamps in reverse version order, so feed position says nothing about what shipped when.

◆ Prediction

Expect the next release to be driven by another purrr or furrr change rather than new functionality, since that has been the sole trigger for the last four.

G
gdverse
ANALYTICS
0.0

gdverse is turning geographical detector methods into inference, not just point estimates.

◆ Current state

A geographical detector toolkit for spatial stratified heterogeneity, shipping small numbered releases every few months. Recent work centres on statistical rigour: confidence intervals for the q-statistic (experimental in 1.3-2, made more robust in 1.6), reported significance for interaction detection, and a fix for stratification collision in that same interaction path. The rest is Python-interop maintenance — reticulate compatibility, parallel stability in cpd_disc, and dependency configuration.

◆ Where it's heading

The arc is from computing detector statistics to qualifying them. Confidence intervals, significance reporting and non-centrality parameter estimation are all about telling users how much to trust a q-value, which is the gap between a research script and a package other people cite. The Python-dependency work is the recurring tax on that: several releases exist mainly to keep reticulate-backed models passing checks.

◆ Prediction

Expect the experimental q-statistic confidence intervals to be promoted to a stable, documented interface across the detector family, since the last two releases have both worked on their robustness and reporting.

Alternatives to crossmap and gdverse

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 crossmap or gdverse.

See all crossmap alternatives → · See all gdverse alternatives →

Recent activity from crossmap and gdverse

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

  1. 6mo agogdverseInteraction detection reports significance; stratification collision fixed
  2. 6mo agocrossmapRaw-vector mapping functions removed
  3. 6mo agocrossmapRe-exports moved to the parallelly namespace
  4. 10mo agogdversePython examples wrapped to stop CRAN check failures
  5. 10mo agogdversecpd_disc refactored for parallel stability and reticulate compatibility
  6. 11mo agocrossmapFuture-backed tests skipped on CRAN
  7. 11mo agocrossmapInternal test fixes
  8. 1y agogdverseAdds package citation metadata
  9. 1y agogdverseExperimental confidence intervals for the q statistic
  10. 1y agogdversePlot method bug fixes across four detector models
  11. 3y agocrossmapxpluck adds multi-index plucking
  12. 4y agocrossmapCluster specifications supported in cross_fit

Frequently asked questions

What is the difference between crossmap and gdverse?

Both compete on the same themes — r package — within Analytics. crossmap and gdverse 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 crossmap better than gdverse?

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

What are the best alternatives to crossmap?

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

What are the best alternatives to gdverse?

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