> For the complete documentation index, see [llms.txt](https://docs.geopard.tech/geopard-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geopard.tech/geopard-tutorials/gis-quick-hints/qgis-change-string-to-number-values-in-the-shapefile.md).

# QGIS: convert a text field to a number in a shapefile

Use to\_real() or to\_int() in the QGIS Field Calculator to turn text values into numbers, keep decimals, and fix rate or yield columns that will not import.

Open the attribute table, start the Field Calculator, create a new decimal field and enter `to_real("your_field")`. Use `to_int()` for whole numbers. If decimals disappear after saving, set the output field length to 0 or a precision above zero. Numbers stored as text are the usual reason a yield or rate column will not colour a map or import as a rate.

{% hint style="success" %}
Upload the fixed file and see it as a map: [Start free](https://app.geopard.tech/auth/sign-up?utm_source=docs\&utm_medium=cta\&utm_campaign=qgis-change-string-to-number-values-in-the-shapefile)
{% endhint %}

In QGIS, you can convert a string to a number using the "Field Calculator" tool. First, open the attribute table for the layer you wish to modify. Next, click the "Open Field Calculator" button. In the "Expression" box, type "to\_real(" followed by the name of the field containing the string you want to convert, and closing parenthesis. For example, to convert a string field named "string\_field" to a numeric field, input "to\_real("string\_field")" in the Expression box. You can also modify the output field name and data type by selecting the appropriate options. Finally, click "OK" to complete the conversion. The original string field will remain in the attribute table, while the new numeric field will be added to the table.

<figure><img src="https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2Fi3rxrGu9XbcEMSGWGGEX%2FScreenshot%202023-04-03%20at%2017.22.03.png?alt=media&amp;token=1425fbc0-f7fa-4d0d-b794-b50c8db37b8d" alt=""><figcaption></figcaption></figure>

1. Open "Properties"
2. Go to "Field Calculator"
3. Check "Update Existing field"
4. to\_real("attributeName")
5. Save edits
6. Repeat the same for each attribute

   <figure><img src="https://3272281156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2Fc6LPt5wG8QlPkfn1B00s%2FScreenshot%202023-04-03%20at%2017.29.49.png?alt=media&amp;token=86437f74-6d54-4cae-8e04-ff319e4769a6" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Upload the fixed file and see it as a map: [Start free](https://app.geopard.tech/auth/sign-up?utm_source=docs\&utm_medium=cta\&utm_campaign=qgis-change-string-to-number-values-in-the-shapefile)
{% endhint %}


---

# 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.geopard.tech/geopard-tutorials/gis-quick-hints/qgis-change-string-to-number-values-in-the-shapefile.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.
