Data and method
From observation to decision: a transparent pipeline
Provider interface
Time series for plots, spans and routes.
Decision engines
Rules and weights in code, with tests.
Record
Result, inputs and reasoning are stored together.
Delivery
Dashboard, reports, CSV and REST API.
How does it work?
Deforestation engine (Menşe)
- Confidence level and reasoning lines
- Comparison with the alert a coarse loss layer would raise
- Same input → same result
Deterministic
Same observation, same decision. Every result is stored with its inputs.
Vegetation engine (Koridor)
- Weighting by customers served and fire zone
- A recommended cycle per span
- Trim audits
Deterministic
Same observation, same decision. Every result is stored with its inputs.
Surface change engine (Gözcü)
- A target time by priority
- Area change and trend
- False-alarm rate
Deterministic
Same observation, same decision. Every result is stored with its inputs.
Designed for the long term
Frequently asked questions
Frequently asked questions about data sources and method.
Would you like a short introductory call?
Get in touchDoes FORESTOS have its own satellites?
No. FORESTOS takes its observation data from a provider interface; which provider is connected is decided at installation.
Is the data in the demo environment real?
No. In the demo environment observation series are generated synthetically and deterministically; the screens carry this note.
Are decisions made by AI?
No. All three engines are deterministic, unit-tested code working with documented rules and weights.
