rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
bayestestR vs osmdata
A side-by-side editorial comparison of bayestestR and osmdata — release velocity, themes, recent moves, and the top alternatives to consider.
bayestestR vs osmdata: at a glance
What is bayestestR?
Bayesian diagnostics get stricter defaults while the Stan backend list widens
bayestestR is the diagnostics and hypothesis-testing layer of the easystats stack, and its recent releases have concentrated on two things: reporting the right uncertainty numbers by default, and accepting posterior draws from more sources. The 0.18.x line added CmdStanFit support alongside the existing rstanarm/brms paths and switched effective-sample-size reporting to tail-ESS. Bug-fix releases in between are mostly CRAN-check maintenance.
What is osmdata?
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
The last two releases are the substantive ones. 0.4.0 lets `getbb()` resolve OSM relations via Wikidata ids, adds `filter_osm_user()` to Overpass query objects, and corrects metadata typing so timestamps are POSIXct rather than locale-dependent strings. 0.3.0 dropped the re-exported magrittr pipe, raised the R floor to 4.1 for the base pipe, and fixed polygon output to follow the OGC simple-features model instead of treating every ring as an independent polygon. Earlier entries are CRAN repairs and query-construction fixes.
bayestestR vs osmdata: editorial side-by-side
bayestestR
0.0ANALYTICS
Bayesian diagnostics get stricter defaults while the Stan backend list widens
◆ Current state
bayestestR is the diagnostics and hypothesis-testing layer of the easystats stack, and its recent releases have concentrated on two things: reporting the right uncertainty numbers by default, and accepting posterior draws from more sources. The 0.18.x line added CmdStanFit support alongside the existing rstanarm/brms paths and switched effective-sample-size reporting to tail-ESS. Bug-fix releases in between are mostly CRAN-check maintenance.
◆ Where it's heading
The package is converging on a single posture: work with raw MCMC draws from anywhere, and report the diagnostic that actually governs the interval being shown. Successive releases have swapped defaults rather than added surface area, and the efficiency work in 0.16.x aimed squarely at large brms and rstanarm fits. Output formatting is drifting toward the shared easystats display() and tinytable path.
◆ Prediction
Expect continued backend coverage on the Stan side and further alignment of print/display behavior with insight and the rest of easystats; the entries do not show a push into new inference methods.
osmdata
0.0ANALYTICS
osmdata keeps tightening its Overpass query surface, breaking small things to get types right.
◆ Current state
The last two releases are the substantive ones. 0.4.0 lets `getbb()` resolve OSM relations via Wikidata ids, adds `filter_osm_user()` to Overpass query objects, and corrects metadata typing so timestamps are POSIXct rather than locale-dependent strings. 0.3.0 dropped the re-exported magrittr pipe, raised the R floor to 4.1 for the base pipe, and fixed polygon output to follow the OGC simple-features model instead of treating every ring as an independent polygon. Earlier entries are CRAN repairs and query-construction fixes.
◆ Where it's heading
The pattern is deliberate correctness work: each release accepts a small breaking change to make returned objects match the standard they claim to follow, whether that is OGC polygon structure, POSIXct timestamps, or UTF-8 metadata columns. Alongside it, the Overpass query builder keeps gaining filters — by area, by out type, by osm_types, now by user and via Wikidata. The package is maturing rather than expanding.
◆ Prediction
More Overpass filter and query-object composition helpers are the likeliest next additions, since that is where both recent releases put their new surface.
Alternatives to bayestestR and osmdata
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 bayestestR or osmdata.
writexl
writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.
rgbif
rgbif is steadily pushing users off paged searching and onto real downloads.
rstanarm
rstanarm is community-maintained now, tracking Stan and lme4 rather than adding models.
taxa
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
See all bayestestR alternatives → · See all osmdata alternatives →
Recent activity from bayestestR and osmdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoosmdataosmdata 0.4.0
- 2mo agobayestestRmcse() gains a centrality argument
- 2mo agobayestestRCmdStanFit support and tail-ESS as the default diagnostic
- 11mo agobayestestRrope() gains complement probabilities; display() methods added
- 11mo agoosmdataosmdata 0.3.0
- 1y agobayestestRdescribe_posterior() efficiency and multinomial handling
- 1y agobayestestReffects argument changes behavior for large brms/rstanarm fits
- 1y agobayestestRTail ESS returned from effective_sample() and its callers
- 2y agoosmdataosmdata 0.2.5 resubmitted after CRAN removal
- 3y agoosmdataosmdata 0.2.3 fixes test broken by sp deprecation
- 3y agoosmdataosmdata 0.2.2 adds out:csv queries and centre coordinates
- 3y agoosmdataosmdata 0.2.1 deprecates nodes_only, fixes memory leaks
Frequently asked questions
What is the difference between bayestestR and osmdata?
They serve adjacent needs but don't currently overlap on shipped themes. bayestestR and osmdata 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 bayestestR better than osmdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bayestestR and osmdata 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 bayestestR?
Top bayestestR alternatives in Analytics are ranked by recent ship velocity. Browse the "bayestestR alternatives" section above for the current picks, or visit /alternatives/bayestestr for the full list with editorial commentary on each.
What are the best alternatives to osmdata?
Top osmdata alternatives in Analytics are ranked by recent ship velocity. Browse the "osmdata alternatives" section above for the current picks, or visit /alternatives/osmdata for the full list with editorial commentary on each.