Multi-user Mode

Multi-user Environment

Gemini Terrain has two alternatives for multi-user environments:

1. Cloud project in Gemini Connected
2. Activation of multi-user mode for projects stored on server

Note

For best collaboration, we clearly recommend using cloud projects in Gemini Connected rather than projects stored on server. From our perspective, cloud projects have replaced the activation of multi-user mode.

For more information about cloud projects in Gemini Connected, see the chapter Gemini Connected in the user manual. Note that cloud projects use the principles described below, in addition to a range of other functionality.

The old multi-user mechanism that Gemini Terrain still has available for projects stored on server is described below. For more information about the various storage structures you work with, see the section on file types.

Activating Multi-user Mode

The old multi-user mode is activated by checking Multi-user mode (does not automatically open files for editing) via Settings Gemini Terrain... - General.

This option is automatically activated and grayed out for cloud projects.

Project File

The program only takes write permissions when changes are made to the project, for example with the buttons Info..., Edit... or Add.... This means that none of the users have permanent control over the project file - everyone works initially against the drawing list without write permissions (marked as "READ-ONLY" in the program header).

If other users have taken write access to the prj file, you will receive a message informing you about this:

Drawings

For drawings (BIM files), multi-user access is handled through the project menu. Drawings that are opened by a user are marked with the symbol # and username for other users. Such drawings can only be opened as "read only" (write-protected).

Figure: Project menu where drawing Demo4001 Map is opened by user mato, while drawing Demo4011 Regulatory plan is opened by user.

Application Layers and Models

Multi-user mode is supported for Gemini Terrain's own storage structures, i.e., application layers and projected models (aly/gmi, SFI, EFI, XFI), so that multiple users can work simultaneously on the same project with controlled access to files. These elements have a function to Open/lock for editing. When a user has opened a file for editing, others will not be able to edit the same file.

Symbol Usage in Lists

The following indicators are displayed in the lists for application layers and models:

• \<Blank>: Open for editing by you
• # before model name: Locked for editing, but possible to open
• #\<Username>: Locked for editing (read only), locked by another user

Here is an example of how this is displayed in the program:

Figure: Use of indicators in the model list

Updates from Other Users

When refreshing the screen with the command Refresh Screen ([F5]) or the command RP (RePaint), all locked layers will be checked against the last timestamp for the last reading. If the file on the server has been updated, you will receive a message that the layer has changed and a question about re-reading the file.

Handling Crash Situations

When a user opens a file for editing, lock files with the same name are created. For an application layer, for example:

• .aly~
• .gmi~

The lock files contain information about which user created them. The lock files are automatically deleted when the application layer is locked for editing or when it is closed (by exiting the drawing).

If the program crashes while a user has an application layer open for editing, the lock files will remain and block other users. If you restart the program after this crash, the automatic project recovery will usually clean up these files. If this does not happen, the lock files must be deleted manually. Remember that you can always find out who created the file, as it will contain the username.

Hidden Files

The lock files have the Hidden property enabled. To see these files, you must enable the display of hidden files in Windows Explorer.