bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
Comparison · Infra & APIs
geocomplexity vs HydroPortailStats
A side-by-side editorial comparison of geocomplexity and HydroPortailStats — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
geocomplexity vs HydroPortailStats: at a glance
| Feature | geocomplexity | HydroPortailStats |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | spatial-statistics, r-package, geographically-weighted-regression, raster | hydrology, flood-frequency, bayesian-statistics, extreme-values |
| Last editorial update | 1h ago | 58m ago |
| Website | Visit → | Visit → |
What is geocomplexity?
A spatial complexity package that shipped its method, then went quiet
geocomplexity computes geographical complexity from spatial dependence and configuration similarity across both vector and raster data, and uses it to build spatial weight matrices and a complexity-aware geographically weighted regression. That capability arrived complete in the 0.1.0 release of September 2024. The three releases since contain no functional change: a citation file, a dependency trim, one function moved out to a sibling package, and a maintainer surname correction.
What is HydroPortailStats?
France's national flood statistics, ported out of Fortran and into R.
HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.
geocomplexity vs HydroPortailStats: editorial side-by-side
geocomplexity
0.0INFRA · APIS
A spatial complexity package that shipped its method, then went quiet
◆ Current state
geocomplexity computes geographical complexity from spatial dependence and configuration similarity across both vector and raster data, and uses it to build spatial weight matrices and a complexity-aware geographically weighted regression. That capability arrived complete in the 0.1.0 release of September 2024. The three releases since contain no functional change: a citation file, a dependency trim, one function moved out to a sibling package, and a maintainer surname correction.
◆ Where it's heading
The package sits inside Wenbo Lyu's spatial statistics family, where shared functionality migrates into the common sdsfun package rather than being duplicated across dependents. moran_test left geocomplexity for sdsfun in 0.2.0, which is the same consolidation pattern visible across the author's other packages. What remains here is the method-specific surface, and it has not changed in eighteen months.
◆ Prediction
The entries give no signal of planned functional work; on this pattern the next release is as likely to be metadata or another function migration to sdsfun as anything user-visible.
HydroPortailStats
0.0INFRA · APIS
France's national flood statistics, ported out of Fortran and into R.
◆ Current state
HydroPortailStats exposes the statistical machinery behind the French HydroPortail — distribution fitting, quantile curves and their uncertainties for hydrological series. The 2025 release re-implements the HBay Fortran executable in R, adding Bayesian estimation from historical flood records with censored and interval-valued data and systematic measurement error, plus a triangular distribution and truncated random generation.
◆ Where it's heading
The package started as a straight extraction of the portal's existing functions and is now absorbing the surrounding legacy toolchain: HBay was a separate compiled program with its own config files, and this release brings both the method and its configuration format inside R. Releases are sparse — three in two years, with an eighteen-month gap before the latest — and the intervening one was CRAN paperwork.
◆ Prediction
The HBay import came with a configuration-file reader for continuity with the old executable, which suggests further legacy hydrological tooling could follow the same path; the entries name no specific next target.
Alternatives to geocomplexity and HydroPortailStats
Other Infra & APIs 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 geocomplexity or HydroPortailStats.
estimatr
Fast design-based estimators for experiments, coasting on CRAN patches.
ggdist
The grammar of uncertainty visualization, now drawing the uncertainty in its own estimates.
ipaddress
IP address vectors for R that hit 1.0 and then went quiet.
ltertools
A column-key toolkit for stitching decades of ecological field data into one table.
finnts
Microsoft's automated forecasting framework, still mostly a one-maintainer effort.
See all geocomplexity alternatives → · See all HydroPortailStats alternatives →
Recent activity from geocomplexity and HydroPortailStats
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agogeocomplexityMaintainer surname spelling corrected for pinyin compliance
- 1y agoHydroPortailStatsHistorical flood records enter the estimator via an HBay port ⚡
- 1y agogeocomplexityPackage citation added
- 1y agogeocomplexitymoran_test migrates out to the shared sdsfun package
- 1y agogeocomplexityGeographical complexity measures and complexity-weighted GWR
- 3y agoHydroPortailStatsCRAN submission renames the return-period arguments
- 3y agoHydroPortailStatsFirst release: the HydroPortail statistical functions in R
Frequently asked questions
What is the difference between geocomplexity and HydroPortailStats?
Both compete on the same themes — r-package — within Infra & APIs. geocomplexity and HydroPortailStats 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 geocomplexity better than HydroPortailStats?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geocomplexity and HydroPortailStats 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 Infra & APIs products to evaluate alongside.
What are the best alternatives to geocomplexity?
Top geocomplexity alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "geocomplexity alternatives" section above for the current picks, or visit /alternatives/geocomplexity for the full list with editorial commentary on each.
What are the best alternatives to HydroPortailStats?
Top HydroPortailStats alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HydroPortailStats alternatives" section above for the current picks, or visit /alternatives/hydroportailstats for the full list with editorial commentary on each.