> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/administration/updating-and-upgrading.md).

# Updating & Upgrading

## Updating & Upgrading

#### Update an existing GeoDin installation

## Updating a GeoDin Version

Use in any case a different directory for the installation of the actual GeoDin version than your previous version of GeoDin and carry out the steps of the installation as described above. Start GeoDin system after the installation and apply the changes on object types, dictionaries, measurement value structures etc., which were carried out in your previous version of GeoDin. For this change to **System** and click on the entry **System configuration**. Start the system adjustment by double-clicking the method icon.

#### Updating the GeoDin Help files

The GeoDin Help content evolves alongside the program, so it should be updated regularly alongside GeoDin itself. There are two ways to update it:

1. Click the **Online-Update** button in the top toolbar of the Help window.
2. Or update manually: download the language archive (for example `german.zip`) from the help update location, then replace the same-named zip archive under `...\Help\RTF\` in your GeoDin installation, without unpacking it.


---

# 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.geodin.com/administration/updating-and-upgrading.md?ask=<question>&goal=<endgoal>
```

`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.