> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/academy/reports-and-papers/mapping-impact.md).
# Mapping Impact
The state of geospatial tool capacity for restoration practirion
Even the best geospatial tools fall flat if the people using them don’t have the time, training, or systems to match. While supporting users in the FieldDoc system, we received a steady stream of feedback alluding to that reality. That insight drove us to ask a simple but important question: What is the spectrum of geospatial capacity across FieldDoc users? Are they interested or able to fully integrate spatial data into their everyday work?
In April 2025, The Commons sent a survey to all registered FieldDoc users to better understand how restoration and conservation teams are managing geospatial data. We wanted to learn what tools practitioners rely on, where GIS capacity is strong, and where it’s limited—or missing entirely.
The respondents revealed clear patterns—and actionable opportunities. The restoration sector may be a nature-based industry, but their access to and confidence with creating and managing geospatial data falls far short of universal standards that some technical providers and data collectors expect.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.fielddoc.org/academy/reports-and-papers/mapping-impact.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
