> 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 and upgrading How to update an existing GeoDin installation to a newer version, and how to keep the GeoDin Help files current from inside the Help window. ## Update an existing GeoDin installation 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.geodin.com/administration/updating-and-upgrading.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.