Description
Orbit 3DM is a specialist software suite for managing, extracting and sharing 3D data from digital mapping developed by Bentley Systems. The software supports a wide range of data such as point clouds, images, textured meshes and GIS data, and offers unique features for managing and analyzing this data. East. The mentioned information sources are used to build digital twins and model real-world phenomena. This software supports all data collection and storage systems and there is no limit to the volume and amount of information input to the system. This tool is very flexible and supports various mapping systems such as ground systems, mobile mapping, drone mapping systems, oblique mapping, aerial mapping and….
Perform complex information calculations, analyze and extract data from maps for engineering and urban planning purposes, etc. are among the most important applications of this software. All data in the software can be converted into graphics maps and the user can create a highly realistic 360 degree map of raw data within minutes. This software is used in various fields and industries, and among its most important regular users are engineers, geographers, urban and industrial infrastructure operators and developers, etc.
3DM Orbit Features,
- Quick and easy management of 3D map data
- Processing of cartographic data
- Build the final 360-degree map based on the processed information
- Share raw and processed data
- Perform modeling operations
- Receive, store and optimize data received from various sources
- Full support for various mapping systems such as aerial, terrestrial and…
- Cataloging and archiving 3D map data
- Eliminate noise, moving objects and paths in cloudy point maps
- Optimize and improve the positioning of various elements in three-dimensional maps
- Optimize cloud point data for improved performance and fast, low-cost storage
- Processing and coloring cloud point data to share across different platforms
- Analyze cartographic data and produce standard reports
- Automatic detection of posts, geographic directions and traffic signs
- Automatic detection of bumps, smooth surfaces, corners, etc.
- Navigation and navigation between map and map data in two-dimensional and three-dimensional modes
Required configuration
Operating system
To learn more about system requirements for Windows, Linux, and Java, see Required configuration,
Orbit 3DM desktop product: Windows only.
Computing power
Depending on your expectations, the type and volume of resources used (e.g. point cloud, imagery, base maps, etc.).
Here is a guideline:
- Minimum: 64-bit operating system, 4 GB RAM, dual-core processor(s)
- Recommended: 64-bit operating system, 8 GB RAM or more, Quad-core processor
software
Next to Java, no special requirements.
Graphic card
Orbit desktop products use the Java Execution Engine (JRE) and CPU to process graphics requests.
Orbit desktop products will use the 3D graphics card (GPU) to render complex 3D graphics, for example 3D tin models.
If no 3D graphics card is available, complex 3D queries will be processed by Java Runtime using the CPU.
Virtual environments (like Citrix, Virtualbox, VMWare, etc.) still struggle to integrate movies, the use of high-resolution animated images, and complex 3D graphics. The result may be that desktop and web clients act more slowly or fail to render the 3D scene.
For example, smooth viewing and roaming through high-resolution spherical images or free navigation in a 3D point cloud requires an adequate image refresh rate. These actions can be compared to watching an HD movie.
When using Citrix, we recommend XenApp, including video optimization and a 1 GB network connection.
Internet connectivity
Standalone Orbit Desktop products require online connectivity.
Orbit desktop clients do not require online access but do require connectivity with their Orbit server, see Orbit Server Requirements.
disk space
No special requirements for installing Orbit software. A new installation is around 300 MB.
Greater attention is needed to organize the enormous volume of map resources.
File storage and access
storage
Orbit requires a file-based storage system. This can be a local or network storage system that supports direct file access.
When importing, Orbit will process all mapping data into performance-optimized resource files, which may require slightly more storage capacity. Optimized storage reduces other hardware requirements.
Access to files and disks
Orbit queries result in direct access to files, performance is particularly determined by disk speed and disk access.
Slow disks or slow connections will create a bottleneck. SSDs are nice to have.
large files
When processing large map data sets, your file system must be capable of storing large files. Processing errors may occur due to (1) not enough disk space to complete, (2) file system size limitation (FAT32 is limited to 4 GB, NTFS is recommended), and (3) extreme fragmentation of storage volume.
Single operator
For standalone systems or other small setups, you may want to store data on external drives.
Using high-speed interfaces like eSATA or USB3 is highly recommended.
Multi operator
For larger data volumes, we recommend using an optimized central storage system (e.g. server-side RAID systems) consistent with the data volume and expected number of users. Make a wise decision, the slowest link will define the speed of use. This may be your network and not data storage.
Note that you can host the mapping data on hardware other than the Orbit desktop installation. As long as there is a fast connection (1GB or more) between the two, this won’t be a problem.
Configuration example
- Visualization Objectives:
- 64-bit, dual core, Intel i5 processor or equivalent, 4 GB of memory, 2 USB3 connections.
- Purposes of processing:
- 64-bit, quad core, Intel i7 or equivalent, 8 GB RAM or more, 1 TB hard drive, 2 USB 3 or more connections.
- Intensive treatment goals:
- 64-bit, quad core or more, Intel i9 or equivalent, 16 or 32 GB of RAM, 1 TB SSD, 4 USB 3 or more connections.
Pictures
buy
For all questions Contact us
size
313 MB