silx
silx settles into maintenance a release after its PySide6 migration
Comparison · Analytics
nswgeo vs TimescaleDB
A side-by-side editorial comparison of nswgeo and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
nswgeo vs TimescaleDB: at a glance
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.
What is TimescaleDB?
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
nswgeo vs TimescaleDB: editorial side-by-side
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.
TimescaleDB
5.0ANALYTICS
TimescaleDB is paying down correctness debt in its columnstore query paths.
◆ Current state
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
◆ Where it's heading
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
◆ Prediction
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
Alternatives to nswgeo and TimescaleDB
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 TimescaleDB.
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI
OpenCTI spends a release unblocking queues and hardening upserts
See all nswgeo alternatives → · See all TimescaleDB alternatives →
Recent activity from nswgeo and TimescaleDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoTimescaleDB2.29.2: SkipScan and sparse-index correctness fixes
- 15d agoTimescaleDB2.29.1: security fixes plus compression bugfixes
- 19d agoTimescaleDB2.29.0: chunk exclusion speeds up UPDATE and DELETE
- 1mo agoTimescaleDB2.28.3: columnar pipeline correctness fixes
- 1mo agoTimescaleDB2.28.2: upgrade-path fixes for 2.28.1
- 1mo agoTimescaleDB2.28.1: compressed-table crash and constraint fixes
- 4mo agonswgeoSuburb, postcode, PHN and LHD boundaries all refreshed
- 7mo agonswgeonswgeo 0.5.1
- 1y agonswgeoUpdated to the 2024 ASGS release
- 2y agonswgeoTerritories, PHN maps and the outline() helper added
Frequently asked questions
What is the difference between nswgeo and TimescaleDB?
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is nswgeo better than TimescaleDB?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TimescaleDB is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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 TimescaleDB?
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.