← Back to home
Comparison · Infra & APIs

packageRank vs sits

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

packageRank vs sits: at a glance

FeaturepackageRanksits
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themescran, download-analytics, log-filtering, visualizationearth-observation, remote-sensing, machine-learning, r-package
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is packageRank?

CRAN download analytics maintained one micro-change at a time, hundreds per year

packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.

Read the full packageRank trajectory →

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 →

packageRank vs sits: editorial side-by-side

P
packageRank
INFRA · APIS
0.0

CRAN download analytics maintained one micro-change at a time, hundreds per year

◆ Current state

packageRank computes download counts and percentile ranks from CRAN's logs, with a filtering layer that tries to separate real installs from mirrors, sequences and bots. The recent releases are dense lists of small changes — thirty or more per version — spread across plot arguments, filter behaviour, and the cranDistribution object that now absorbs what packageDistribution() used to do separately.

◆ Where it's heading

There is no directional arc here; there is a maintainer keeping a measurement instrument calibrated against a data source that keeps moving. CRAN's logs went missing for a week in 2025 and the package now ships those dates as data and draws them as polygons on every plot. A chatgpt argument has been threaded through the plotting functions since 0.9.6. Function surface churns constantly — arguments renamed, plot helpers archived, others integrated.

◆ Prediction

Given the cadence, the next release will be another few dozen adjustments concentrated wherever CRAN's logs last surprised the maintainer. The consolidation of plotting arguments toward a single axis.package annotation looks unfinished.

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.

Alternatives to packageRank and sits

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 packageRank or sits.

See all packageRank alternatives → · See all sits alternatives →

Recent activity from packageRank and sits

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

  1. 5mo agopackageRankPackage and version axis annotations across every plot
  2. 7mo agositsSNIC segmentation, imputation helpers and QGIS palette export
  3. 8mo agositsOne-line hotfix for a CRAN compiler requirement
  4. 10mo agopackageRankMissing CRAN log dates shipped as data and drawn on plots
  5. 11mo agositsHotfix: TAE embeddings, MPC token handling, texture divide-by-zero
  6. 11mo agositsA Python API arrives, alongside SAR texture measures
  7. 1y agopackageRankWeekend and version overlays for the base graphics path
  8. 1y agopackageRankPackage history prefers CRAN over the pkgsearch fallback
  9. 1y agositsExclusion masks, multiple tiling systems and faster segment classification
  10. 1y agopackageRankDistribution summaries gain totals and a top-N default
  11. 1y agopackageRankcranDistribution() object and a direct query family
  12. 1y agositsFour more archives wired in, including Digital Earth Africa

Frequently asked questions

What is the difference between packageRank and sits?

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

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

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

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.