← Back to home
Comparison · Analytics

osmapiR vs simulist

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

osmapiR vs simulist: at a glance

FeatureosmapiRsimulist
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, api-client, r-language, geospatialepiverse-trace, outbreak-simulation, line-list, data-realism
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

What is osmapiR?

osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.

osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.

Read the full osmapiR 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 →

osmapiR vs simulist: editorial side-by-side

O
osmapiR
ANALYTICS
0.0

osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.

◆ Current state

osmapiR wraps the full OpenStreetMap API from R — reading and writing map data, changesets, notes, GPX traces and user records — with OAuth2 where the endpoint requires it, pagination handled internally, and atomic calls vectorised. Recent releases have filled in the moderation and social surface: note subscription, user blocks, changeset discussion search. The newest release lets `bbox` arguments arrive as a character string, matrix, vector, an sf `bbox`, or a terra `SpatExtent`.

◆ Where it's heading

Four consecutive releases open with the same line — documentation and code updated for server-side changes, cited by OSM wiki revision range. That is a maintainer treating an evolving remote API as a versioned contract and auditing against it each cycle, which is unusual discipline and the main reason to trust this client over a hand-rolled wrapper. The second thread is fitting into R's spatial conventions rather than exposing OSM's, visible in the bbox coercion work and the httr2 upgrades landing with upstream help.

◆ Prediction

The pattern is stable enough to call: another release synchronised to the next OSM wiki revision range, adding whatever endpoints appeared and adjusting whatever changed shape.

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

See all osmapiR alternatives → · See all simulist alternatives →

Recent activity from osmapiR and simulist

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

  1. 5mo agoosmapiRbbox arguments accept sf and terra objects
  2. 6mo agosimulistJOSS paper corrections
  3. 6mo agosimulistWeighted sex sampling and epiparameter objects for reporting delays
  4. 11mo agosimulistcensor_linelist() adds interval censoring and a weekend effect
  5. 0y agoosmapiRNote search defaults to creation order; JSON for GPX metadata
  6. 1y agoosmapiRNote subscriptions and user block endpoints added
  7. 1y agosimulistPost-processing arrives: truncated snapshots and deliberately messy line lists
  8. 1y agosimulistEvery sim_*() argument gains a default
  9. 1y agoosmapiRChangeset queries gain from and to parameters
  10. 1y agoosmapiRJOSS citation added; single-tag conversion fixed
  11. 2y agoosmapiRComplete OSM API coverage arrives in one release
  12. 2y agosimulistInfectious period replaces contact interval; time-varying fatality risk added

Frequently asked questions

What is the difference between osmapiR and simulist?

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

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

Top osmapiR alternatives in Analytics are ranked by recent ship velocity. Browse the "osmapiR alternatives" section above for the current picks, or visit /alternatives/osmapir 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.