HydroPortailStats
France's national flood statistics, ported out of Fortran and into R.
Comparison · Infra & APIs
geocomplexity vs metR
A side-by-side editorial comparison of geocomplexity and metR — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
geocomplexity vs metR: at a glance
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 metR?
A meteorology ggplot2 extension where the netCDF reader became the main event
metR supplies meteorological and oceanographic tools for R: contour and streamline geoms, EOF decomposition, wave fitting, and ReadNetCDF() for getting gridded data in. Development has concentrated heavily on that reader. Version 0.18.0 added subsetting by dimension index, so the first or last ten timesteps can be read without knowing how many exist; 0.18.1 moved time parsing to the CFtime package; 0.18.2 added cdo operations through rcdo and reading across multiple files in parallel, and fixed a subsetting bug where nearest-gridpoint matching could return data outside the requested range entirely.
geocomplexity vs metR: 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.
metR
0.0INFRA · APIS
A meteorology ggplot2 extension where the netCDF reader became the main event
◆ Current state
metR supplies meteorological and oceanographic tools for R: contour and streamline geoms, EOF decomposition, wave fitting, and ReadNetCDF() for getting gridded data in. Development has concentrated heavily on that reader. Version 0.18.0 added subsetting by dimension index, so the first or last ten timesteps can be read without knowing how many exist; 0.18.1 moved time parsing to the CFtime package; 0.18.2 added cdo operations through rcdo and reading across multiple files in parallel, and fixed a subsetting bug where nearest-gridpoint matching could return data outside the requested range entirely.
◆ Where it's heading
Two threads run through the releases. The first is tracking ggplot2, absorbing the linewidth aesthetic, the trans to transform rename and guide compatibility as each landed upstream. The second is narrowing scope while deepening the data path: GetSMNData() was made defunct as too specific for a general package, raster and gdal dependencies were removed, and the udunits2 dependency was dropped when it was orphaned, initially replaced by a homebrewed date parser and eventually by CFtime. The result is a package steadily shedding its own code in favour of specialised upstream libraries.
◆ Prediction
Expect further ReadNetCDF() work, since it has received features in four of the last five releases and the rcdo integration opens a large surface of operations to expose.
Alternatives to geocomplexity and metR
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 metR.
bsvarSIGNs
Sign, zero and narrative restrictions brought into the bsvars ecosystem.
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.
See all geocomplexity alternatives → · See all metR alternatives →
Recent activity from geocomplexity and metR
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agogeocomplexityMaintainer surname spelling corrected for pinyin compliance
- 7mo agometRSubset notation fix in the netCDF reader
- 11mo agometRcdo operations, parallel multi-file reads, and a subsetting correctness fix
- 1y agometRnetCDF time parsing handed to the CFtime package
- 1y agometRnetCDF subsetting by dimension index
- 1y agometRLongitude scales pass the transform argument correctly
- 1y agogeocomplexityPackage citation added
- 1y agometREOF rotation takes a function, and scope narrows
- 1y agogeocomplexitymoran_test migrates out to the shared sdsfun package
- 1y agogeocomplexityGeographical complexity measures and complexity-weighted GWR
Frequently asked questions
What is the difference between geocomplexity and metR?
Both compete on the same themes — r-package — within Infra & APIs. geocomplexity and metR 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 metR?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. geocomplexity and metR 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 metR?
Top metR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "metR alternatives" section above for the current picks, or visit /alternatives/metr for the full list with editorial commentary on each.