tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
ijtiff vs xportr
A side-by-side editorial comparison of ijtiff and xportr — release velocity, themes, recent moves, and the top alternatives to consider.
ijtiff vs xportr: at a glance
What is ijtiff?
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
What is xportr?
The CDISC transport writer collapsed six pipeline calls into one, then spent two years hardening it
xportr applies CDISC metadata — variable types, lengths, labels, formats, ordering — to R data frames and writes the SAS transport files that go into regulatory submissions. Since v0.4.0 the package has had a single entry point, xportr_process(), that runs the whole chain and writes, and metadata arrives as a plain specification rather than a metacore object. The v0.5.0 release in January 2026 finished the cleanup by deleting every deprecated argument left over from that redesign.
ijtiff vs xportr: editorial side-by-side
ijtiff
0.0ANALYTICS
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
◆ Current state
ijtiff reads and writes TIFF files the way ImageJ writes them, which ordinary R TIFF readers get wrong — multi-channel, multi-frame, and unusual bit depths. The 3.1.x line is dominated by memory correctness in the C tag-handling layer, alongside dropping the large imager dependency from the display path. Cadence is sporadic, with multi-year gaps.
◆ Where it's heading
Two threads run through the window. The C layer is being hardened — memory leaks in tag handling, buffer cleanup, PROTECT errors, validation of malformed files — which is the kind of work that surfaces when a package gets run against real-world files at volume. Separately, the R layer is shedding dependencies, with base graphics replacing imager for display. Both make the package cheaper and safer to depend on rather than more capable.
◆ Prediction
Expect continued C-level correctness work rather than format features, since three of the last three substantive releases were memory or compiler fixes.
xportr
0.0ANALYTICS
The CDISC transport writer collapsed six pipeline calls into one, then spent two years hardening it
◆ Current state
xportr applies CDISC metadata — variable types, lengths, labels, formats, ordering — to R data frames and writes the SAS transport files that go into regulatory submissions. Since v0.4.0 the package has had a single entry point, xportr_process(), that runs the whole chain and writes, and metadata arrives as a plain specification rather than a metacore object. The v0.5.0 release in January 2026 finished the cleanup by deleting every deprecated argument left over from that redesign.
◆ Where it's heading
The work has moved from building the pipeline to defending it against the ways submission data actually arrives: grouped data frames now raise a warning, date and time variables get class checks, illegal characters are resolved rather than erroring, and xportr_write() warns before a file crosses 5GB instead of producing an unusable artifact. Contributor volume is high and spread across sponsors — Atorus, Roche, GSK and others show up in the PR lists — which is what keeps a validated-context package moving without a single owner.
◆ Prediction
With deprecations cleared in 0.5.0, the next cycle likely targets more input-shape validation of the kind 0.5.0 started — the grouped-data and datetime-class checks read as the first two of a series. Nothing in these entries points to a new output format.
Alternatives to ijtiff and xportr
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 ijtiff or xportr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all ijtiff alternatives → · See all xportr alternatives →
Recent activity from ijtiff and xportr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agoxportrDeprecated arguments deleted; 5GB and datetime guards added
- 1y agoxportrTest fixes for the metacore 0.2.0 update
- 1y agoijtiffPROTECT-error and documentation fixes across 3.1.1-3.1.3
- 1y agoijtiffDrops the imager dependency; fixes tag-handling memory leaks
- 1y agoxportrhms accepted as a numeric type; domain logging filled in
- 1y agoxportrFile-size limit moves into xportr_write, deprecating xportr_split
- 2y agoxportrxportr_process() runs the whole pipeline in one call ⚡
- 2y agoxportrUnused dependencies removed
- 3y agoijtiffMoves to rlang::abort() and away from magrittr
- 3y agoijtiffFixes NEWS.md headings
- 5y agoijtiffCompatibility with libtiff using C99 stdint.h
- 5y agoijtiffQuiets pkg-config warnings; drops LazyData
Frequently asked questions
What is the difference between ijtiff and xportr?
They serve adjacent needs but don't currently overlap on shipped themes. ijtiff and xportr 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 ijtiff better than xportr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ijtiff and xportr 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 ijtiff?
Top ijtiff alternatives in Analytics are ranked by recent ship velocity. Browse the "ijtiff alternatives" section above for the current picks, or visit /alternatives/ijtiff for the full list with editorial commentary on each.
What are the best alternatives to xportr?
Top xportr alternatives in Analytics are ranked by recent ship velocity. Browse the "xportr alternatives" section above for the current picks, or visit /alternatives/xportr for the full list with editorial commentary on each.