← Back to home
Comparison · Analytics

osmextract vs sftime

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

osmextract vs sftime: at a glance

Featureosmextractsftime
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesopenstreetmap, geospatial, r-language, gdalspatiotemporal, r-spatial, interoperability, tidyverse-integration
Last editorial update43m 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 sftime?

The spatiotemporal companion to sf, moving at the pace of the packages around it.

sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.

Read the full sftime trajectory →

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

S
sftime
ANALYTICS
0.0

The spatiotemporal companion to sf, moving at the pace of the packages around it.

◆ Current state

sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.

◆ Where it's heading

The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.

◆ Prediction

Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.

Alternatives to osmextract and sftime

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

See all osmextract alternatives → · See all sftime alternatives →

Recent activity from osmextract and sftime

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

  1. 3mo agosftimeExamples switched to the native R pipe
  2. 4mo agoosmextractDownloads move to a persistent cache outside tempdir
  3. 11mo agosftimeFixes the cubble namespace version check
  4. 1y agoosmextractoe_match gains a version argument for historical extracts
  5. 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
  6. 1y agosftimeConverts from spatstat, sftrack and cubble objects
  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 agoosmextractHelp files regenerated for valid HTML5

Frequently asked questions

What is the difference between osmextract and sftime?

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

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

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