whirl
whirl turned script logging into a standardized provenance artifact regulators can read.
A side-by-side editorial comparison of gpkg and rapr — 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.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
rapr pulls Rangeland Analysis Platform data into R — vegetation cover and production rasters derived from Landsat and Sentinel-2, plus the tabular summary APIs. The 1.1.3 release replaces the single-purpose table function with a general get_rap_table() covering the cover, coverMeteorology, production and production16day endpoints. The package reached CRAN in 2025 and is maintained by brownag, who also maintains the GeoPackage interface gpkg.
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.
rapr pulls Rangeland Analysis Platform data into R — vegetation cover and production rasters derived from Landsat and Sentinel-2, plus the tabular summary APIs. The 1.1.3 release replaces the single-purpose table function with a general get_rap_table() covering the cover, coverMeteorology, production and production16day endpoints. The package reached CRAN in 2025 and is maintained by brownag, who also maintains the GeoPackage interface gpkg.
The shape is familiar for a young API client: add access to one endpoint, then generalise it once a second endpoint proves the pattern. get_rap_production16day_table() arrived in 1.1.0 and was deprecated three releases later in favour of a product argument. Between those, the work was error handling — empty geometries, server-side HTTP failures, warning timing — the unglamorous half of wrapping a remote service. The 1.0.0 release had already set the ambition by exposing both the 30m Landsat and 10m Sentinel-2 sources behind one argument.
Expect the remaining RAP endpoints to be folded into get_rap_table() as they are needed, and the deprecated 16-day function to be removed once the general interface has been out long enough.
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 rapr.
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.
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
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — geospatial, r-package, raster — within Infra & APIs. gpkg and rapr 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 rapr 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 rapr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rapr alternatives" section above for the current picks, or visit /alternatives/rapr for the full list with editorial commentary on each.