← Back to home
Comparison · Analytics

osmextract vs xplainfi

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

osmextract vs xplainfi: at a glance

Featureosmextractxplainfi
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesopenstreetmap, geospatial, r-language, gdalmlr3, feature-importance, interpretability, statistical-inference
Last editorial update45m ago5h ago
WebsiteVisit →Visit →

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 →

What is xplainfi?

xplainfi treats feature importance as an estimate with error bars, not a number.

xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.

Read the full xplainfi trajectory →

osmextract vs xplainfi: editorial side-by-side

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.

X
xplainfi
ANALYTICS
2.5

xplainfi treats feature importance as an estimate with error bars, not a number.

◆ Current state

xplainfi implements feature importance methods for mlr3 — perturbation-based PFI, CFI and RFI, refit-based LOCO and WVIM, and SAGE. Its defining choice is that importance scores come with inference attached: several confidence-interval methods, including the Nadeau-Bengio correction and a distribution-free option added in 1.1.0. It declared itself released at 1.0.0 in January 2026.

◆ Where it's heading

Two lines of work run in parallel. The statistical side keeps adding inference options — variance corrections, conditional predictive impact, and the Lei et al. observation-wise loss-difference test — while the computational side attacks the cost of refit-based methods, most recently with a batch_size argument that parallelises refits and a default of one refit per resampling iteration. Support for pre-trained learners in 1.1.0 removes the refit requirement entirely in some workflows.

◆ Prediction

The stated reasoning that budget is better spent on resampling iterations than repeated refits suggests n_repeats may be removed from WVIM and LOCO outright, as the release notes hint.

Alternatives to osmextract and xplainfi

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

See all osmextract alternatives → · See all xplainfi alternatives →

Recent activity from osmextract and xplainfi

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

  1. 21d agoxplainfiRefits parallelise; repeated refits deprioritised in favour of resampling
  2. 4mo agoosmextractDownloads move to a persistent cache outside tempdir
  3. 5mo agoxplainfiPre-trained learners supported; distribution-free inference added
  4. 6mo agoxplainfiVersion bumped to mark the package as released
  5. 9mo agoxplainfiConfidence intervals arrive for feature importance scores
  6. 1y agoosmextractoe_match gains a version argument for historical extracts
  7. 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
  8. 2y agoosmextract51 new openstreetmap.fr regions and a GDAL 3.9 fix
  9. 3y agoosmextractNon-Geofabrik downloads were saved under the wrong filename
  10. 3y agoosmextractHelp files regenerated for valid HTML5

Frequently asked questions

What is the difference between osmextract and xplainfi?

They serve adjacent needs but don't currently overlap on shipped themes. xplainfi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is osmextract better than xplainfi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. xplainfi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

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.

What are the best alternatives to xplainfi?

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