Compare hazards
Evaluate heat, cold, rain, wind and soil moisture with one severity vocabulary.
← All crop tools
Illustrative agriculture imageryCROP RISK SIMULATOR
Stress-test a crop before the weather tests the field.
Explore heat, cold, heavy-rain, strong-wind and dry-soil scenarios. Every factor shows its value, threshold and severity so preparedness can be discussed with evidence.
AVAILABLE · SCENARIO SCREENINGSee how it works ↓
THE DECISION IT SUPPORTS
Which near-term stresses should the team prepare for first?
The simulator turns supplied forecast values into a consistent factor-by-factor screen. It prioritises scouting and readiness, but it does not predict yield or insured loss.
Built for
- Farm advisory teams
- FPO coordinators
- Agricultural platforms
- District planning teams
WHY TEAMS USE IT
Turn broad data into a clearer next step.
Each result is designed to narrow a decision, show the inputs behind it, and surface what must still be checked locally.
Test what-if cases
Change inputs to see how hotter, wetter or windier periods alter the picture.
Focus field checks
Use high-severity factors to decide where attention is needed first.
Communicate context
Share the threshold and value behind an alert rather than an unexplained warning.
FROM REGION TO FIELD
See where each signal fits.
Images illustrate the operational setting. They are not live observations; use source timestamps and local measurements for decisions.
MOISTURE STRESSCompare heat and dryness
Regional stress signals focus scouting; crop symptoms and root-zone measurements confirm them.
SCOUTINGTurn alerts into observations
Field checks distinguish weather exposure from pest, disease and nutrient causes.
LOCAL SENSORGround the model in the field
Root-zone moisture adds specificity a regional forecast cannot provide.
THE INFORMATION STACK
What goes in—and what it helps explain.
Availability is stated per input. AtmosGrid never converts a missing parcel observation into a made-up field value.
INFORMATIONSOURCEHOW IT IS USEDSTATUS
01Crop IDAtmosGrid profileSelects crop-specific temperature limits.REQUIRED
02Maximum temperatureForecast / callerScreens heat exposure.OPTIONAL
03Minimum temperatureForecast / callerScreens cold exposure.OPTIONAL
0424-hour rainForecast / callerFlags heavy rain and access concerns.OPTIONAL
05Wind speedForecast / callerScreens lodging and fieldwork risk.OPTIONAL
06Soil moistureSensor / modelAdds dry-soil context.CLIENT INPUT
A PRACTICAL WORKFLOW
From input to reviewable decision.
The workflow keeps model context, field evidence and human approval in their proper places.
- 01
Select crop and period
Use the crop in the field and a forecast period relevant to the action.
- 02
Supply comparable values
Keep timestamps, units and source clear.
- 03
Read individual factors
Overall risk is the highest factor; inspect why.
- 04
Overlay crop stage
Threshold effects differ at emergence, flowering and maturity.
- 05
Trigger proportionate action
Use moderate risk for readiness and high risk for targeted checks.
HOW INFORMATION BECOMES USEFUL
Examples of decisions it can inform.
These are screening patterns, not automatic instructions. Operational thresholds and local advisories remain authoritative.
Heat in a sensitive period
- Signal
- Temperature exceeds the crop profile ceiling.
- Useful action
- Prioritise irrigation review and scouting.
- Check before acting
- Stage, humidity and water availability.
Heavy rain before operations
- Signal
- Daily rainfall crosses the screen.
- Useful action
- Reassess access, drainage and input timing.
- Check before acting
- Sub-daily intensity is not represented.
Strong wind near maturity
- Signal
- Wind exceeds the threshold.
- Useful action
- Inspect lodging-prone fields.
- Check before acting
- Variety, plant height and gusts.
FOR PRODUCT TEAMS
A transparent API contract.
The response exposes gaps and limitations so an application can explain confidence instead of hiding it.
/api/v1/agriculture/india/crop-risk-simulateExample request
{
"cropId": "wheat",
"weather": {
"maxTemperatureC": 39,
"rainMm24h": 80, "windKph": 20
}
}decision responseExample response
{
"overallRisk": "high",
"factors": [
{ "id": "heat", "severity": "high",
"value": 39, "threshold": 25 }
],
"dataGaps": ["soilMoistureFraction"]
}CAPABILITY BOUNDARIES
Useful now. Honest about what comes next.
Supported now
- Transparent per-factor thresholds
- Heat, cold, rain, wind and dry-soil screens
- Caller-controlled scenario comparison
- Explicit missing-factor output
Additional data required
- Crop stage and variety sensitivity
- Field soil moisture and irrigation status
- Pest and disease observations
- Calibrated local yield or loss models
BUILD RESPONSIBLY
Use the result to focus attention—not replace field judgment.
Pair AtmosGrid’s regional weather context with local measurements, crop stage, variety guidance and qualified agricultural advice.