TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
Comparison · Analytics
intsurv vs nswgeo
A side-by-side editorial comparison of intsurv and nswgeo — release velocity, themes, recent moves, and the top alternatives to consider.
intsurv vs nswgeo: at a glance
What is intsurv?
A Cox cure-rate model package woke up after four years to simplify its own interface.
intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.
What is nswgeo?
NSW boundary data for R, refreshed as the official sources move
nswgeo packages New South Wales geographic boundaries for R — suburbs, postcodes, local government areas, Primary Health Networks and Local Health Districts — as ready-to-plot sf datasets. The 0.6.0 release refreshes nearly all of them against new upstream sources, moving postcodes to 2021 ABS boundaries and taking LHD boundaries from a new official feed. It is maintained by cidm-ph alongside the mapping packages that consume it, including ggmapinset.
intsurv vs nswgeo: editorial side-by-side
intsurv
0.0ANALYTICS
A Cox cure-rate model package woke up after four years to simplify its own interface.
◆ Current state
intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.
◆ Where it's heading
The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.
◆ Prediction
The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.
nswgeo
0.0ANALYTICS
NSW boundary data for R, refreshed as the official sources move
◆ Current state
nswgeo packages New South Wales geographic boundaries for R — suburbs, postcodes, local government areas, Primary Health Networks and Local Health Districts — as ready-to-plot sf datasets. The 0.6.0 release refreshes nearly all of them against new upstream sources, moving postcodes to 2021 ABS boundaries and taking LHD boundaries from a new official feed. It is maintained by cidm-ph alongside the mapping packages that consume it, including ggmapinset.
◆ Where it's heading
Every release is dictated by an upstream release calendar rather than a roadmap: the 2023 ASGS, then 2024, then the 2021 ABS postcode boundaries and the new LHD source. That makes field-name churn the package's defining hazard — LGA_NAME_2021 to LGA_NAME_2023 to LGA_NAME_2024, and now lhd_name carrying a Local Health District suffix. The maintainer's habit of registering compatibility aliases through cartographer shows an awareness that these renames break downstream code silently.
◆ Prediction
Expect the next release to track the following ASGS edition with another round of field renames, and any new content to stay in the health-geography area the package's users work in.
Alternatives to intsurv and nswgeo
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 intsurv or nswgeo.
cfbfastr
College football's open data client hit v2 — and now reports how many API calls you have left.
rnpn
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
rempsyc
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
sdsfun
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all intsurv alternatives → · See all nswgeo alternatives →
Recent activity from intsurv and nswgeo
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agonswgeoSuburb, postcode, PHN and LHD boundaries all refreshed
- 6mo agonswgeonswgeo 0.5.1
- 10mo agointsurvModel configuration moves into dedicated control functions
- 1y agonswgeoUpdated to the 2024 ASGS release
- 2y agonswgeoTerritories, PHN maps and the outline() helper added
- 5y agointsurvCross-validated model selection and offset terms added
- 6y agointsurvC++ headers relocated so other packages can link them
- 7y agointsurvCox cure models for uncertain event status arrive
- 7y agointsurvParameter initialization methods added to the alpha
- 7y agointsurvAlpha cut for paper submission and simulation reproducibility
Frequently asked questions
What is the difference between intsurv and nswgeo?
They serve adjacent needs but don't currently overlap on shipped themes. intsurv and nswgeo 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 intsurv better than nswgeo?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. intsurv and nswgeo 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 intsurv?
Top intsurv alternatives in Analytics are ranked by recent ship velocity. Browse the "intsurv alternatives" section above for the current picks, or visit /alternatives/intsurv for the full list with editorial commentary on each.
What are the best alternatives to nswgeo?
Top nswgeo alternatives in Analytics are ranked by recent ship velocity. Browse the "nswgeo alternatives" section above for the current picks, or visit /alternatives/nswgeo for the full list with editorial commentary on each.