← Back to home
Comparison · Infra & APIs

sits vs usmap

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

sits vs usmap: at a glance

Featuresitsusmap
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesearth-observation, remote-sensing, machine-learning, r-packagecartography, sf, data-packaging, fips
Last editorial update1h ago49m ago
WebsiteVisit →Visit →

What is sits?

An R package for satellite time series just grew a Python API.

sits classifies satellite image time series — building data cubes from cloud archives, training deep learning models on them, and producing land-cover maps. The releases here are dense feature lists in a steady 1.5.x line, and two themes recur in every one: more source collections wired in, and more of the classification pipeline made parallel or chunked. Version 1.5.3 added pysits, a Python API onto the same engine.

Read the full sits trajectory →

What is usmap?

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

Read the full usmap trajectory →

sits vs usmap: editorial side-by-side

S
sits
INFRA · APIS
0.0

An R package for satellite time series just grew a Python API.

◆ Current state

sits classifies satellite image time series — building data cubes from cloud archives, training deep learning models on them, and producing land-cover maps. The releases here are dense feature lists in a steady 1.5.x line, and two themes recur in every one: more source collections wired in, and more of the classification pipeline made parallel or chunked. Version 1.5.3 added pysits, a Python API onto the same engine.

◆ Where it's heading

The package is positioning itself as the interface layer to Earth observation archives rather than as an algorithm library. Each release absorbs another provider — Planetary Computer, Digital Earth Africa and Australia, CDSE, TERRASCOPE, Open Geo Hub, PLANET — so the differentiator is coverage and the uniform cube abstraction over it. The Python API extends the same logic to the language most of that community actually works in. Alongside, the work is increasingly about scale: chunk parallelisation, multicores sampling, GPU classification, WebGL rendering.

◆ Prediction

With collections still being added release over release, expect more providers and continued performance work on the classification and regularisation paths. The open question the entries do not answer is how far pysits tracks the R API, since it appears once and is not mentioned again in later releases.

U
usmap
INFRA · APIS
0.0

Ten years in, US mapping splits its data out and finally adds Puerto Rico.

◆ Current state

usmap plots US state and county maps in an Alaska- and Hawaii-inset projection and joins user data to them by FIPS code. Over the last two years it has been rebuilt underneath: the map data moved out to a companion usmapdata package, the geometry became sf, and a data_year parameter lets a plot match the vintage of the data being plotted. Version 1.0.0 marks ten years of the project and adds Puerto Rico across every function.

◆ Where it's heading

The package has separated what it draws from how it draws, and that separation is what makes the recent releases possible: annual map vintages ship in usmapdata without touching usmap, and Puerto Rico could be backfilled into every existing year at once. The remaining work is coverage and defaults rather than architecture, and the Puerto Rico exclusion default is already governed by an environment variable rather than a code change.

◆ Prediction

Expect the annual map vintage to keep arriving through usmapdata, with usmap itself changing only where a new territory or a projection default needs handling.

Alternatives to sits and usmap

Other Infra & APIs 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 sits or usmap.

See all sits alternatives → · See all usmap alternatives →

Recent activity from sits and usmap

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

  1. 7mo agositsSNIC segmentation, imputation helpers and QGIS palette export
  2. 8mo agositsOne-line hotfix for a CRAN compiler requirement
  3. 11mo agositsHotfix: TAE embeddings, MPC token handling, texture divide-by-zero
  4. 11mo agositsA Python API arrives, alongside SAR texture measures
  5. 11mo agousmapPuerto Rico added across every usmap function and map year
  6. 1y agousmapdata_year parameter threaded through the plotting functions
  7. 1y agositsExclusion masks, multiple tiling systems and faster segment classification
  8. 1y agositsFour more archives wired in, including Digital Earth Africa
  9. 2y agousmapPopulation and poverty data refreshed; ggplot2 3.5 legend fix
  10. 2y agousmapMap data becomes sf; usmap_transform() returns geometry
  11. 2y agousmapDocumentation links updated
  12. 2y agousmapMap data extracted to a companion usmapdata package

Frequently asked questions

What is the difference between sits and usmap?

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

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. sits and usmap 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to sits?

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

What are the best alternatives to usmap?

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