← Back to home
Comparison · Analytics

nswgeo vs rnpn

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

nswgeo vs rnpn: at a glance

Featurenswgeornpn
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgeospatial, australia, public-health, reference-dataphenology, api-client, ecological-data, data-cleaning
Last editorial update2h ago45m ago
WebsiteVisit →Visit →

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 →

What is rnpn?

The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.

rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.

Read the full rnpn trajectory →

nswgeo vs rnpn: editorial side-by-side

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.

R
rnpn
ANALYTICS
0.0

The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.

◆ Current state

rnpn is the R client for the USA National Phenology Network, retrieving observation records, phenometrics and gridded model layers. Version 1.3.0 in March 2025 replaced nearly all of its infrastructure at once — sp and raster dropped, terra made optional, XML swapped for xml2, plyr for dplyr, httr and curl for httr2 — and changed what functions return, with tibbles in place of data.tables and empty tibbles in place of NULL on error. The two releases since have completed the missing-value handling and restored performance lost in the transition.

◆ Where it's heading

The package is being brought onto the current R stack and made honest about missing data, and those are the same project. Converting the -9999 sentinel to NA started in 1.3.0 for download functions and was extended to all columns in 1.4.1; the string "emptyvalue" got the same treatment. Beyond the migration, the feature additions are modest and specific to the domain, such as custom start and end dates for defining a phenometrics season.

◆ Prediction

With the dependency migration finished and sentinel handling now applied across all columns, the next releases most likely return to domain features and to fixes surfaced by the server side, which has already prompted work through migrations and backend moves. The removed progress indicator is an acknowledged regression that may come back.

Alternatives to nswgeo and rnpn

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 nswgeo or rnpn.

See all nswgeo alternatives → · See all rnpn alternatives →

Recent activity from nswgeo and rnpn

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. 11mo agornpnSentinel -9999 now converted to NA across all columns
  4. 1y agornpnCustom season windows for phenometrics, and a speed regression fixed
  5. 1y agornpnDependency stack and return types replaced wholesale
  6. 1y agonswgeoUpdated to the 2024 ASGS release
  7. 1y agornpnBackfilled notes for seven earlier maintenance releases
  8. 2y agonswgeoTerritories, PHN maps and the outline() helper added

Frequently asked questions

What is the difference between nswgeo and rnpn?

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

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

What are the best alternatives to rnpn?

Top rnpn alternatives in Analytics are ranked by recent ship velocity. Browse the "rnpn alternatives" section above for the current picks, or visit /alternatives/rnpn for the full list with editorial commentary on each.