← Back to home
Comparison · Analytics

osmdata vs posterior

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

osmdata vs posterior: at a glance

Featureosmdataposterior
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, overpass-api, spatial-data, breaking-changesbayesian, rvar, pareto-diagnostics, r-infrastructure
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

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.

Read the full osmdata trajectory →

What is posterior?

posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.

The releases in this window advance on two fronts. The rvar random-variable type gained factor and ordered subtypes (1.4.0), rvar-indexed slicing and `rvar_ifelse()` (1.5.0), base `%*%` matrix multiplication and indexed variable names (1.6.0). Separately, Pareto diagnostics have grown from `pareto_smooth()` options and individual `pareto_khat()`-family functions (1.6.0) through `pit()` for draws and rvars (1.6.1) to exported generalized-Pareto functions and `pareto_pit` (1.7.0). 1.7.1 is a paperwork release for a JOSS submission.

Read the full posterior trajectory →

osmdata vs posterior: editorial side-by-side

O
osmdata
ANALYTICS
0.0

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.

P
posterior
ANALYTICS
0.0

posterior keeps deepening two things: the rvar type and Pareto-based diagnostics.

◆ Current state

The releases in this window advance on two fronts. The rvar random-variable type gained factor and ordered subtypes (1.4.0), rvar-indexed slicing and `rvar_ifelse()` (1.5.0), base `%*%` matrix multiplication and indexed variable names (1.6.0). Separately, Pareto diagnostics have grown from `pareto_smooth()` options and individual `pareto_khat()`-family functions (1.6.0) through `pit()` for draws and rvars (1.6.1) to exported generalized-Pareto functions and `pareto_pit` (1.7.0). 1.7.1 is a paperwork release for a JOSS submission.

◆ Where it's heading

posterior is positioning itself as shared infrastructure rather than an end-user package: 1.7.0 explicitly exports generalized-Pareto machinery 'for use in other packages', and the JOSS paper is a citation vehicle for the same audience. The rvar work points the same way — a random-variable type other Bayesian packages can build on. Cadence is steady but unhurried, roughly one feature release a year.

◆ Prediction

More diagnostic functions are likely to be exported for downstream reuse, following the pattern 1.7.0 established with the generalized-Pareto helpers.

Alternatives to osmdata and posterior

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 osmdata or posterior.

See all osmdata alternatives → · See all posterior alternatives →

Recent activity from osmdata and posterior

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

  1. 1mo agoosmdataosmdata 0.4.0
  2. 2mo agoposteriorposterior 1.7.1 released for JOSS paper
  3. 3mo agoposteriorposterior 1.7.0 exports generalized-Pareto functions
  4. 10mo agoposteriorposterior 1.6.1 adds pit() for draws and rvars
  5. 11mo agoosmdataosmdata 0.3.0
  6. 1y agoposteriorposterior 1.6.0 adds Pareto diagnostics and ESS-based thinning
  7. 2y agoposteriorposterior 1.5.0 adds nested-Rhat and rvar indexing
  8. 2y agoosmdataosmdata 0.2.5 resubmitted after CRAN removal
  9. 3y agoosmdataosmdata 0.2.3 fixes test broken by sp deprecation
  10. 3y agoosmdataosmdata 0.2.2 adds out:csv queries and centre coordinates
  11. 3y agoosmdataosmdata 0.2.1 deprecates nodes_only, fixes memory leaks
  12. 3y agoposteriorposterior 1.4.0 adds factor and ordered rvar subtypes

Frequently asked questions

What is the difference between osmdata and posterior?

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

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

What are the best alternatives to posterior?

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