rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
osmdata vs taxa
A side-by-side editorial comparison of osmdata and taxa — release velocity, themes, recent moves, and the top alternatives to consider.
osmdata vs taxa: at a glance
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.
What is taxa?
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
osmdata vs taxa: editorial side-by-side
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.
taxa
0.0ANALYTICS
taxa started a ground-up rewrite in 2021 and has published almost nothing since.
◆ Current state
0.4.0 began a complete rewrite aimed at making the component classes behave like base R vectors, explicitly shipping without the `taxmap` class and parking the old implementation inside metacoder until the new one matured. Four years later that is still where things stand: 0.4.2 experimented with `''` instead of `NA` for missing values and chased a vctrs test break, and 0.4.4 fixed CRAN check issues. The releases before the rewrite were the productive ones — `taxonomy_table()`, `print_tree()`, `get_dataset()`, fuzzy name matching, faster parsers.
◆ Where it's heading
The rewrite has not landed. `taxmap`, the class most users came for, was never reimplemented in the new design, and the only releases since are CRAN compliance. Meanwhile metacoder still carries the old taxa, which means the ecosystem is running on the version the rewrite was meant to replace. This reads as a stalled migration rather than an active one.
◆ Prediction
Nothing in the entries indicates the rewrite is resuming; the likely next release is another CRAN-check fix. Whether `taxmap` ever arrives in the new design is unresolved.
Alternatives to osmdata and taxa
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 taxa.
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.
rotl
rotl's whole release history is keeping name matching honest against a moving taxonomy.
taxize
taxize spends its releases absorbing other people's API changes, one dead source at a time.
See all osmdata alternatives → · See all taxa alternatives →
Recent activity from osmdata and taxa
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoosmdataosmdata 0.4.0
- 11mo agoosmdataosmdata 0.3.0
- 1y agotaxataxa 0.4.4 fixes CRAN check issues
- 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
- 4y agotaxataxa 0.4.2 tries empty strings for missing values
- 5y agotaxataxa 0.4.0 begins a base-R-vector rewrite without taxmap ⚡
- 6y agotaxataxa 0.3.4 fixes n_obs with numeric column names
- 6y agotaxataxa 0.3.3 supports numeric column names in taxmap
- 7y agotaxataxa 0.3.2 fixes parsers and adds negative class_col indexes
Frequently asked questions
What is the difference between osmdata and taxa?
They serve adjacent needs but don't currently overlap on shipped themes. osmdata and taxa 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 taxa?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmdata and taxa 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 taxa?
Top taxa alternatives in Analytics are ranked by recent ship velocity. Browse the "taxa alternatives" section above for the current picks, or visit /alternatives/taxa-r for the full list with editorial commentary on each.