rnaturalearth
rnaturalearth finished its sp exit and is now optimising how the data actually arrives.
Comparison · Analytics
osmdata vs taxize
A side-by-side editorial comparison of osmdata and taxize — release velocity, themes, recent moves, and the top alternatives to consider.
osmdata vs taxize: 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 taxize?
taxize spends its releases absorbing other people's API changes, one dead source at a time.
The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.
osmdata vs taxize: 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.
taxize
0.0ANALYTICS
taxize spends its releases absorbing other people's API changes, one dead source at a time.
◆ Current state
The most recent work is migration: 0.10.0 replaced the deprecated Global Names Resolver functions with GNA equivalents (`gna_verifier`, `gna_parse`), rewrote `scrapenames` for the new API, and updated its rredlist usage to match that package's own v4 rewrite. 0.10.1 then tuned `gna_verifier`'s batch size to 50. The older entries in the window show the same shape from a different angle: `tnrs()` made defunct because the service died, COL dropped over rate limiting, NatureServe reworked for a new API, and a package-wide parameter rename to `sci` / `com` / `id` / `sci_com` / `sci_id`.
◆ Where it's heading
taxize's job is aggregating a dozen taxonomic databases, so most of its engineering is downstream of decisions it does not control — sources go away, endpoints change, rate limits appear. The visible trend is consolidation: fewer, better-maintained backends rather than broader coverage. Release cadence has thinned to roughly one a year, and the rredlist coupling means it now inherits that package's breaking changes too.
◆ Prediction
Expect the next release to track another upstream source change rather than add new databases; the deprecated-parameter aliases from the 0.9.97 rename are also overdue for removal.
Alternatives to osmdata and taxize
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 taxize.
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 osmdata alternatives → · See all taxize alternatives →
Recent activity from osmdata and taxize
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agoosmdataosmdata 0.4.0
- 5mo agotaxizetaxize 0.10.1 lowers gna_verifier batch size
- 11mo agoosmdataosmdata 0.3.0
- 1y agotaxizetaxize 0.10.0 migrates to GNA and the new rredlist API
- 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
- 5y agotaxizetaxize 0.9.99 retires tnrs(), paginates WORMS queries
- 5y agotaxizetaxize 0.9.98 adds NCBI and zoological rank names
- 6y agotaxizetaxize 0.9.97 standardises parameter names package-wide
- 6y agotaxizetaxize 0.9.96 updates NatureServe for its new API
Frequently asked questions
What is the difference between osmdata and taxize?
They serve adjacent needs but don't currently overlap on shipped themes. osmdata and taxize 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 taxize?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. osmdata and taxize 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 taxize?
Top taxize alternatives in Analytics are ranked by recent ship velocity. Browse the "taxize alternatives" section above for the current picks, or visit /alternatives/taxize for the full list with editorial commentary on each.