tibblify
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
A side-by-side editorial comparison of rasterpic and resmush — release velocity, themes, recent moves, and the top alternatives to consider.
rasterpic became an S3 generic and picked up stars support; the rest is upkeep
rasterpic georeferences ordinary images onto spatial objects, producing terra SpatRasters that can be plotted as basemaps or overlays. The package is small and its job is narrow. The meaningful recent change is 0.5.0, which turned rasterpic_img() into an S3 generic with methods per input class and added support for stars objects alongside sf and terra.
resmush declared itself finished and has shipped nothing but maintenance since.
resmush compresses images through the reSmush.it API from R. Version 1.0.0 was an explicit maturity statement rather than a feature release: the major version was bumped to signal a stable development state, the minimum R version moved to 4.1.0, and documentation moved to Quarto. The two releases since are console message polish, an internals refactor, and mock-based tests.
rasterpic georeferences ordinary images onto spatial objects, producing terra SpatRasters that can be plotted as basemaps or overlays. The package is small and its job is narrow. The meaningful recent change is 0.5.0, which turned rasterpic_img() into an S3 generic with methods per input class and added support for stars objects alongside sf and terra.
The direction is broader input-class coverage inside the same single-function design, and tighter integration with the plotting ecosystem downstream. 0.3.0 renamed output layers to r/g/b/alpha specifically to stay compatible with tmap 4.0; 0.5.1 restored the RGB specification on masked and inverted output after it regressed, and moved errors and warnings to cli formatting. Releases are frequent but small.
With the generic in place, adding further input classes is now cheap, so that is the likely direction. The 0.5.1 regression on mask/inverse output suggests the RGB-specification path is the fragile part worth watching.
resmush compresses images through the reSmush.it API from R. Version 1.0.0 was an explicit maturity statement rather than a feature release: the major version was bumped to signal a stable development state, the minimum R version moved to 4.1.0, and documentation moved to Quarto. The two releases since are console message polish, an internals refactor, and mock-based tests.
This is a package in maintenance by design. The functional surface has not changed since 0.2.2 added a dry-run check and a referer header to the API calls, and the notable earlier change was subtractive, dropping webp when the upstream API stopped accepting it. Recent activity is dominated by dependency bumps and testing work, with mocks replacing live API calls in the test suite.
Expect the same maintenance cadence, with the most likely source of a real change being another format or endpoint shift at the reSmush.it API rather than anything originating in the package.
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 rasterpic or resmush.
tibblify learned to derive its own specs from OpenAPI, removing the step users disliked most
spsurvey has spent four years consolidating after its 5.0.0 rewrite rather than adding to it
StreamCatTools is quietly moving off web services and onto cloud-native GeoParquet
reproducible added a windowed read path so remote GeoTiffs never fully download
qcTAF is building an automated checklist for reproducible fisheries assessments, one criterion at a time
After three dormant years, rpymat returned to fix the OpenMP crash that breaks R and conda together
See all rasterpic alternatives → · See all resmush alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rasterpic and resmush 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rasterpic and resmush 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.
Top rasterpic alternatives in Analytics are ranked by recent ship velocity. Browse the "rasterpic alternatives" section above for the current picks, or visit /alternatives/rasterpic for the full list with editorial commentary on each.
Top resmush alternatives in Analytics are ranked by recent ship velocity. Browse the "resmush alternatives" section above for the current picks, or visit /alternatives/resmush for the full list with editorial commentary on each.