Copying and Transferring Projects
Copying and transferring GeoDin projects - duplicating, exporting, and moving projects between databases.
Projects can be copied within the same database (for branching variants or template re-use) or transferred between databases (e.g. moving a project from a local Access database to a shared client-server database).
GeoDin offers project-level Add Objects, Copy Project, and Publish and Export methods for these workflows. The exact options depend on whether the destination is in the same database, in a different database of the same connection, or in a different database type entirely.
Handing over data to state authorities (Landesämter)
When delivering data to a state geological authority (Landesamt), the recommended approach is to use a dedicated transfer database rather than sending your main project database.
Step-by-step workflow:
Step 1: Create the transfer database
Create a dedicated transfer database - this can be either an Access (.accdb) file or a PostgreSQL database. Connect it to GeoDin as a separate database connection.
Ensure the transfer database is accessible on the GeoDin server (e.g. a local path such as C:\Temp\) and not only on a long UNC network path. Very long UNC paths can cause connection issues with Access files.
For the comprehensive reference - full syntax, all options, edge cases - see Working with Projects.
Last updated
Was this helpful?