> For the complete documentation index, see [llms.txt](https://docs.predicteasy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.predicteasy.com/data-preprocessing/label-encoding.md).
# Label Encoding
Label encoding is a technique used to **convert categorical data into numerical format.** It assigns a unique integer to each category, allowing algorithms to work with categorical variables. For example, converting 'Red', 'Blue', and 'Green' to 0, 1, and 2, respectively.
**Steps to follow :**
1. Identify and highlight the columns you wish to label encode. Click and drag to select the specific range (e.g., A1:A30).
2. Look for the "Label Encoding" option within PredictEasy and select specific range.
3. If the selected area has headers, make sure to check the checkbox designated for headers. This ensures that the add-on considers the header row as header during the label encoding process.
4. Click the "Encode" button within the PredictEasy interface. This action triggers the label encoding process.
####
---
# 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.predicteasy.com/data-preprocessing/label-encoding.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.