← Back to home
Comparison · Analytics

nswgeo vs sdsfun

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

nswgeo vs sdsfun: at a glance

Featurenswgeosdsfun
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesgeospatial, australia, public-health, reference-dataspatial-statistics, geodetector, spatial-clustering, rcpp
Last editorial update2h ago47m 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 sdsfun?

A spatial-statistics utility package exists to be depended on, and is built accordingly.

sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.

Read the full sdsfun trajectory →

nswgeo vs sdsfun: 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.

S
sdsfun
ANALYTICS
0.0

A spatial-statistics utility package exists to be depended on, and is built accordingly.

◆ Current state

sdsfun collects spatial data science utilities — neighbour lists, spatial constrained clustering, discretization, dummy variable generation, geographical detector statistics and projection helpers — with the computationally heavy parts implemented in Rcpp. It was assembled quickly across late 2024, adding a function set roughly every three weeks, and has slowed since to a couple of releases a year. The most recent work is corrective: no longer initializing the RNG state at load, fixing matrix inputs misread as vectors, and clearing an Armadillo deprecation.

◆ Where it's heading

This is infrastructure for a family of packages rather than an end-user tool, and the changelog says so directly — functions were added to support gdverse and sesp, and moran_test was migrated in from geocomplexity. That migration pattern is the defining move: capability consolidates here so the downstream packages can share it instead of each carrying its own copy. Growth has slowed as that consolidation completed, leaving correctness and dependency upkeep.

◆ Prediction

Given the package moves when its dependents need something, the next release most likely brings in another shared function or responds to a downstream requirement rather than following its own plan. Armadillo and CRAN check changes remain the reliable source of maintenance work.

Alternatives to nswgeo and sdsfun

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 sdsfun.

See all nswgeo alternatives → · See all sdsfun alternatives →

Recent activity from nswgeo and sdsfun

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. 10mo agosdsfunPackage load stops touching the RNG state
  4. 1y agosdsfunUnified partial correlation testing and head/tails discretization
  5. 1y agosdsfunMissing-value handling added to linear trend removal
  6. 1y agonswgeoUpdated to the 2024 ASGS release
  7. 1y agosdsfunCovariate-based detrending and long-to-matrix spatial reshaping
  8. 1y agosdsfunSpatially constrained hierarchical clustering and SPADE estimation
  9. 1y agosdsfunFast geodetector q-value estimator added
  10. 2y agonswgeoTerritories, PHN maps and the outline() helper added

Frequently asked questions

What is the difference between nswgeo and sdsfun?

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

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

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