← Back to home
Comparison · Analytics

healthyR.data vs nswgeo

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

healthyR.data vs nswgeo: at a glance

FeaturehealthyR.datanswgeo
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, healthcare-data, cms, api-clientgeospatial, australia, public-health, reference-data
Last editorial update2h ago6h ago
WebsiteVisit →Visit →

What is healthyR.data?

From a bundled hospital dataset to a live CMS API client.

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

Read the full healthyR.data trajectory →

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.

Read the full nswgeo trajectory →

healthyR.data vs nswgeo: editorial side-by-side

H
healthyR.data
ANALYTICS
0.0

From a bundled hospital dataset to a live CMS API client.

◆ Current state

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

◆ Where it's heading

The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.

◆ Prediction

With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.

N
nswgeo
ANALYTICS
0.0

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 healthyR.data 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 healthyR.data or nswgeo.

See all healthyR.data alternatives → · See all nswgeo alternatives →

Recent activity from healthyR.data and nswgeo

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

  1. 4mo agonswgeoSuburb, postcode, PHN and LHD boundaries all refreshed
  2. 6mo agonswgeonswgeo 0.5.1
  3. 1y agohealthyR.datahttr2 compatibility fix
  4. 1y agonswgeoUpdated to the 2024 ASGS release
  5. 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
  6. 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data
  7. 2y agonswgeoTerritories, PHN maps and the outline() helper added
  8. 3y agohealthyR.dataTwenty CMS measure accessors added
  9. 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
  10. 5y agohealthyR.dataxz compression added to meet CRAN size policy

Frequently asked questions

What is the difference between healthyR.data and nswgeo?

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

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

Top healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data 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.