> For the complete documentation index, see [llms.txt](https://isbm.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://isbm.savimbo.com/practice-guide/id/land-rights/geocode-averaging.md).

# Cara melakukan geocode averaging

Cara termurah untuk membuat peta akurat di hutan

Anda dapat mengubah paket Anda kapan saja dari pengaturan penagihan workspace Anda. Perubahan berlaku segera.

### Langkah demi langkah untuk merata-ratakan geocode

{% stepper %}
{% step %}

#### Pilih cara Anda akan mendapatkan&#x20;

Ada banyak cara berbeda untuk mendapatkan geocode. Aplikasi yang berbeda punya tingkat kesalahan yang berbeda.&#x20;
{% endstep %}

{% step %}

#### Buat diri Anda nyaman

Anda harus mengambil titik itu beberapa kali secara berurutan. 30 menit di tempat yang sama adalah minimum Savimbo. Jadi bawalah buku, timer, dan buat diri Anda nyaman.&#x20;
{% endstep %}

{% step %}

#### Salin daftar yang bagus!&#x20;

XXXX
{% endstep %}
{% endstepper %}

Saat Anda upgrade di tengah siklus, Anda akan dikenai biaya prorata untuk sisa periode penagihan saat ini. Tagihan penuh berikutnya akan datang pada tanggal penagihan biasa Anda.


---

# 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://isbm.savimbo.com/practice-guide/id/land-rights/geocode-averaging.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.
