> For the complete documentation index, see [llms.txt](https://docs.mapeo.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapeo.app/espanol/guia-de-referencia-completa/customization-options/custom-configurations/creating-custom-configurations/codificar-la-configuracion/creating-categories.md).

# Creating categories

{% hint style="info" %}
To review key information on defining categories, see [Categorías](/espanol/guia-de-referencia-completa/customization-options/custom-configurations/creating-custom-configurations/planeando-la-configuracion-y-la-estructura-de-datos/categorias.md).
{% endhint %}

### In the `presets` directory, customize the `.json` files

In the **presets** directory, each `.json` file needs:

* `icon` must mach the name of an icon in the `icons` folder - use prefix only, excluding the size refernce and file extension (eg. for `fishing-24px.svg/fishing-100px.svg` use `fishing`).
* `name` will be the human-readable label shown to the user
* `geometry` must be an array of `point` ,`area`, and/or `line` (All categories for use in Mapeo Mobile must include `point`.)
* `sort` (optional) is an integer that will determine the order in which categories are displayed on the **Categories** screen of Mapeo Mobile. If no `sort` is included, categories will be listed alphabetically by `name`.
* an array of `fields` (optional) which should match the `key` created in the fields directory. Fields will be displayed to users in the order they are listed in the `fields` array.
* `color` (optional) determines the color of observation dots on the map. (Dots fall back to orange if no color is defined.) Value can be a hex code, CSS color name or any string supported by [validate-color](https://github.com/dreamyguy/validate-color).

#### Example preset file (`fishing-site.json`):

```
{
    "icon": "fishing",
    "name": "Fishing Site",
    "sort": 10,
    "color": "#13D5CF",
    "fields": [
        "name"
    ],
    "geometry": [
        "point",
        "area"
    ]
}
```


---

# 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.mapeo.app/espanol/guia-de-referencia-completa/customization-options/custom-configurations/creating-custom-configurations/codificar-la-configuracion/creating-categories.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.