← Back to home
Comparison · Analytics

osmextract vs vcr

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

osmextract vs vcr: at a glance

Featureosmextractvcr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, geospatial, r-language, gdaltesting, http-mocking, breaking-change, api-cleanup
Last editorial update45m ago2h 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 vcr?

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

Read the full vcr trajectory →

osmextract vs vcr: 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.

V
vcr
ANALYTICS
0.0

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

◆ Current state

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

◆ Where it's heading

The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.

◆ Prediction

Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.

Alternatives to osmextract and vcr

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

See all osmextract alternatives → · See all vcr alternatives →

Recent activity from osmextract and vcr

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

  1. 4mo agoosmextractDownloads move to a persistent cache outside tempdir
  2. 8mo agovcr2.0 removes the logging API and the exported R6 classes
  3. 1y agoosmextractoe_match gains a version argument for historical extracts
  4. 1y agovcrMaintainer email address updated
  5. 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
  6. 2y agovcrAdds httr2 support alongside httr and crul
  7. 2y agoosmextract51 new openstreetmap.fr regions and a GDAL 3.9 fix
  8. 3y agoosmextractNon-Geofabrik downloads were saved under the wrong filename
  9. 3y agovcrDrops compilation; test setup moves back to helper files
  10. 3y agovcrFixes request matching with escaped characters
  11. 3y agoosmextractHelp files regenerated for valid HTML5
  12. 5y agovcrvcr_test_path() finds the package root correctly

Frequently asked questions

What is the difference between osmextract and vcr?

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

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

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