← Back to home
Comparison · Analytics

osmdata vs tidyclust

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

osmdata vs tidyclust: at a glance

Featureosmdatatidyclust
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, overpass-api, spatial-data, breaking-changestidyclust, clustering, tidymodels, dbscan
Last editorial update58m 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 tidyclust?

tidyclust just tripled the model types it can fit, and handed finalization back to tune

tidyclust brings clustering into the tidymodels interface, and 0.3.0 was the release where its model coverage stopped being k-means and hierarchical clustering. DBSCAN and HDBSCAN, Gaussian mixtures, and mean shift all arrived at once as proper clustering specifications. The two releases since have been bug fixes on the metric and sparse-data paths, which is the usual pattern after a large surface addition.

Read the full tidyclust trajectory →

osmdata vs tidyclust: 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.

T
tidyclust
ANALYTICS
0.0

tidyclust just tripled the model types it can fit, and handed finalization back to tune

◆ Current state

tidyclust brings clustering into the tidymodels interface, and 0.3.0 was the release where its model coverage stopped being k-means and hierarchical clustering. DBSCAN and HDBSCAN, Gaussian mixtures, and mean shift all arrived at once as proper clustering specifications. The two releases since have been bug fixes on the metric and sparse-data paths, which is the usual pattern after a large surface addition.

◆ Where it's heading

The package is converging with the rest of tidymodels rather than maintaining a parallel API: finalize_model_tidyclust() and finalize_workflow_tidyclust() are deprecated because tune::finalize_model() and tune::finalize_workflow() now handle cluster_spec objects natively. That removes the last place where clustering needed its own version of a shared verb. With density-based and model-based clustering now present, the interface has to cover model families with genuinely different assumptions than the centroid methods it started with.

◆ Prediction

The recent fixes to cluster_metric_set() labeling and custom-metric authoring suggest evaluation is the current focus, so metrics suited to density-based clusters are the likely next addition.

Alternatives to osmdata and tidyclust

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 tidyclust.

See all osmdata alternatives → · See all tidyclust alternatives →

Recent activity from osmdata and tidyclust

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

  1. 1mo agotidyclusttidyclust 0.3.2 fixes k_means() on sparse predictors
  2. 1mo agotidyclusttidyclust 0.3.1 stops same-named metrics silently merging
  3. 1mo agoosmdataosmdata 0.4.0
  4. 2mo agotidyclusttidyclust 0.3.0 adds DBSCAN, Gaussian mixture, and mean shift models
  5. 11mo agoosmdataosmdata 0.3.0
  6. 1y agotidyclusttidyclust 0.2.4 switches distance calculations to philentropy
  7. 2y agotidyclusttidyclust 0.2.3 resolves a clustMixType reverse-dependency issue
  8. 2y agotidyclusttidyclust 0.2.2 resolves a ClusterR reverse-dependency issue
  9. 2y agoosmdataosmdata 0.2.5 resubmitted after CRAN removal
  10. 3y agoosmdataosmdata 0.2.3 fixes test broken by sp deprecation
  11. 3y agoosmdataosmdata 0.2.2 adds out:csv queries and centre coordinates
  12. 3y agoosmdataosmdata 0.2.1 deprecates nodes_only, fixes memory leaks

Frequently asked questions

What is the difference between osmdata and tidyclust?

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

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

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