This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.
For documentation on the current version, please check Knowledge Base.
Process Imagery
The administration procedure “Process Imagery” allows the Orbit administrator
to process the original images to more efficient multiresolution images for faster viewing performances. 1)
Processing images is optional.
It is advised when using high resolution images or for web viewing (low bandwidth connection).
Processing images is optional.
It is advised when using high resolution images or for web viewing (low bandwidth connection).
Advantages of Processed Images
CPU for Publishing
Standard images (jpg, tiff, png, … ) require much more CPU to be charged and displayed via an Orbit Publisher.
The complete images needs to be read and corrected for pan, tilt and roll before serving to one of the publishing clients.
This will cause server performance issues if the server does not meet the minimum server requirements.
Also for a desktop client processing the images will reduce the time required to correct the images before displaying.
Data streaming
Standard images need to be loaded completely in full resolution for viewing.
A processed image will be loaded on a very intelligent and efficient way which will reduce strongly the volume of data that needs to be transferred and time for displaying on a Publishing client.
Also for a desktop client processing the images will reduce the data transfer and the time for lading the images.
Start Processing
Open run
Open the mobile mapping run you wish to process.
Procedures > Administration > Mobile Mapping > Open Run
Process Imagery
Open the procedure Process Imagery.
Procedures > Administration > Mobile Mapping > Process Imagery
Start
On clicking start all images of the current opened run will be processed.
This action can be cancelled any time and restarted later if required. Already processed images will not be removed and will be used for viewing.
Processing Time
The processing time depends on the :
- computing power of the machine
- data storage and file access
- size and resolution of images
Example image processing 1423 images/87 minutes, 981 images/hour, 16.4 images/minute
- 64bit, Quad core, 4GB memory, Intel core i7
- read and write on external USB3 connected hard disk
- original images : 5.93GB, average size of 4.27MB/image, 8000×4000 pixels
- processed images : 12.9GB, average size of 9.28MB/image
Example image processing 862 images/50 minutes, 1034 images/hour, 17.3 images/minute
- 64bit, Quad core, 4GB memory, Intel core i7
- read and write on external USB3 connected hard disk
- original images : 2.77GB, average size of 3.29MB/image, 8000×4000 pixels
- processed images : 5.16GB, average size of 6.13MB/image
Disk Storage
The processed images will be created in the “processed” sub-directory of the Orbit run :
- <Orbit Run directory>\panorama1\processed\
- <Orbit Run directory>\planar1\processed\
The files are not optimized for disk storage but for viewing performance. Depending the image compression of the original images the size of the processed image will vary between the original size (uncompressed original images) and twice the original size (compressed original images).
Ensure the required disk-space is available.
1)
Process Imagery is possible for all Orbit runs imported from Orbit version 10.5 or later. Orbit runs from Orbit version 10.4 or earlier cannot be used.
Last modified:: 2019/03/25 11:36