whirl
whirl turned script logging into a standardized provenance artifact regulators can read.
A side-by-side editorial comparison of gpkg and skytrackr — release velocity, themes, recent moves, and the top alternatives to consider.
An R interface to GeoPackage that keeps sanding down its own API
gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.
Light-based animal geolocation gets a second model that stops assuming the bird sat still.
skytrackr estimates animal positions from logger light data by fitting a sky-illuminance model. Three releases span the history: a 2023 v0.9 the author called functional but unpolished, a CRAN-compliant v1.0 in October 2025 that added batch reading and twilight screening, and a v2.0 six weeks later that is the first structural expansion. v2.0 pulls the data-selection and calibration steps out of the main skytrackr() call and exposes them as stk_filter(), stk_calibrate() and stk_center().
gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.
The package is still finding its interface shape, and most releases pair a small capability with a deprecation or signature change — destfile giving way to y, gpkg_create_dummy_features deprecated, vapour swapped out for gdalraster. The consistent direction is deferring to GDAL and terra conventions rather than inventing gpkg-specific behaviour, and pushing connection management out of users' hands. Cadence is roughly one release a year with dependency automation now in CI.
Expect further alignment of write-path defaults with GDAL conventions and continued deprecation-with-replacement of early argument names, with an ogr2ogr-style path for out-of-memory vector data flagged as a possibility rather than a commitment.
skytrackr estimates animal positions from logger light data by fitting a sky-illuminance model. Three releases span the history: a 2023 v0.9 the author called functional but unpolished, a CRAN-compliant v1.0 in October 2025 that added batch reading and twilight screening, and a v2.0 six weeks later that is the first structural expansion. v2.0 pulls the data-selection and calibration steps out of the main skytrackr() call and exposes them as stk_filter(), stk_calibrate() and stk_center().
The arc is toward exposing internals the package used to hide. Each release takes a step that was buried inside the main fitting call and turns it into a function the researcher can inspect, plot and constrain, with the scale parameter now estimated across a whole dataset rather than guessed. The new individual light model is the sharper turn: it drops the stationarity assumption behind the original diurnal fit and solves each observation along a constant-bearing course from the previous position.
The author describes the individual model's robustness as still being evaluated and its convergence as more fickle than the diurnal approach, so the next release most likely tunes convergence and documents when each model applies rather than adding a third.
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 gpkg or skytrackr.
whirl turned script logging into a standardized provenance artifact regulators can read.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
A small B-Cubed utility for turning R Markdown into publishable docs
R's logging package handed to new maintainers and rebuilt from the inside out
Four dormant years end with a test fix, not a feature
See all gpkg alternatives → · See all skytrackr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. gpkg and skytrackr 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. gpkg and skytrackr 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.
Top gpkg alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gpkg alternatives" section above for the current picks, or visit /alternatives/gpkg for the full list with editorial commentary on each.
Top skytrackr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "skytrackr alternatives" section above for the current picks, or visit /alternatives/skytrackr for the full list with editorial commentary on each.