← Back to home
Comparison · Analytics

GSODR vs simulist

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

GSODR vs simulist: at a glance

FeatureGSODRsimulist
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesropensci, weather-data, r-package, noaaepiverse-trace, outbreak-simulation, line-list, data-realism
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is GSODR?

A weather-station data client that broke one return type to hand back distances instead of bare IDs.

GSODR fetches and tidies NOAA Global Surface Summary of the Day weather data for R. The 4.0.0 release made nearest_stations() return a data.table of full station metadata plus distance in kilometres rather than a character vector of station IDs, with a documented one-liner for anyone who only wanted the IDs. Nothing has shipped since March 2024.

Read the full GSODR trajectory →

What is simulist?

simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.

simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.

Read the full simulist trajectory →

GSODR vs simulist: editorial side-by-side

G
GSODR
ANALYTICS
0.0

A weather-station data client that broke one return type to hand back distances instead of bare IDs.

◆ Current state

GSODR fetches and tidies NOAA Global Surface Summary of the Day weather data for R. The 4.0.0 release made nearest_stations() return a data.table of full station metadata plus distance in kilometres rather than a character vector of station IDs, with a documented one-liner for anyone who only wanted the IDs. Nothing has shipped since March 2024.

◆ Where it's heading

The package is mature and its releases read as upkeep: refreshing the internal ISD history database, dropping dependencies in favour of base and curl, and hardening the download path against station-year combinations that do not exist. The 4.0.0 change fits the same pattern of returning more structure by default rather than making callers query twice.

◆ Prediction

The most likely next release is another internal station-history refresh; there is no signal of new data sources or analysis features in these entries.

S
simulist
ANALYTICS
0.0

simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.

◆ Current state

simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.

◆ Where it's heading

The scope moved outward in two steps. 0.5.0 added truncate_linelist() and messy_linelist() to produce right-truncated snapshots and data with missingness and inconsistencies; 0.6.0 added censor_linelist() for grouping dates into intervals with a weekend-reporting effect. The simulation core has meanwhile settled — 0.7.0's changes are interface polish: weighted sex sampling and <epiparameter> objects accepted for reporting_delay.

◆ Prediction

Post-processing is where the recent work is, so further realism controls — additional reporting artefacts or interval schemes — are a likelier next step than new epidemic model structures.

Alternatives to GSODR and simulist

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 GSODR or simulist.

See all GSODR alternatives → · See all simulist alternatives →

Recent activity from GSODR and simulist

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

  1. 6mo agosimulistJOSS paper corrections
  2. 6mo agosimulistWeighted sex sampling and epiparameter objects for reporting delays
  3. 11mo agosimulistcensor_linelist() adds interval censoring and a weekend effect
  4. 1y agosimulistPost-processing arrives: truncated snapshots and deliberately messy line lists
  5. 1y agosimulistEvery sim_*() argument gains a default
  6. 2y agosimulistInfectious period replaces contact interval; time-varying fatality risk added
  7. 2y agoGSODRnearest_stations() returns metadata and distances
  8. 2y agoGSODRStation history refresh and internal tidying
  9. 2y agoGSODRBad station-year requests warn instead of failing the batch

Frequently asked questions

What is the difference between GSODR and simulist?

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

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

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

What are the best alternatives to simulist?

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