Optimize Imagery of Mapping Run

This page describes the desktop procedure “Optimize Imagery”¹⁾ for Mobile Mapping.

1. Open run
2. Procedures > Administration > Mobile Mapping > Process Imagery

The procedure “Optimize Imagery” makes it possible to :

• Optimize all Original Images of the Opened Run into Processed Images.
• Create for each group of Planar Images of the Opened Run a single Spherical Reference Image.

Recommendation
Use of Processed Images improves performance.

• Advised for desktop use if the image resolution is less then 32MP.
• Highly recommended for desktop use if the image resolution is more then 32 MP.
• Highly recommended at all time for Publisher and Flash WebClient.
• Mandatory for Publisher and Html5 WebClient.

Advantages
Use of Processed Images has following advantages :

• Significant reduced CPU requirement for Publisher Server.
• Almost instant transfer and display of a low resolution Fast transfer and display of low and high resolution Image for Publisher WebClients.
• More efficient transfer and display of full resolution Image for Publisher WebClients.

However jpg quality can be set to apply compression and reduce file size, Processed Images are not optimized to reduce file size. If the same jpg quality is used for both Original and Processed Images, then the file size will increase by ~30%.
If a Processed Image is available, the Original Image is no longer used and can be deleted.

Requirements
Optimize Imagery requires :

• An Original Run of Version 2 as used since Orbit 10.5, see Orbit Run Versions & Structure.
• Local file access to Original Images. Remote Original Images cannot be used. Use of link.ini image reference file is supported.

Advantages
A Spherical Reference Image combines the ease of use of a Spherical Images and the accuracy of a Planar Images.
One can easily navigate from one Planar Image Group to another nearby recording position and open one of the available high resolution and accurate Planar Images.

Requirements
Create Spherical Reference Image requires :

• An Original Run of Version 3 as used since Orbit 11.0, see Orbit Run Versions & Structure.
• Local file access to Original Images.
• Planar Image Group Identifier for each recording position, stored in photo position “OrbitPhotoGroupId” attribute.
• Import Template addon “panorama_planargroups”.
  Provide an Orbit Mapping Run to Orbit Support to receive the required template addon.

Optimize all Original Images of the Opened Run into Processed Images.

Set jpg compression quality for the processed images.

Select one of the preset values or use “Custom” to set any quality value via the slider below.
Higher quality will increase the file size and the corresponding time to load the image.
There is no point to process the images with a higher quality than the original image files. For most use cases jpg quality 80 “Good” will be ok.
More information about the effect of jpg quality and compression : https://en.wikipedia.org/wiki/JPEG.

Set image size in pixels.

the software automatically detects the size of the original images.It is advised to keep the original settings, only if you have huge images(over 10000×5000)it is reasonable to downsize them. The ratio should always be kept as it is.

Set mask to hide unwanted structures.

Optionally select a mask file to be applied on top of the original images to hide e.g. GPS antenna while processing the optimized images.
A mask file is a *.png file having exactly the same resolution as the original images. Its color and transparency are taken into account while processing.

Set option to apply blurred and erased registered areas.

Optionally activate blurring to be applied on top of the processed images.
Blur and erase areas can be registered using the Orbit extension Blur and Erase extension, see www.orbitgt.com/content/mobile-mapping.

Delegate job to Task Manager or start processing now.

CPU and Memory requirements
Optimize image process is multi-threaded and uses all available CPU and Memory resources. This process reduces your computer performance and affects/is affected by other running processes.
We strongly recommend to isolate this process, for example running over night, to avoid any cpu or memory issues.

Stop and Restart Processing
All images of the currently opened run will be processed.
This process can be interrupted at all time. Already Processed Images are retained and this job can be restarted to process remaining Original Images at all time.
To re-process already Processed Images the appropriated Processed Images need to be removed from the Orbit Run :
<Orbit Run>/<camera>/processed

Processing Time
Some stats and facts of processing images

Example image processing 123,787 images/ 59 hours 27 minutes, 2082 images/hour, 34.7 images/minute

• 64bit, Quad core, 16GB memory, Intel core i7
• read from external USB3 connected hard disk
• write to internal SSD drive
• original images : 8000×4000 pixels, jpg quality 80, average size of 4.25 MB/image,
• processed images : same resolution and quality, average size of 5.31 MB/image

Create for each group of Planar Images of the Opened Run a single Spherical Reference Image.

If the above described requirements are fulfilled the second procedure step “Create” will be added automatically.

Delegate job to Task Manager or start processing now.
At the moment do not cancel or interrupt the process.