Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:desktop_ext:blur_registration [2018/06/26 09:30]
127.0.0.1 external edit
dev:desktop_ext:blur_registration [2023/01/18 20:55]
jeroen removed
Line 4: Line 4:
 {{orbitgis:how_to_find.png?25&nolink|}} [[dev:desktop:workspace:main_toolbar|Main Toolbar]] > Extensions > Blur Registration {{orbitgis:how_to_find.png?25&nolink|}} [[dev:desktop:workspace:main_toolbar|Main Toolbar]] > Extensions > Blur Registration
  
-This page describes how use the extension "Blur Registration" in the Orbit desktop.+This page describes how to use the extension "Blur Registration" in the Orbit 3DM Blur and Erase Production.
  
-As the name says, "Blur Registration" extension makes it possible to blur or to erase parts of the imagery, in order to hide unwanted elements. It can be used to hide car plate numbers or people faces. The extension is designed to allow very fast processing. For example, in an optimal environment, it is possible to process around 600 images per hour.+As the name says, "Blur Registration" extension makes it possible to blur or to erase parts of an image, in order to hide unwanted elements. It can be used to hide car plate numbers or people faces. The extension is designed to allow very fast processing. For example, in an optimal environment, it is possible to process around 600 images per hour.
  
-The Orbit desktop product Blur and Erase Production does not include the administration procedure "Import Run". In order to be able to blur and erase imagery, the user must have a run previously imported or created by another Orbit product. +The Orbit desktop product Blur and Erase Production does not include the administration procedure "Import Run". In order to be able to blur and erase imagery, the user must have a run previously imported or created by another Orbit product and add it via the Blur Registration extension
  
 ==== Concepts ==== ==== Concepts ====
- 
  
 **Blur**\\ **Blur**\\
-Make a part or several parts of an image indistinct, unclear and hazy by reducing the edge content and making the transition form one color to the other very smooth.+Make one or several parts of an image indistinct, unclear and hazy by reducing the edge content and making the transition from one color to another very smooth.
  
 **Erase**\\ **Erase**\\
Line 20: Line 19:
  
 **Files & folders**\\ **Files & folders**\\
-As result of using the extension, .xml files containing the definition of the blurred areas are created. These files are saved in the same location as the input imagery. +As result, .xml files containing the definition of the blurred areas are created. These files are saved in the same location as the input imagery. 
  
 ==== Sidebar ==== ==== Sidebar ====
Line 29: Line 28:
  
 **Start**\\ **Start**\\
-Srart the procedure, starting with the first image. Simply find the locations to blurand create the blurring areas by pointing the cursor to the desired locations.+Start the procedure. By default, the first available image will be opened. Simply find the locations to blur and create the blurring areas by hovering the mouse cursor to the desired locations.
  
 **Search Box**\\ **Search Box**\\
-Search for a particular image, by using the name or a part of the name, inside the opened run folder structure. The result of the search will be displayed on the Map.+Search for a particular image, by using the name or a part of the name, inside the opened run folder structure. The result of the search will be displayed on Blur Registration Tab.
  
 **Navigation Tools**\\ **Navigation Tools**\\
Line 59: Line 58:
  
 <note tip> <note tip>
-The .xml files can be physically written on the images using the [[dev:desktop_ext:blur_erase|Blur&Erase QC]] tool, or using the procedure [[dev:desktop_ext:mobile_mapping:manage:imagery|Optimize Imagery]] +The .xml files can be physically written on the images using the [[dev:desktop_ext:blur_erase|Blur&Erase QC]] tool, or using the procedure [[dev:desktop_ext:mapping:manage:imagery|Optimize Imagery]] 
 </note> </note>