> For the complete documentation index, see [llms.txt](https://guides.mapaction.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.mapaction.org/clusters-and-sector-specific-products/food-security/baseline/types-of-livelihood.md).

# Types of livelihood

Showing the general predominant types of livelihood across the region (range land, cropping, river/lake or sea fishing or where cash based economy dominates).

### Strategic or operational?

Strategic

### Basemap, baseline or situational?

Baseline

### When might it be produced?

As early as possible in a response.

### Intended audience

World Food Programme (WFP) and the Food and Agriculture Organization (FAO) may use these for contextualising the crisis.

### Influence on humanitarian decisions

Supports a contextual understanding of the area of interest. Useful for understanding broad-scale risks to the population.

### Methods

Use a simple basemap to show typical livelihood zones (e.g. <http://fews.net/east-africa/kenya/livelihood-zone-map/march-2011>) with key geographical features (rivers, lakes, terrain etc).

### Data

* Agricultural land
* Waterbodies


---

# 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:

```
GET https://guides.mapaction.org/clusters-and-sector-specific-products/food-security/baseline/types-of-livelihood.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
