Legacy Project Files¶
This chapter provides guidance on how to handle legacy project files when upgrading to newer versions of Gemini Terrain.
Upgrade Recommendations¶
Our new major release, version 21, has undergone extensive testing, both internally and with a selection of pilot customers, to ensure stability and performance. We have great confidence that this version will provide significant improvements. At the same time, we acknowledge that unexpected challenges can always arise in complex systems, and we have therefore allocated resources for rapid follow-up and bug fixes through the service release.
A question many will ask is whether to implement the new version on existing projects or complete the projects in the old version. We recommend upgrading now to take advantage of the new features and improved performance, and we are ready to assist you if you have questions or need support.
For local projects, we recommend taking a backup of the project before conversion.
Cloud projects have built-in history, which gives us confidence against unintended conversions. This means we can restore files to previous versions if needed. However, a challenge is that we must restore files manually, one by one. For controlled conversion of cloud projects, we can download a local copy of the project in advance. This makes it easier to restore the entire project if necessary.
If you encounter problems when updating legacy projects, you can go through intermediate versions, for example from version 17, then to version 18, and finally to version 19.
Note
We must manually copy any user-defined files from version 20's user folder to version 21's user folder after installation. For example, a missing MetadataUserNor.json file will cause application layers and models with references to attributes in this file to get REF_ERROR.
DDScad .prj and .bim Files¶
These files are always converted from one major release to another. If they are opened in version 21, for example, they cannot be opened in version 20 or older versions afterwards.
Gemini Terrain Data .aly\.gmi, .sfi, .xfi, and .efi Files¶
The format in these files does not necessarily change from one major version to another. Then they are not converted and can be added/opened in older versions since no changes have been made to the file formats.
Gemini Terrain 20¶
Projects created in Gemini Terrain 20 should be updated to version 21.
Gemini Terrain 20¶
Projects created in Gemini Terrain 20 should be updated to version 21.
Gemini Terrain 19¶
Application Layers¶
In version 20, the combined triangle net/point cloud object has been split into two separate objects, one for triangle net and one for point cloud.
Application layers are therefore converted when we open legacy projects in version 20. Only application layers that are used in drawings in the project are converted. All .aly files are upgraded with symbols, filters, and annotations for point clouds. Only .gmi files with point clouds are upgraded.
Note
This means you lose the point cloud data if you add/open the application layer in an older version after conversion.
Models¶
No changes in the models and no conversion when opened in version 20, so they can be added/opened in older versions.
Gemini Terrain 18¶
For projects with quantities registered to Gemini QuantiFlow, you must decide whether to complete the projects in version 18 or transition to the new methodology if the project is converted to version 19. This is described in more detail in a separate chapter, Important: Transition from Gemini Terrain Version 18 to 19.
For other projects created in Gemini Terrain 18, we recommend updating to version 19.
Note that the map legends in version 18 are in the file <projectname>_Ter.ini. In version 19, the map legends are in MapLegends.ini which can be located locally and in the user folder. The map legends are converted to the new ini file locally in the project.
Gemini Terrain 17¶
Projects created in Gemini Terrain 17 should be updated to version 18.
Gemini Terrain 16¶
Projects created in Gemini Terrain 16 should be updated to version 17. In version 16, user folders in the then-current Gemini Sync were local. Note that these become shared and synchronized in version 17.
Gemini Terrain 15¶
When it comes to legacy project files, there is one important change from version 15 to 16, and that is the local placement of cloud projects. To save disk space, this is now independent of the Gemini Terrain version. Old downloaded projects are not automatically deleted, but these can be cleaned up if desired.
Another change in this path is that it now includes the company name. The reason for this is that you can in principle represent several different companies, where each company has projects with the same name, which is now handled.
Here is an example of this name change, where changes are indicated in bold:
- Gemini Terrain 15:
C:\Users\vsh\AppData\Local\Gemini\Ter15\CloudCache\My Project\Demo-Nor - Gemini Terrain 16:
C:\Users\vsh\AppData\Local\Gemini\CloudCache\[Company Name]\My Project\Demo-Nor
Gemini Terrain 14¶
For projects created in Gemini Terrain 14, we recommend updating to version 15. However, there are a couple of things to be aware of.
Application Layers¶
Regarding application layers, we have a completely new attribute concept (metadata). This means that properties are converted when using the new version 15.
A template in the new concept consists of an .aly and a .gmi file. This means that the al_ file is discontinued in version 15. The old templates can still be used as they are converted.
Models¶
The SFI model has been updated from data version 11 to data version 12. This means that when transitioning to version 15, the model cannot be opened again in older versions. Furthermore, we also support surface boundaries on all layers.
The new attribute concept is also implemented for models.
Regarding .efi/.xfi models, these have not received a new version number, which means they can be opened in older versions, but the metadata will then disappear.
Note
Another thing to be aware of is that if you remove reference group attributes from the project level, we lose associated data in application layers and models. No warning is given about this.
Gemini Terrain 13¶
For projects created in Gemini Terrain 13, we recommend using the new version 14.
The road model has been updated from data version 10 to data version 11. This means that when transitioning to version 14, the model cannot be opened again in older versions. A new road dimensioning library has also been created, which means there may be small differences in the generation of road parameters for files from version 13 opened in version 14.
As always, we recommend backing up the project before continuing work on it in version 14.
Gemini Terrain 12¶
For projects created in Gemini Terrain 12, we recommend using the new version 13. As always, we recommend backing up the project before continuing work on it in version 13.
Note that all models (SFI, XFI, and EFI) have received new numbers in version 13 due to changes in file formats. They therefore cannot be opened in version 12 after being opened in version 13.
Note
Also note that the road model has received some new construction rules, especially in connection with the use of inner fill slopes and construction of troughs. This may cause differences in quantity calculations between version 12 and 13. See the news document for a detailed description of what has changed.
Gemini Terrain projects where quantity reporting has been performed to Gemini Connected must be copied to the Gemini Connected project in the cloud before quantity reporting continues.
Note
Note that in version 13, no automatic backup of the version 12 project is taken before it is converted to version 13. This must be done manually before the version 12 project is opened in version 13.
Gemini Terreng & Entreprenør 11¶
For projects created in Gemini Terreng & Entreprenør 11, we recommend using the new version 12.
It is unproblematic to go from version 11 to version 12.
Gemini Terreng & Entreprenør 10¶
For projects created in Gemini Terreng & Entreprenør 10, we recommend using the new version 11.
It is unproblematic to go from version 10 to version 11.
Gemini Terreng & Entreprenør 80¶
For projects created in Gemini Terreng & Entreprenør 80, we recommend using the new version 10.
It is unproblematic to go from version 80 to version 10. It is not recommended to go directly from version 80 to version 11.
Gemini Terreng & Entreprenør 73¶
For projects created in Gemini Terreng & Entreprenør 73, we recommend using the new version 80.
It is unproblematic to go from version 73 to version 80.
Gemini Terreng & Entreprenør 72¶
For projects created in Gemini Terreng & Entreprenør 72, we recommend using the new version 80.
It is unproblematic to go from version 72 to version 80.
Gemini Terreng & Entreprenør 71¶
For projects created in Gemini Terreng & Entreprenør 71, we recommend using the new version 80.
It is unproblematic to go from version 71 to version 80. The road model (SFI) has been extended with annotations but has not received a new version number. This means we can open SFI files from version 80 in version 71, but note that you will lose any annotations.
Gemini Terreng & Entreprenør 65¶
For projects created in Gemini Terreng & Entreprenør 65, we recommend going through version 7 before using the new version 8.0.
Drawings received a new file type when we went from version 65 to version 71, from .bin to .bim. When you open a version 65 project in version 7, you are asked to convert this project. A backup (zip file) of the project is then created in the backup folder before it is converted. A consequence of the file type change is that we must manually open old user-defined title fields and save them again as .bim files.
Gemini road models also have a new version number in version 7. This change occurred when we went from version 65 to version 71. The change was due to a new method (extended) for describing the superstructure using the manual method.
Gemini Terrain & Entreprenør 64m¶
For projects created in Gemini Terrain 64, we recommend completing ongoing projects in the old version. This is because version 64 and version 72 dimension roads according to old and new road standards, respectively. The fact that roads are not dimensioned according to the same rules means you get slightly different results in the two versions.
Gemini Entreprenør 64¶
For projects in Gemini Entreprenør 64, we recommend using the new version on existing projects as well.
Road models in Entreprenør 64 have the same storage structure as in version 80. Although the data content in the file has been somewhat extended, no conversion is necessary (the file has only received a new version number).
Gemini Terrain 64¶
For projects in Gemini Terrain 64, we recommend completing ongoing projects in the old version, especially if you are working with roads. This is due to the new storage structure for road models (SFI), with a new construction engine and new concept for mass types. The new storage structure means that .rfi files must be converted to .sfi files.
Up to and including version 72, road models are automatically converted to the new format (SFI). This generally works well, but some road parameters (for example, topsoil) have been discontinued. Furthermore, we no longer use calculation methods 1: Soil, 2: Rock, 3: Soil over rock, and 4: Mass replacement. The program now calculates masses depending on which physical layers exist in the profiles, meaning: If we have layers for soil, masses for soil excavation are calculated; if we have layers for rock, masses for rock excavation are calculated, etc. Note that we now must have layers for topsoil and mass replacement to calculate these masses. The topsoil parameter has been discontinued. Note that the old .rfi file remains in the project folder.
Note
From version 73 onwards, it is no longer possible to convert old .rfi files directly. We must then go through version 72.