parallelDist
parallelDist is in pure preservation mode — one build fix every few years.
Comparison · Analytics
inbospatial vs pecan
A side-by-side editorial comparison of inbospatial and pecan — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
inbospatial vs pecan: at a glance
What is inbospatial?
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.
What is pecan?
PEcAn v1.10 makes land-management events a first-class input and parallelises the whole SDA workflow
PEcAn is a workflow framework for ecosystem modelling — it standardises meteorological and initial-condition inputs, drives a set of coupled process models such as SIPNET, ED2, BioCro and LDNDC, and runs uncertainty analysis and state data assimilation over the results. Version 1.10.0 adds an events schema with validation and a SIPNET writer, so disturbance and management events can be declared in JSON and turned into model input, and runs the entire SDA workflow in parallel. It also adds CH4 and N2O to the standard variable table and an AmeriFlux meteorological ensemble path with ERA5 fallback.
inbospatial vs pecan: editorial side-by-side
inbospatial
0.0ANALYTICS
A thin R wrapper over Flemish geospatial services, adding one standard at a time
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
pecan
0.0ANALYTICS
PEcAn v1.10 makes land-management events a first-class input and parallelises the whole SDA workflow
◆ Current state
PEcAn is a workflow framework for ecosystem modelling — it standardises meteorological and initial-condition inputs, drives a set of coupled process models such as SIPNET, ED2, BioCro and LDNDC, and runs uncertainty analysis and state data assimilation over the results. Version 1.10.0 adds an events schema with validation and a SIPNET writer, so disturbance and management events can be declared in JSON and turned into model input, and runs the entire SDA workflow in parallel. It also adds CH4 and N2O to the standard variable table and an AmeriFlux meteorological ensemble path with ERA5 fallback.
◆ Where it's heading
Two directions are visible. The framework keeps widening what it can represent — more standard variables, more carbon pools in BADM-based initial conditions, more coupled models — and it keeps industrialising the parts that used to be manual, from automated package documentation to qsub job-array expansion to parallel assimilation. The events schema is the first of these that gives users a declarative input format rather than a function to call, which is a different kind of extension than adding another model coupling.
◆ Prediction
The events schema currently has one model writer, for SIPNET, so the obvious next step is writers for the other coupled models — otherwise the format only benefits a single backend of the several PEcAn drives.
Alternatives to inbospatial and pecan
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 pecan.
cairo
Cairo finally catches R's graphics engine, all the way to GE API 16.
rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
mutagen
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
See all inbospatial alternatives → · See all pecan alternatives →
Recent activity from inbospatial and pecan
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 4mo agoinbospatialOGC API Features querying and WCS layer discovery arrive
- 7mo agopecanEvents schema, parallel SDA workflow, CH4 and N2O standard variables ⚡
- 1y agopecanAutomated pkgdown docs for all packages; qsub job-array support
- 1y agopecanLDNDC coupling, soilgrids carbon extraction, SDA observation prep
- 1y agopecanPFT-specific sensitivity analysis and BioCro 1.0 support
- 1y agopecanBioCro output renamed to PEcAn standard names; RCE fix
- 1y agopecanPEcAn.utils namespace cleanup; deprecated model2netcdf removed
- 1y agoinbospatialFlanders digital elevation model becomes queryable
- 2y agoinbospatialWMS and WMTS shorthands plus projection distortion utilities
Frequently asked questions
What is the difference between inbospatial and pecan?
Both compete on the same themes — r-package — within Analytics. inbospatial and pecan 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 inbospatial better than pecan?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. inbospatial and pecan 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 inbospatial?
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.
What are the best alternatives to pecan?
Top pecan alternatives in Analytics are ranked by recent ship velocity. Browse the "pecan alternatives" section above for the current picks, or visit /alternatives/pecan-r for the full list with editorial commentary on each.