← Back to home
Comparison · Analytics

FedData vs sftime

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

Shared themes:r-package

FedData vs sftime: at a glance

FeatureFedDatasftime
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesropensci, geospatial, r-package, open-dataspatiotemporal, r-spatial, interoperability, tidyverse-integration
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

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.

Read the full FedData 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 →

FedData vs sftime: editorial side-by-side

F
FedData
ANALYTICS
0.0

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.

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

See all FedData alternatives → · See all sftime alternatives →

Recent activity from FedData and sftime

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

  1. 3mo agosftimeExamples switched to the native R pipe
  2. 11mo agosftimeFixes the cubble namespace version check
  3. 1y agoFedDataget_padus() updated to PAD-US 4.0
  4. 1y agoFedDataAnnual NLCD access added; get_nass() retired
  5. 1y agosftimeConverts from spatstat, sftrack and cubble objects
  6. 2y agoFedDatasp and raster dropped; everything returns terra or sf
  7. 3y agoFedDataGHCN moves to https; NHD handles empty and odd geometries
  8. 3y agoFedDataAll raster writing moves to terra
  9. 3y agoFedDataVersion 3 rebuilds on sf and cloud-optimised GeoTIFFs

Frequently asked questions

What is the difference between FedData and sftime?

Both compete on the same themes — r-package — within Analytics. FedData 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 FedData better than sftime?

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