Knowledge Base
Recent Changes

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
Next revision Both sides next revision
dev:desktop_ext:catalog [2019/03/25 11:36]
127.0.0.1 external edit 		dev:desktop_ext:catalog [2020/04/23 14:07]
reine
Line 8: Line 8:
 **Cloud Upload Tool** \\ **Cloud Upload Tool** \\
 {{orbitgis:how_to_find.png?25&nolink |}} Top Toolbar > Catalog {{orbitgis:how_to_find.png?25&nolink |}} Top Toolbar > Catalog
 +
 ===== Concepts ===== ===== Concepts =====
  
Line 77: Line 78:
   * Use the search box to filter on any available field. The restriction will be applied on <Enter>.   * Use the search box to filter on any available field. The restriction will be applied on <Enter>.
   * Double click a table header name to sort.   * Double click a table header name to sort.
-  * Use the "Archived Runs" check box to display archived runs.  +  * Use the "Archived Runs" checkbox to display archived runs.  
-  * Right click a single selected run record or multiple selected records to open the Catalog Context Menu. +  * Right-click a single selected run record or multiple selected records to open the Catalog Context Menu. 
  
 === Open and view resource === === Open and view resource ===
Line 85: Line 86:
   * Double click a table record to highlight and zoom to the extents of the mobile mapping resource.    * Double click a table record to highlight and zoom to the extents of the mobile mapping resource. 
   * Change the color presentation on Map 2D with a single click on the color field. Note if a resource is selected in the catalog table, the [[dev:desktop:preferences:selection|selection preference]] focus color will be used.   * Change the color presentation on Map 2D with a single click on the color field. Note if a resource is selected in the catalog table, the [[dev:desktop:preferences:selection|selection preference]] focus color will be used.
-  * Open a selected Run or Project via the Catalog Context Menu or via the according button in the Catalog View Sidebar \\ The currently opened Run or Project is displayed in bold. \\ Contrary to open run or open project via procedures, the map will not zoom to the extents of the opened mobile mapping resource and, if available, trajectory information will be displayed immediately on the Map 2D. These two small differences make it possible to verify or compare the accuracy of multiple runs at the same location. Subsequently segments can be adjusted or removed directly. +  * Open a selected Run or Project via the Catalog Context Menu or via the according button in the Catalog View Sidebar \\ The currently opened Run or Project is displayed in bold. \\ Contrary to open run or open project via procedures, the map will not zoom to the extents of the opened mobile mapping resource and, if available, trajectory information will be displayed immediately on the Map 2D. These two small differences make it possible to verify or compare the accuracy of multiple runs at the same location. Subsequently, segments can be adjusted or removed directly. 
  
 ==== Table information ==== ==== Table information ====
Line 97: Line 98:
 The status of your mobile mapping run is displayed by the status indicator : The status of your mobile mapping run is displayed by the status indicator :
  
-  * Imported, Added (yellow) : a processed Orbit run has been added or raw data is imported. +  * Imported, Added (yellow): a processed Orbit run has been added or raw data is imported. 
   * In process (red): run contains adjustments that aren't consolidated.    * In process (red): run contains adjustments that aren't consolidated. 
   * Processed (grey): run was processed.   * Processed (grey): run was processed.
   * Delivered (blue): run was delivered.   * Delivered (blue): run was delivered.
-  * Exported (green) : run is an exported segment.+  * Exported (green): run is an exported segment. 
 + 
 +=== Numbers === 
 + 
 +Trajectory: Length of the complete trajectory 
 +Panoramas#, Planars#: Number of photo positions / Number of Original Images / Number of Processed Images \\ 
 +Paronamas%, Planars%: Percentage Original images / Percentage of Processed Images - compared to photo positions 
 +Point cloud: number of lidar points in the run, in millions \\ 
 +Total Size: the size of data on disk, in gigabytes
  
 === HTML5 & Cloud === === HTML5 & Cloud ===
  
-To check if Mapping Runs\Oblique Projects are HTML5 and Cloud ready select Run\Project in the Catalog and with right click "Calculate data volume" first and then "Calculate image availability".+To check if Mapping Runs\Oblique Projects are HTML5 and Cloud-ready select Run\Project in the Catalog and with right-click "Calculate data volume" first and then "Calculate image availability".
  
 "Calculate data volume" checks if all the folders of the run have the expected amount of files in them. The amounts of image files are displayed in the catalog table. "Calculate data volume" checks if all the folders of the run have the expected amount of files in them. The amounts of image files are displayed in the catalog table.
Line 111: Line 120:
 "Calculate image availability" checks if the photo positions that are listed in the photo position file match the images in the run. If there is a mismatch, than one or more new files are created in the metadata folder of the run in which the mismatches are listed. "Calculate image availability" checks if the photo positions that are listed in the photo position file match the images in the run. If there is a mismatch, than one or more new files are created in the metadata folder of the run in which the mismatches are listed.
  
-Icon indicating a Mapping Run is ready to upload to the [[1814:desktop_ext:3d_mapping_cloud_upload|3D Mapping Cloud]].+Icon indicating a Mapping Run is ready to upload to the [[1814:desktop_ext:3d_mapping_cloud_upload|3DM Cloud]].
  
   * Red: not ready for upload. \\   * Red: not ready for upload. \\
Line 119: Line 128:
 A tool-tip indicates the reason why the Mapping Run is not ready to upload. A tool-tip indicates the reason why the Mapping Run is not ready to upload.
 Reasons might be :  Reasons might be : 
-    * Images are not optimized into processed images. +    * Images are not optimized into processed images, see [[dev:desktop_ext:mapping:manage:imagery|]] 
-    * Number of processes images is less than number of photo positions. For each photo positions of the Mapping Run the corresponding optimized image must be available.+    * Number of processed images is less than the number of photo positions. For each photo position of the Mapping Run the corresponding optimized image must be available.
     * Resource directory (point cloud, panorama, planar, trajectory) is available but the data is not yet imported. Delete resource directory if the according resource not exists.      * Resource directory (point cloud, panorama, planar, trajectory) is available but the data is not yet imported. Delete resource directory if the according resource not exists. 
  
 After resolving indicated by tool-tip issues, 'Calculate data volume' and 'Calculate image availability' again to check the HTML5 and Cloud-readiness status. After resolving indicated by tool-tip issues, 'Calculate data volume' and 'Calculate image availability' again to check the HTML5 and Cloud-readiness status.
  
-The Cloud-readiness status also indicates if the Mapping Run/Oblique Project can be used for publication in HTML5 Web Viewer and vice versa (naming will depended of the Orbit installed version). The Mapping Run/Oblique Project can not be published in HTML5 if the indicator is red. +The Cloud-readiness status also indicates if the Mapping Run/Oblique Project can be used for publication in HTML5 Web Viewer and vice versa (naming will depend of the Orbit installed version). The Mapping Run/Oblique Project can not be published in HTML5 if the indicator is red.
- +
-<note tip>(especially for the Topcon IPS-2 users)HTML5 indicator is red and popping up hint: "No file trajectory.ovf available". When trying to publish\share a Run created with one of the older templates, please check if there is a folder processed inside trajectory folder. In this case move files trajectory1.ovf and trajectory1.ord one folder up, remove folder processed and rename trajectory1 to trajectory. </note> +
- +
-=== Numbers ===+
  
-Panorama, planars : total number of images included in the run \\ +<note tip>(especially for the Topcon IPS-2 users)HTML5 indicator is red and popping up hint: "No file trajectory.ovf available". When trying to publish\share a Run created with one of the older templates, please check if there is a folder processed inside the trajectory folder. In this case move files trajectory1.ovf and trajectory1.ord one folder up, remove folder processed and rename trajectory1 to trajectory. </note>
-Point cloud : number of lidar points in the run, in millions \\ +
-Total Size : size of data on the disk, in gigabytes+
  
 ==== Context menu ==== ==== Context menu ====
 
Last modified:: 2023/11/14 10:51