> 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/svn/hitri-gis-namigi/qgis-spremeni-besedilne-vrednosti-v-stevilske-v-shapefileu.md).
# QGIS: spremeni besedilne vrednosti v številske v shapefileu
Pretvorite besedilne atribute v številčne vrednosti v QGIS za analizo in uvoz.
V QGIS lahko niz pretvorite v število z orodjem »Izračun polj«. Najprej odprite atributno tabelo za sloj, ki ga želite spremeniti. Nato kliknite gumb »Odpri izračun polj«. V polje »Izraz« vnesite »to\_real(« in za njim ime polja, ki vsebuje niz, ki ga želite pretvoriti, ter zaključno oklepaj. Na primer, če želite nizovno polje z imenom »string\_field« pretvoriti v številsko polje, v polje »Izraz« vnesite »to\_real("string\_field")«. Ime izhodnega polja in podatkovni tip lahko tudi spremenite z izbiro ustreznih možnosti. Na koncu kliknite »V redu«, da dokončate pretvorbo. Izvorno nizovno polje bo ostalo v atributni tabeli, novo številsko polje pa bo dodano v tabelo.
1. Odprite »Lastnosti«
2. Pojdite na »Izračun polj«
3. Označite »Posodobi obstoječe polje«
4. to\_real("attributeName")
5. Shrani urejanje
6. Ponovite enako za vsak atribut
---
# 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/svn/hitri-gis-namigi/qgis-spremeni-besedilne-vrednosti-v-stevilske-v-shapefileu.md?ask=&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.
