> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/basic-settings/fields/geo-fields.md).

# Geo Fields

> These are the fields required by the [Geo](/docs/modules/geo.md) module.

> When filtering for geo-fields: products will be displayed in the search results that have market IDs that meet the filter **and** market values that do **not** meet the filter.

| Field Type                       | Field Role                                     | Import Sources | Explanation                                                                                                                                      |
| -------------------------------- | ---------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| GEO                              | Market Location                                | GEO            | Field containing the locations of the markets.                                                                                                   |
| TEXT                             | Market ID                                      | GEO            | Field containing the market IDs, used for all the mappings.                                                                                      |
| TEXT or ALPHANUMERIC             | EITHER Product number OR Master article number | GEO and DATA   | Field with the product IDs, the Geo mappings should be attached to.                                                                              |
| TEXT or INTEGER or FLOAT or DATE |                                                | GEO            | Non-List-Field containing the values that shall be mapped to a market and product. For Geo to work properly, at least one field should be added. |


---

# 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.fact-finder.com/docs/basic-settings/fields/geo-fields.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.