Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of inbospatial and spatstat — release velocity, themes, recent moves, and the top alternatives to consider.
A thin R wrapper over Flemish geospatial services, adding one standard at a time
inbospatial gives R users direct access to Flemish and Belgian government spatial services without hand-writing request URLs. Three releases over three years have built it up service by service: WMS and WMTS tile shorthands and projection-distortion utilities first, then the Flanders digital elevation model, and now OGC API Features querying plus layer discovery for WCS services. Much of each release is hardening the MHT-file parsing that these services return.
The spatstat umbrella package, now mostly a pointer to the sub-packages doing the work
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
inbospatial gives R users direct access to Flemish and Belgian government spatial services without hand-writing request URLs. Three releases over three years have built it up service by service: WMS and WMTS tile shorthands and projection-distortion utilities first, then the Flanders digital elevation model, and now OGC API Features querying plus layer discovery for WCS services. Much of each release is hardening the MHT-file parsing that these services return.
The package grows by absorbing one more service standard per release rather than by adding abstraction. The 0.1.0 additions point the same way — get_feature_ogc() covers a newer OGC standard alongside the existing WCS and WFS paths, and get_wcs_layers() addresses the practical problem that you cannot query a coverage without first knowing what layers exist. Release cadence is slow and driven by which service the maintainers needed next.
Expect the next release to add another regional service endpoint or extend OGC API Features coverage, on a timescale of a year or more given the gaps between the three releases so far.
spatstat is the front package of a family that was split into specialised components — spatstat.geom, spatstat.random, spatstat.model, spatstat.explore, spatstat.univar and spatstat.sparse. Its own release notes reflect that: entries in this window are largely announcements of where the real changes landed, plus documentation and cross-reference maintenance. The codebase it fronts passed 200,000 lines as of 3.5-1.
The split is effectively complete and the umbrella's role has settled into coordination — tracking version dependencies across sub-packages and pointing users to them. The family has kept subdividing over this period, with spatstat.univar joining in 3.1-0. The one substantive user-facing addition here is documentation infrastructure: 3.3-0 added the ability to list the history of changes to a specific function, which is a navigational answer to a codebase now spread across many packages.
Expect this package's notes to continue summarising sub-package activity rather than carrying features of its own, since every release in this window does exactly that. Read spatstat.geom, spatstat.random and spatstat.model for the substance.
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 inbospatial or spatstat.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
See all inbospatial alternatives → · See all spatstat alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. inbospatial and spatstat 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inbospatial and spatstat 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.
Top inbospatial alternatives in Analytics are ranked by recent ship velocity. Browse the "inbospatial alternatives" section above for the current picks, or visit /alternatives/inbospatial for the full list with editorial commentary on each.
Top spatstat alternatives in Analytics are ranked by recent ship velocity. Browse the "spatstat alternatives" section above for the current picks, or visit /alternatives/spatstat-r for the full list with editorial commentary on each.