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

Process Imagery

This page describes how to use the desktop mobile mapping administrator procedure “Process Imagery”and the advantages of processed images.

The Oblique administration procedure “Process Imagery” allows the Orbit administrator to process all original images of the opened Project into optimized native Orbit multi-resolution images to improve performances.

  1. Open Project
  2. Procedures > Administration > Oblique > Process Imagery
Processing images is optional. However, it is advised when using high resolution images or for web viewing.

How to use

Quality

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


Advantages of Processed Images

CPU for Publishing

Original images (jpg, tiff, png, … ) require much more CPU to be loaded and displayed both for Publisher and Web client. This results in higher server requirements to avoid server performance issues.
Processed images do not require some of the time and CPU consuming processes.

Also for an Orbit desktop, processing the images will reduce the time required to display the image.

Data streaming

Original images must be loaded completely in full resolution before they can be displayed by a client.
Processed images are loaded in an intelligent, more efficient way which reduces strongly the volume of data (and according time) to be transferred.

Also for an Orbit desktop, processing the images will reduce the data transfer.

Low resolution preview

Original images must be loaded with a single full resolution request to be displayed.
Processed images include a low resolution image for instant response on client side.


Processing Time

The time required for processing the images depends :

  • 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

Processed images are stored in the “processed” sub-directory of the Orbit project :

  • <Orbit Project directory>\planar1\processed\

Processed images 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 (strong compressed original images).

Ensure the required disk-space is available.

 
Last modified:: 2019/03/25 11:36