osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
FedData vs osmextract
A side-by-side editorial comparison of FedData and osmextract — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:geospatial
FedData vs osmextract: at a glance
What is FedData?
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
FedData downloads and standardises US federal geospatial datasets — NLCD, NHD, NED, SSURGO, Daymet, GHCN, PAD-US, NASS — into consistent R objects. Two breaking majors define the current package: 3.0.0 moved returns to sf and raster and pulled data from cloud-optimised GeoTIFFs, and 4.0.0 finished the job by dropping sp and raster entirely for terra and sf. Recent releases are dataset refreshes, most recently PAD-US 4.0.
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.
FedData vs osmextract: editorial side-by-side
FedData
0.0ANALYTICS
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
◆ Current state
FedData downloads and standardises US federal geospatial datasets — NLCD, NHD, NED, SSURGO, Daymet, GHCN, PAD-US, NASS — into consistent R objects. Two breaking majors define the current package: 3.0.0 moved returns to sf and raster and pulled data from cloud-optimised GeoTIFFs, and 4.0.0 finished the job by dropping sp and raster entirely for terra and sf. Recent releases are dataset refreshes, most recently PAD-US 4.0.
◆ Where it's heading
The package tracks two moving targets at once: the R spatial stack, which it has now fully migrated onto terra and sf, and the federal agencies whose URLs, file naming and hosting keep shifting. With the dependency migration finished, releases have shrunk to single-dataset updates such as annual NLCD and PAD-US 4.0, which suggests the structural work is done and the ongoing cost is data-source maintenance.
◆ Prediction
Expect continued small releases pinned to new vintages of the underlying federal datasets, plus fixes when an agency moves or reformats a source; no further dependency-level upheaval is visible in these entries.
osmextract
0.0ANALYTICS
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 FedData 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 FedData or osmextract.
ymlthis
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all FedData alternatives → · See all osmextract alternatives →
Recent activity from FedData and osmextract
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agoosmextractDownloads move to a persistent cache outside tempdir ⚡
- 1y agoFedDataget_padus() updated to PAD-US 4.0
- 1y agoosmextractoe_match gains a version argument for historical extracts
- 1y agoosmextractRouting semantics sharpen for driving and restricted-access links
- 1y agoFedDataAnnual NLCD access added; get_nass() retired
- 2y agoosmextract51 new openstreetmap.fr regions and a GDAL 3.9 fix
- 2y agoFedDatasp and raster dropped; everything returns terra or sf ⚡
- 3y agoosmextractNon-Geofabrik downloads were saved under the wrong filename
- 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
- 3y agoFedDataAll raster writing moves to terra
- 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs ⚡
- 3y agoosmextractHelp files regenerated for valid HTML5
Frequently asked questions
What is the difference between FedData and osmextract?
Both compete on the same themes — geospatial — within Analytics. FedData 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 FedData better than osmextract?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. FedData 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 FedData?
Top FedData alternatives in Analytics are ranked by recent ship velocity. Browse the "FedData alternatives" section above for the current picks, or visit /alternatives/feddata 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.