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

Local vs EOS resources

The Orbit software has several ways to import GIS resources. The manner in which you import the data will determine the restrictions and permissions you have in order to edit or manage the resources:

  • Local resources
  • Resources managed by EOS (Enterprise Orbit Service)

Local Resources

Orbit GIS and Orbit Client both support the import of local data by drag and drop.
Orbit GIS allows you to create new datasets and open resources using the Resource Library. (These 2 functions are disabled in Orbit Client)

These functions above describe how a local datasets can be imported in Orbit.
The local datasets will have full access to all functions in the Context Menu

EOS Resources

EOS Resources are GIS resources that are managed on server-side. You can add, manage or delete them using the EOS Console.
The advantage of an EOS resource is they can be used and edited by more than one user at the same time.
Also they are restricted by user permissions. Administrators can determine the permissions of each user for each dataset in the EOS Console.

Orbit desktop products can connect to the EOS in Orbit depending on which software you are using:

  • Orbit GIS: Use the Resource Library to import EOS resources
  • Orbit Client: EOS resources are bundled into workspaces. Enter your user and pasword to see which workspace are available for user. Starting Orbit Client will give you a predetermined set of EOS Resources. It is not enabled to remove an EOS resource in Orbit Client.

EOS Resources are restricted to use the following functions of the Context Menu:

  • Join Tables…
  • Labels…
  • Legend Editor…
  • Charts Editor…
  • Dataset Structure…
  • View Metadata…
  • Save Dataset to…
  • Export Dataset to…
Last modified:: 2023/01/09 12:48