| Both sides previous 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/03/20 11:09]
reine [Tab] |
| "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. \\ |
| Reasons might be : | Reasons might be : |
| * Images are not optimized into processed images. | * Images are not optimized into processed images. |
| * 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> | <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> |
| |
| === Numbers === | === Numbers === |