> For the complete documentation index, see [llms.txt](https://docs.basin.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.basin.global/appendix/ecosystem-services-dependencies-and-risks/by-sector-and-industry.md).
# By Sector & Industry
The following sections delve into the nature-related risks and dependencies across 11 GICS sectors consisting of 157 sub-industries and 150+ economic production processes. As applicable, each sector and industry is cross referenced to SASB and NACE.
Industries are ordered based on the S\&P Ecosystem Footprint, prioritizing sectors by their impact measured in hectares. This metric integrates three critical aspects: the **land area** affected by a company's operations, the **extent of reduction in ecosystem integrity**, and the **importance of the impacted ecosystems**. By amalgamating these factors, it calculates a company's equivalent impact on key global ecosystems in terms of biodiversity conservation and service provision, expressed as the number of hectares of the most significant ecosystems fully degraded.
## GICS Sectors by Ecosystem Footprint
---
# 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.basin.global/appendix/ecosystem-services-dependencies-and-risks/by-sector-and-industry.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.