r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
rtflite vs USAboundaries
A side-by-side editorial comparison of rtflite and USAboundaries — release velocity, themes, recent moves, and the top alternatives to consider.
rtflite vs USAboundaries: at a glance
What is rtflite?
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.
What is USAboundaries?
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
rtflite vs USAboundaries: editorial side-by-side
rtflite
0.0ANALYTICS
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
◆ Current state
rtflite generates the RTF tables clinical study reports are built from, a Python answer to the R tooling that has owned this niche. Over one dense month it grew a full export path: DOCX in 2.2.0, DOCX concatenation in 2.3.0, a configurable LibreOffice converter in 2.4.0, and HTML plus PDF in 2.5.0. The three releases since have been documentation, test infrastructure, and typing work — the feature push has stopped and consolidation has started.
◆ Where it's heading
Every format addition routes through the same LibreOffice converter rather than a per-format implementation, and 2.4.0's breaking change made that converter an injectable object you can configure and reuse. That is the shape of a package expecting to run inside a pipeline that produces hundreds of tables, not one that converts a document at a time. The recent quiet — snapshot tests moved onto `pytest-r-snapshot`, docs migrated, pandas and pyarrow dropped from dev dependencies — reads as work to stay dependency-light while the surface stabilizes.
◆ Prediction
With the export matrix filled in and three consecutive infrastructure-only releases, the next substantive change is most likely on the input side — table construction and pagination — since `page_by` and `subline_by` are the only feature area still generating bug reports in these notes.
USAboundaries
0.0ANALYTICS
Seven years dormant, then two releases dragging every census boundary from 2020 to 2024
◆ Current state
USAboundaries supplies contemporary and historical US boundary data — states, counties, congressional districts, cities, ZIP code tabulation areas — as sf objects, with the bulk data held in a companion USAboundariesData package. After a gap running from 2018 to late 2025, two releases a month apart refreshed the contemporary census vintage from 2020 to 2024: 0.5.0 covered everything except states, and 0.5.1 finished the job.
◆ Where it's heading
For a data package the release cycle is the data vintage, and the 0.3.0 split into a separate data package was designed precisely so those refreshes would not require a code release. That the 2024 update still arrived as two package versions seven years later says the mechanism is being used sparingly. Nothing in the feed shows work on the API itself since us_cities() gained an sf return type and a states argument in 2018.
◆ Prediction
The next release is most likely another vintage refresh when the census data moves again, rather than new geographies or functions. The split of 0.5.0 and 0.5.1 suggests state boundaries are handled on a separate path from the rest and may lag again.
Alternatives to rtflite and USAboundaries
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 rtflite or USAboundaries.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all rtflite alternatives → · See all USAboundaries alternatives →
Recent activity from rtflite and USAboundaries
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agortfliteMulti-section body typing tightened; pandas dropped from dev deps
- 7mo agortfliteAPI reference renders Pydantic field metadata
- 7mo agortfliteDocumentation site migrated to Zensical
- 7mo agortfliteSnapshot tests moved to pytest-r-snapshot
- 7mo agortfliteHTML and PDF export complete the output matrix ⚡
- 7mo agortfliteLibreOffice conversion becomes an injectable converter object
- 9mo agoUSAboundariesState boundaries updated to the 2024 census vintage
- 10mo agoUSAboundariesCensus data refreshed to 2024, states excepted
- 8y agoUSAboundariesus_cities() returns sf and gains a states argument
- 9y agoUSAboundariesData split into a companion package; all boundaries become sf ⚡
- 9y agoUSAboundariesContemporary state, county and district boundaries added
Frequently asked questions
What is the difference between rtflite and USAboundaries?
They serve adjacent needs but don't currently overlap on shipped themes. rtflite and USAboundaries 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 rtflite better than USAboundaries?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rtflite and USAboundaries 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 rtflite?
Top rtflite alternatives in Analytics are ranked by recent ship velocity. Browse the "rtflite alternatives" section above for the current picks, or visit /alternatives/rtflite for the full list with editorial commentary on each.
What are the best alternatives to USAboundaries?
Top USAboundaries alternatives in Analytics are ranked by recent ship velocity. Browse the "USAboundaries alternatives" section above for the current picks, or visit /alternatives/usaboundaries for the full list with editorial commentary on each.