> 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/dnevnik-sprememb-in-izdaje-izdelka/izdaja-spletne-razlicice-februar-2024-cena-na-povrsino-enote.md).

# Izdaja spletne različice februar 2024 (cena na površino, enote)

Ta izdaja izboljšuje GeoPardove cene, vključno z izbiro enot in upravljanjem naročnin.

### Cenik: Izbira enote mere

Ekipa GeoPard z navdušenjem predstavlja novo funkcijo, ki prinaša dodatno prilagodljivost v naš cenik. S to posodobitvijo lahko uporabniki GeoPard zdaj brez težav preklapljajo med hektarji in akri ter si tako izberejo enoto mere, ki ustreza njihovim željam. Namen te izboljšave je zagotoviti bolj prilagojeno izkušnjo in našim uporabnikom omogočiti, da izberejo tisto, kar jim najbolj ustreza.

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FadoIJj05wBLU6ZgeBX21%2Funit_of_measure.gif?alt=media&amp;token=39fccb77-3abc-4fd8-9959-cc5250892eb8" alt=""><figcaption><p>Cenik: Izbira enote mere</p></figcaption></figure>

### Cenik: Upravljanje naročnine

Ker razumemo vrednost nemotenega postopka obnove naročnine, smo sistem dodatno izboljšali, da bi zagotovili neprekinjen dostop do GeoPard. Če ste obstoječi uporabnik, ki še ni uporabljal Stripe za plačila, vas **Upravljaj moj paket** gumb neposredno odpelje na stran Naročnina na paket. Če Stripe že uporabljate, vas isti gumb odpelje v Stripe Customer Portal.

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FUMprC4JOb4T1adevxp9e%2Frelease_feb2024_2.png?alt=media&amp;token=c98f5659-2d02-47d3-90f4-f571e259dd28" alt="" width="237"><figcaption><p>Cenik: Upravljanje naročniških paketov</p></figcaption></figure>

### Izboljšave za razvijalce:

\[FTR] Popravek razširjenega stanja razdelka oznak

\[FTR] Izboljšave obravnave napak

\[BUG] Popravek anketiranja uporabniških podatkov po uspešni naročnini

\[BUG] Popravek nalaganja podatkov polja med ustvarjanjem cone na zemljevidu

\[BUG] Popravek številčnega prikaza legende 3D zemljevida

<figure><img src="https://29491374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYICBELdyAXXebKAzfLOR%2Fuploads%2FKy5YYuayHsWmn8UEeuGU%2FScreenshot%202024-03-14%20at%2019.58.07.png?alt=media&amp;token=fdddf2dc-3dbb-43c4-9b17-c60161089ba4" alt=""><figcaption><p>Izboljšava legende 3D zemljevida</p></figcaption></figure>

\[BUG] Onemogoči izvoz PDF za objavljene nize podatkov

\[BUG] Popravek napake, če je bil zemljevid cone uspešno ustvarjen

<br>


---

# 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/dnevnik-sprememb-in-izdaje-izdelka/izdaja-spletne-razlicice-februar-2024-cena-na-povrsino-enote.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.