> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/for-developers/data-dictionary.md).

# Data Dictionary

The data dictionary describes field names, units, sources and value interpretation for AlphaGeo’s data products. Use it alongside the relevant endpoint documentation: available fields depend on the product, endpoint and your subscription.

## API and download coverage

| Interface                                                                                             | Contents                                                                                                                                                                              |
| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Physical Risk API](/for-developers/alphageo-data-api/global-adaptation-layers-risk-api.md)           | Physical hazard features across nine hazards, including six hurricane return-period wind speeds and the derived 1,000-year category.                                                  |
| [Resilience Data API](/for-developers/alphageo-data-api/global-adaptation-layers-resilience-api.md)   | Adaptation features and societal resilience (`HDI`, `GFCP`, `VUL_POP`).                                                                                                               |
| [Climate Risk Scores API](/for-developers/alphageo-data-api/global-climate-risk-index-api.md)         | Physical and resilience-adjusted scores for nine hazards, overall scores and overall percentiles.                                                                                     |
| [Financial Impact Analytics API](/for-developers/alphageo-data-api/financial-impact-analytics-api.md) | Insurance, utilities, CapEx, exit-cap-rate adjustments, downtime, efficiency, productivity, maintenance and insurability fields.                                                      |
| [Portfolio Scores API](/for-developers/alphageo-data-api/portfolio-scores-api.md)                     | Portfolio averages of scores, plus FIA fields when authorized.                                                                                                                        |
| Portfolio downloads                                                                                   | Fields depend on the selected download. Financial Impact downloads also include `10Y_NPV`, `AAL` and `ADPT_ALPHA`; these are not returned by the public FIA or Portfolio Scores APIs. |

The public Physical Risk API returns 100- and 1,000-year flood depths. The wider download field set also includes 250- and 500-year flood depths, sea-level change (`SLR_CHG`) and burnability (`BURNABILITY_INDEX`). A field’s presence in the dictionary does not mean every endpoint returns it.

## Reading the values

* Check the unit for each field. For example, `INS_RATE_ANNUAL = 2` means 2% annual growth, while `10_YEAR_DISCOUNT = 0.25` means a 0.25-percentage-point addition to the exit capitalization rate.
* `HDI` and `VUL_POP` are delivered on a 0–100 scale. `HDI = 91` corresponds to an HDI of 0.91.
* The 2025 physical baseline primarily uses ERA5-Land reanalysis over 2020–2025, with coverage fallbacks; other hazards use source-specific baselines. See the [source and baseline FAQ](/faqs/data-products-faq.md).
* `data_version` is the service’s configured data-version label. The placeholder in documentation examples is not an actual version value.

## Request the dictionary

Request a link to the data dictionary using the form below.

{% embed url="<https://share.hsforms.com/10GKTMfk7QBuXA7ii8H6w1Q5kd7q>" %}


---

# 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://docs.alphageo.ai/for-developers/data-dictionary.md?ask=<question>&goal=<user_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.