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

System Requirements

Hardware & product specific requirements


Orbit Core, used by Orbit Desktop and Orbit Server, is 100% pure Java. No extra's, just Java. Orbit Desktop and Server run on all platforms that Support Java and provide a Java Runtime Engine.

There are no differences in Orbit functionality on different platforms.
Except some Orbit Resource Drivers are based on third-party libraries. These drivers might not be available on all platforms, see Supported Resources.
Some visuals depend on the platform due to graphical drivers.

Supported Version

Orbit packages Java SE 11 (LTS) with current setups and installers.
Testing and validation to use Java SE 17 (LTS) are not yet completed.

Java Keystore

Special note about Java Keystore and SSL Security Certificates, see SSL Certificate for Java Keystore.

GL rendering by JOGL

Orbit uses JOGL, a Java Binding for the OpenGL API for hardware-supported 3D graphics.

Up to Orbit Release 22.7, a “jogamp_xxx.exe” instance was executed from the user's Temp directory. This could be blocked AppLocker, or alike, as a security infraction and prevent Orbit to start.
From Orbit Release 22.10 the JOGL bindings are installed and launched from the Orbit installation directory to overcome this security issue.

Patch Version 22.7

  1. Download and unzip Update Pacakge
  2. Delete folders “bin” and “software”
    • Delete <Orbit installation directory>/program/bin
    • Delete <Orbit installation directory>/program/software
  3. Copy patch
    • Copy folders <Orbit update package>/program/bin and <update_package>/program/software/
    • Paste into <Orbit installation directory>/program/


The java package called “log4j” has been compromised by hackers, see
Orbit is not using the log4j package in any of its applications.
Orbit is not impacted by this publicly announced vulnerability.


The java framework called “Spring4Shell” has been compromised by hackers.
Orbit is not using the Spring4Shell package in any of its applications.
Orbit is not impacted by this publicly announced vulnerability.


For Orbit 3DM Desktop and Publisher installation is guaranteed on:

  • Desktop: 7 (not for the Connect Edition), 8, 10, and 11.
  • Server: 2003, 2003 (R2), 2008 (R2), 2012 (R2), 2016, 2019, 2019(R2) and 2022


On Windows, the Java Runtime Engine used by Orbit is included in the Orbit installation.
Java doesn't need to be installed or updated. An existing Java installation won't generate conflicts with Orbit's JRE and visa versa.

Orbit Desktop Standalone

From Orbit version 11.01) application license, settings, and data are stored within the Windows User Application Data directory. Consequently, each Operating System user will need to activate Orbit and will manage its own data and preferences.


For Orbit 3DM Publisher only.


The Orbit team provides and test “Orbit 3DM Publisher” for the current Ubuntu Long Term Support (LTS) release, see Ubuntu Releases.

Each Linux distribution has its own characteristics, we tested and advise Ubuntu.
However, as a Linux expert, you are able to tune the configuration to run on your preferred distribution.

More information on Orbit for Ubunto, see Orbit 3DM Publisher on Ubuntu.


The Orbit 3DM Publisher Server doesn't require a graphical user interface. The Orbit 3DM Import Tool is available standalone and on Windows only.


The Orbit 3DM Publisher requires a Java runtime (11 or higher) to be available on the system as the default java version.


Orbit Geospatial Technologies is committed to international and interprofessional standards.

  • Most commonly used spatial data storage formats are supported, see Supported Resources.
  • Only standard Java is used.
  • Orbit Publisher services pure OGC WFS and WMS Web services.
  • Orbit Publisher uses standard Http/Https, Wd/Wss, XML and Jason communication.
Orbit Desktop Standalone on Windows, remark for older versions < 11.0 : Orbit Desktop products on Windows.
Last modified:: 2023/05/12 16:31