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 stockplotr — 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.
A stock-assessment plotting package is growing a table engine to match its figures.
stockplotr generates the figures and, since 0.8.0-beta, the tables that go into NOAA fisheries stock assessment reports. The 0.8.0 release swapped the table backend from flextable to gt and shipped table_landings() as the first table function; 0.9.0 exported it with an interface deliberately mirroring the plot functions. Alongside that, convert_output() moved in from the sister package asar so model output is standardized here rather than upstream.
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.
stockplotr generates the figures and, since 0.8.0-beta, the tables that go into NOAA fisheries stock assessment reports. The 0.8.0 release swapped the table backend from flextable to gt and shipped table_landings() as the first table function; 0.9.0 exported it with an interface deliberately mirroring the plot functions. Alongside that, convert_output() moved in from the sister package asar so model output is standardized here rather than upstream.
The package is consolidating the whole report-artifact pipeline in one place: standardize model output, then emit both figures and tables from the same long-format frame. Pulling convert_output() out of asar because stockplotr depended on it more heavily is the clearest signal of where the center of gravity now sits. Everything is still tagged beta, and the plot function count is growing faster than the table one.
More table_* functions built on the gt foundation are the obvious next step, matching the existing plot_* set; the 0.9.0 notes describe table_landings() as the first of a revamped family rather than a one-off.
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 stockplotr.
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 stockplotr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. inbospatial and stockplotr 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 stockplotr 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 stockplotr alternatives in Analytics are ranked by recent ship velocity. Browse the "stockplotr alternatives" section above for the current picks, or visit /alternatives/stockplotr-r for the full list with editorial commentary on each.