To be able to use a fully configured NET Engineering project in NET Cloud, it must first be exported from NET Engineering to a GeoServer and then imported into NET Cloud.
This saves a lot of time when setting up the NET Cloud project, but still requires some configuration work, as not all options from NET Engineering can be transferred.
Work steps for creating the export file
| Work step | Note | |
1 | Open your industry model in Map3D. | Attention: Administrator rights on the industry model are required. Normal users unfortunately do not have access to the export. In addition, the module “TKI NET Mobile Base Data Model” must be activated. |
2 | Select your desired display model and create the graphic. | On the right-hand side in the display management, the layers to be published can now be activated. Layers that are not checked will not be published. We are happy to provide you with a standard NET Cloud display model. |
| 3 | By right-clicking on the industry model, a new entry “NET Cloud: Publish layers to GeoServer” appears. | |
| 4 | A new dialog opens. Please enter the connection data for your GeoServer there and connect to it. A test request is sent using the specified access data. Any warnings can be found in the log file. | The two most common problems are: Warning: The remote server could not be resolved. Solution: Check the URL for typos. Also check whether the GeoServer is reachable from the computer on which Map3D is currently running. Adjust the proxy settings if necessary. Warning: The remote server returned an error. Solution: Check the username and password. Does the user have write permissions on the GeoServer? |
| 5 | Specify a new workspace to create a new workspace and data store, or select an existing workspace to extend it with additional layers. | The checkbox “consider linked layers” makes it possible to publish the domain tables as well. For example, if the data model is configured so that the route knows its surface type, the table for surface types is also published, even if it is not displayed in the display management. |
| 6 | After pressing the “Publish” button, information about the successfully published layers and styles appears in the log window. These are immediately available in the GeoServer. At the end of the process, a dialog window opens to save the ZIP configuration file. This file is required to upload the project into NET Cloud. | The file can be created again via “Publish”. |
| 7 | Navigate to the projects in NET Cloud using your browser. On the right side you will find the “Import” button, which can be used to upload the ZIP configuration file. Depending on the project size, this may take 1–5 minutes. | Be sure to ensure that the specified “Workspace” for the import is identical to the “Workspace” on the GeoServer. This cannot be changed later. |
| 8 | The project should now be fully configured. To reload all styles, you can optionally run Problems → “Repair all SLD styles”. Please check whether all layers are present and have the correct geometries (point, line, polygon). |