Sources and licensing
Phoeniks records the origin, ingest time and licence of every input, and enforces those licence terms before a derived record can be exposed commercially. Provider neutrality is deliberate: no single satellite or weather vendor is load-bearing.
- Seven, radar to official statistics
- Origin, ingest time, licence
- Automatic, from the source registry
- None load-bearing
Primary sources#
| Sentinel-1 SAR | Radar imagery | Soil-moisture proxy, cloud-independent monitoring |
| HLS | Optical imagery | LAI and FAPAR time series |
| AgERA5 | Reanalysis | Agrometeorological driving variables |
| CHIRPS | Rainfall | Precipitation where station density is low |
| France RPG | Land registry | Open field boundaries |
| IBGE SIDRA | Official statistics | Municipal yield reference |
| CIMMYT Dataverse | Trial data | Model calibration |
Licence enforcement#
A source registry holds the licence terms for every portal and dataset. Records whose terms do not permit commercial redistribution are excluded from commercial surfaces automatically rather than by manual review.
Frequently asked
- Can a client bring their own data?
- Yes. Client-supplied data enters the same provenance and evidence-level treatment as public sources, and is isolated to that client's tenant.
Related pages
Methodology
The Phoeniks methodology: a process-based APSIM, DSSAT and ORYZA ensemble, scenario configuration, scoring engine and a reproducibility ledger.
Validation and evidence
Holdout protocol, calibration, tail and covariance testing, evidence scoring levels and the reproducibility ledger behind every Phoeniks figure.
Security and governance
Access control, tenant isolation, audit logging, encryption, data residency and incident response across the Phoeniks platform.
See also
Request access
Institutional access. No self-serve trial.