← Back to home
Comparison · Analytics

bundle vs osmextract

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

bundle vs osmextract: at a glance

Featurebundleosmextract
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesserialization, tidymodels, model-deployment, compatibilityopenstreetmap, geospatial, r-language, gdal
Last editorial update49m ago1h ago
WebsiteVisit →Visit →

What is bundle?

Four releases in three years, each one teaching the serializer about a model type it couldn't carry

bundle solves a narrow, real problem: many R model objects hold pointers to external state — compiled boosters, Java handles, torch tensors — that do not survive being saved and reloaded in another session. It wraps them so they do. The package has shipped four releases since 2022, and the shape of each is the same: extend coverage to another model class, or repair coverage that an upstream release broke.

Read the full bundle trajectory →

What is osmextract?

osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.

osmextract downloads OpenStreetMap extracts from Geofabrik, BBBike and openstreetmap.fr and translates them into sf objects via GDAL. The 0.6.0 release moved its download cache from `tempdir()` to a persistent `tools::R_user_dir()` location and raised the R floor to 4.1.0 to get it. It also made spatial `place` inputs self-clipping: pass an sf or bbox object and the boundary is now set to match, so only the relevant slice of a country-sized extract is processed.

Read the full osmextract trajectory →

bundle vs osmextract: editorial side-by-side

B
bundle
ANALYTICS
0.0

Four releases in three years, each one teaching the serializer about a model type it couldn't carry

◆ Current state

bundle solves a narrow, real problem: many R model objects hold pointers to external state — compiled boosters, Java handles, torch tensors — that do not survive being saved and reloaded in another session. It wraps them so they do. The package has shipped four releases since 2022, and the shape of each is the same: extend coverage to another model class, or repair coverage that an upstream release broke.

◆ Where it's heading

Coverage is the product, so the release cadence is set by the ecosystem rather than by a roadmap. dbarts arrived in 0.1.2, along with extra work to preserve xgboost's nfeatures and feature_names through a round trip; 0.1.3 exists because xgboost changed its model format again. The 0.1.1 fix — recipes steps nested inside workflows — points at the same underlying issue one level up, where the object needing bundling is buried inside a tidymodels pipeline rather than passed directly.

◆ Prediction

Expect the next release to follow the same trigger: either a new parsnip engine that carries external pointers, or another upstream format change in one of the engines already covered. xgboost has now forced two of the four releases.

O
osmextract
ANALYTICS
0.0

osmextract stopped throwing your OpenStreetMap downloads away at the end of every session.

◆ Current state

osmextract downloads OpenStreetMap extracts from Geofabrik, BBBike and openstreetmap.fr and translates them into sf objects via GDAL. The 0.6.0 release moved its download cache from `tempdir()` to a persistent `tools::R_user_dir()` location and raised the R floor to 4.1.0 to get it. It also made spatial `place` inputs self-clipping: pass an sf or bbox object and the boundary is now set to match, so only the relevant slice of a country-sized extract is processed.

◆ Where it's heading

Two threads run through every release. One is chasing GDAL — SQL syntax adjusted for 3.10, ogr2ogr options fixed for 3.9, and an `osmconf.ini` that 0.6.0 finally keeps automatically in sync with whatever sf or GDAL provides rather than shipping a snapshot. The other is the road-network extraction added experimentally in 0.3.1, which has been quietly accumulating real routing semantics since: `access = no` links retained when the mode-specific tag permits them, a `oneway` column by default for driving, and `motor_vehicle` always included.

◆ Prediction

Given that `oe_get_network()` has gained transport-mode detail in three separate releases while remaining flagged as experimental, the next substantive work is most likely there — either more modes or a formal exit from experimental status.

Alternatives to bundle and osmextract

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 bundle or osmextract.

See all bundle alternatives → · See all osmextract alternatives →

Recent activity from bundle and osmextract

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

  1. 4mo agoosmextractDownloads move to a persistent cache outside tempdir
  2. 8mo agobundlexgboost bundling updated for newer model versions
  3. 1y agoosmextractoe_match gains a version argument for historical extracts
  4. 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
  5. 1y agobundledbarts BART models become bundleable
  6. 2y agoosmextract51 new openstreetmap.fr regions and a GDAL 3.9 fix
  7. 2y agobundleRecipes steps inside workflows now bundle correctly
  8. 3y agoosmextractNon-Geofabrik downloads were saved under the wrong filename
  9. 3y agobundleFirst CRAN release
  10. 3y agoosmextractHelp files regenerated for valid HTML5

Frequently asked questions

What is the difference between bundle and osmextract?

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

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

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

What are the best alternatives to osmextract?

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