> For the complete documentation index, see [llms.txt](https://docs.answr.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.answr.space/api-data-layers/natural-disasters/drought-probability.md). # Drought Probability Drought hazard refers to the [consecutive dry days](/api-data-layers/climate-analytics/climatic-variables.md#consecutive-dry-days) that might occur during seasons. Dry days are the days at which rainfall height less than 0.1mm is measured. Drought hazard has four severity levels (Low, Moderate, High, Extreme). Low drought hazard corresponds to 30 to 50 days without rain, moderate to 50 to 75 days without rain, high to 75 to 80 days without rain, and extreme to more than 80 days. For each of the severity levels, drought hazard is calculated for each of the 4 seasons. The returned values of the drought hazard are probabilities of exceeding the above duration thresholds per severity class per calendar month. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.answr.space/api-data-layers/natural-disasters/drought-probability.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.