osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
mlr3spatial vs nanoparquet
A side-by-side editorial comparison of mlr3spatial and nanoparquet — release velocity, themes, recent moves, and the top alternatives to consider.
mlr3spatial vs nanoparquet: at a glance
What is mlr3spatial?
Raster prediction in mlr3 finally returns class probabilities, not just hard labels.
mlr3spatial connects mlr3 learners to raster and vector spatial data, handling chunked prediction over large rasters through DataBackendRaster. Development is slow and fix-heavy: most releases in the last two years were compatibility work against mlr3 and paradox rather than new capability. 0.7.0 is the exception.
What is nanoparquet?
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.
mlr3spatial vs nanoparquet: editorial side-by-side
mlr3spatial
0.0ANALYTICS
Raster prediction in mlr3 finally returns class probabilities, not just hard labels.
◆ Current state
mlr3spatial connects mlr3 learners to raster and vector spatial data, handling chunked prediction over large rasters through DataBackendRaster. Development is slow and fix-heavy: most releases in the last two years were compatibility work against mlr3 and paradox rather than new capability. 0.7.0 is the exception.
◆ Where it's heading
The package tracks the mlr3 core rather than leading it — 0.5.0 and 0.6.1 exist to absorb upstream changes in paradox and mlr3. Against that background, 0.7.0 adding probability predictions to predict_spatial() is the first genuine capability increase in a while, arriving alongside two DataBackendRaster fixes for multi-band sources and similarly-named layers. Cadence is roughly one release per year.
◆ Prediction
Given the pattern, the next release is more likely to be compatibility work against a new mlr3 or terra version than another feature; further raster-backend edge cases around layer naming are the visible loose end.
nanoparquet
0.0ANALYTICS
nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.
◆ Current state
nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.
◆ Where it's heading
Almost every entry since 0.4.0 names another engine — Java, arrow-rs, Polars, Arrow schema metadata — which tells you the maintainers are treating cross-reader fidelity as the product rather than R-side ergonomics. The type system is filling in from the edges: DECIMAL beyond 8 bytes, UUID, FLOAT16 and INTERVAL as raw lists, and now 64-bit integers with an explicit read-type option instead of a silent cast to double. Writing to `:stdout:` points at a second audience, shell pipelines rather than interactive R.
◆ Prediction
The remaining unmapped Parquet types the changelog has been parking in raw-vector lists — FLOAT16 and INTERVAL — are the obvious next targets, following the same pattern by which DECIMAL and UUID graduated to real R types.
Alternatives to mlr3spatial and nanoparquet
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 mlr3spatial or nanoparquet.
ymlthis
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all mlr3spatial alternatives → · See all nanoparquet alternatives →
Recent activity from mlr3spatial and nanoparquet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agomlr3spatialpredict_spatial() gains probability predictions
- 3mo agonanoparquet64-bit integer columns and writing Parquet to stdout
- 4mo agonanoparquetFiles now readable by the Java and Rust Parquet libraries
- 10mo agomlr3spatialCompatibility with mlr3 1.2.0
- 1y agomlr3spatialError on conflicting X/Y columns in sf objects
- 1y agonanoparquetReads Polars files that omit the dictionary page offset
- 1y agonanoparquetDate, FLOAT, and mixed-encoding read fixes
- 1y agonanoparquetSchema authoring and append_parquet arrive with a renamed API ⚡
- 1y agonanoparquetFixes a write_parquet crash
- 2y agomlr3spatialCompatibility with paradox 1.0.0
- 3y agomlr3spatialUse terra::inMemory() instead of the @ptr slot
- 3y agomlr3spatialspatial_predict() accepts stars, sf and Raster* inputs
Frequently asked questions
What is the difference between mlr3spatial and nanoparquet?
They serve adjacent needs but don't currently overlap on shipped themes. mlr3spatial and nanoparquet 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 mlr3spatial better than nanoparquet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mlr3spatial and nanoparquet 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.
What are the best alternatives to mlr3spatial?
Top mlr3spatial alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3spatial alternatives" section above for the current picks, or visit /alternatives/mlr3spatial for the full list with editorial commentary on each.
What are the best alternatives to nanoparquet?
Top nanoparquet alternatives in Analytics are ranked by recent ship velocity. Browse the "nanoparquet alternatives" section above for the current picks, or visit /alternatives/nanoparquet for the full list with editorial commentary on each.