← Back to home
Comparison · Analytics

osmdata vs timetk

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

osmdata vs timetk: at a glance

Featureosmdatatimetk
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, overpass-api, spatial-data, breaking-changestime-series, anomaly-detection, visualization, feature-engineering
Last editorial update57m 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 timetk?

timetk swallowed anomalize whole, then went quiet for two years

timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.

Read the full timetk trajectory →

osmdata vs timetk: 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
timetk
ANALYTICS
0.0

timetk swallowed anomalize whole, then went quiet for two years

◆ Current state

timetk handles time series wrangling, visualization, and feature engineering in a tidyverse idiom. Its defining recent move was absorbing the anomalize package outright in 2.9.0, bringing anomaly detection, cleaning, and the associated plots inside timetk rather than leaving them in a sibling package. Development then paused for nearly two years before 2.9.1, a robustness and documentation release.

◆ Where it's heading

The trajectory before the pause was consolidation: fold in adjacent functionality, then make the visualization layer handle many series at once via trelliscopejs, then broaden feature generation with tk_tsfeatures(). The recent release works on the least glamorous layer — internal generics so date parsing and sequence generation behave consistently across Date, POSIXct, hms, yearmon, and yearqtr — which is the kind of foundation work a package does when it has accumulated too many special cases. The long gap and the CI-refresh content suggest maintenance attention rather than a new direction.

◆ Prediction

The stated gap is the unimplemented twitter method for anomalize(), which is the one concrete outstanding item the release notes name; beyond that the recent work points to consolidation rather than expansion.

Alternatives to osmdata and timetk

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

See all osmdata alternatives → · See all timetk alternatives →

Recent activity from osmdata and timetk

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

  1. 1mo agoosmdataosmdata 0.4.0
  2. 11mo agotimetktimetk 2.9.1 makes date parsing consistent across time classes
  3. 11mo agoosmdataosmdata 0.3.0
  4. 2y agotimetktimetk 2.9.0 absorbs the anomalize package
  5. 2y agoosmdataosmdata 0.2.5 resubmitted after CRAN removal
  6. 3y agoosmdataosmdata 0.2.3 fixes test broken by sp deprecation
  7. 3y agoosmdataosmdata 0.2.2 adds out:csv queries and centre coordinates
  8. 3y agoosmdataosmdata 0.2.1 deprecates nodes_only, fixes memory leaks
  9. 4y agotimetktimetk 2.8.1 exposes trelliscope plotting parameters
  10. 4y agotimetktimetk 2.8.0 adds trelliscopejs support for many-series plots
  11. 4y agotimetktimetk 2.7.0 adds tk_tsfeatures() for grouped feature matrices
  12. 4y agotimetktimetk 2.6.2 adds .week_start and facet direction controls

Frequently asked questions

What is the difference between osmdata and timetk?

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

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

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