← Back to home
Comparison · Analytics

osmextract vs pkglite

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

osmextract vs pkglite: at a glance

Featureosmextractpkglite
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, geospatial, r-language, gdalr-packages, pharma-submissions, packaging, file-handling
Last editorial update1h ago1h 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 pkglite?

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

Read the full pkglite trajectory →

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

P
pkglite
ANALYTICS
0.0

pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.

◆ Current state

pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.

◆ Where it's heading

The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.

◆ Prediction

Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.

Alternatives to osmextract and pkglite

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

See all osmextract alternatives → · See all pkglite alternatives →

Recent activity from osmextract and pkglite

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

  1. 4mo agoosmextractDownloads move to a persistent cache outside tempdir
  2. 5mo agopkgliteMaintainer email and CI workflow updates
  3. 1y agoosmextractoe_match gains a version argument for historical extracts
  4. 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
  5. 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
  6. 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
  7. 2y agoosmextract51 new openstreetmap.fr regions and a GDAL 3.9 fix
  8. 2y agopkgliteTest helpers moved to helper.R
  9. 3y agoosmextractNon-Geofabrik downloads were saved under the wrong filename
  10. 3y agopkgliteMore file types recognised; cli dependency dropped
  11. 3y agoosmextractHelp files regenerated for valid HTML5
  12. 5y agopkgliteFile collections gain merge, prune, and a tests template

Frequently asked questions

What is the difference between osmextract and pkglite?

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

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

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