> For the complete documentation index, see [llms.txt](https://docs.landscale.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.landscale.org/assessment-guidelines/step-c/visualize-and-interpret-results.md).

# Visualize and interpret results

Following data collection and processing, the next step is to develop meaningful visualizations and provide clear interpretation of results. This enables end users to better understand the significance of the LandScale assessment findings.

### Upload visual elements

Visualizations translate raw data into accessible insights, revealing trends, patterns, and key messages that may not be obvious from numerical data alone. Well-crafted visuals support effective communication of complex information to a broad audience, regardless of technical expertise.

The assessment team may upload a range of visual elements, such as:

* Charts and graphs.
* Infographics.
* Maps.

These visuals will appear alongside the respective results once they are validated as a part of Step C.&#x20;

{% hint style="info" %}
**Recommended visualization types**

Visualization types should be selected based on the nature of the data and the insights to be conveyed:

* **Bar charts:** Compare quantities across categories or groups.
* **Line graphs:** Illustrate trends or changes over time.
* **Pie charts:** Display proportions or percentages within a whole.
* **Heat maps:** Visualize data density or spatial concentration.
* **Scatter plots:** Show relationships between variables.
* **Histograms:** Present the distribution of data.
* **Infographics:** Integrate multiple visuals into a cohesive narrative.
* **Geographic maps:** Display data with spatial or location-based components.

The selected format should effectively represent the data and emphasize key messages.
{% endhint %}

### Summarize insights and interpretations

Summarizing results is essential to support understanding—particularly for audiences unfamiliar with the landscape context. Summaries should be concise, accessible, and technically accurate.

Key elements to consider include:

* **Key trends:** What notable patterns or changes were observed in the data?
* **Comparative findings:** How do results vary across metrics or areas?&#x20;
* **Performance indicators:** What do the results reveal about progress or challenges?
* **Stakeholder relevance:** Why might these results matter to different stakeholder groups?&#x20;

A thoughtful combination of visualizations and clear interpretation increases the value, clarity, and usability of the LandScale assessment.

<figure><img src="/files/MdLn3TzfLT5WyxCfx2dj" alt=""><figcaption><p>Example of insights and interpretations derived from a result.</p></figcaption></figure>


---

# 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.landscale.org/assessment-guidelines/step-c/visualize-and-interpret-results.md?ask=<question>&goal=<endgoal>
```

`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.
