This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.

Manage Mobile Mapping in Client-Server

This documentation is only relevant when using Orbit Mobile Mapping in Client Server.

Mobile Mapping Runs and Projects

It is recommended to read first the Orbit concepts of mobile mapping data : Orbit Mapping Resource.

Data sharing

In an Orbit Client Server setup special attention is required for data management, storage, file access, system file permissions and network connectivity.
Technical information can be reviewed here : Requirements for Orbit 3DM Publisher.

Server access
To make your runs and projects available for the Orbit EOS service use of UNC syntax is required. An Operating System service cannot use mapped network drives.
Consequently the Orbit EOS Service installed and started as an Operating System Service cannot access data via a mapped network drive. Don't get confused, as Orbit Desktop products or the Orbit EOS Service running in Console are able to use mapped network drives.

Client access
We do advise to import and process data on a local drive to avoid any network traffic while processing. Once imported, the data can be moved to a shared network storage.
Two options :

  • Direct file access
    If the Orbit desktop client has direct file access to runs and projects, all files will be read directly from disk by the Orbit client. This results in more network traffic, reduces server load and enables full point cloud 3D viewing on client side.
    Any application running within the OS user interface has access to mapped network drives.
  • No file access
    If the orbit desktop client has no access to runs and projects, the Orbit service will read the resources from disk and transfer them via the Orbit DOX protocol to the Orbit Client. This results in less network traffic, increases server load and disables full point cloud 3D viewing on client side.

Mobile Mapping Extension

Roles on Extension

The roles on extensions are managed in the EOS Console.
When opening a workspace in the Orbit Client the extension roles for user and workspace will be loaded.

With this role, Mobile Mapping data can be viewed, modified, deleted, imported and exported.
Access to procedures Administration > Mobile Mapping and Mobile Mapping > Open Project. (Both Mobile Mapping Runs and Mobile Mapping Projects).

Operator and User
With this roles, Mobile Mapping data can be viewed only.
Access to procedure Mobile Mapping > Open Project. (Mobile Mapping Projects only)

Last modified:: 2023/05/12 16:31