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

Preliminary documentation

Troubleshooting for Orbit HTML5 Web Viewer

The page describes the resource and publication requirement to open and use the Html5 Web Viewer.

Data preparations

All Mapping Runs\Oblique Projects included in a Publications have to be prepared properly and Cloud-ready. This readiness status is indicated in the Catalog, see https://orbitgt.com/kb/3dm_publisher –> Catalog –> Cloud

Troubleshooting

No window pops-up

Browser pop-ups must be enabled for the HTML5 window to pop-up upon publishing or connecting to a publication.
Example: to enable pop-ups on Google Chrome, go to ../chrome/settings/content/popups and “Allow” pop-ups for all websites or add an exception to allow pop-ups from a specific Publisher.

Error message upon login

Displayed message:

{"code": "1020","message": "The cloud metadata entry does not indicate a web compatible run (No file trajectory.ovf available); run file 'run_location\orbit_mm_run.omr' of project 'project_name' of publication 'publication_name' is not web compatible"}

This message error can be caused by:

  • The MM Run is not ready for display in HTML5. The web-compatibility status and reason for incompatibility can be found in Catalog


Displayed message:

Login error: {"code": "1022","message": "Unable to find project file 'project_location\project.ini' of project 'project_name' of publication 'publication_name'"}

This message error can be caused by:

  • Project file has been moved/removed


Displayed message:

Login error: {"code": "1024","message": "Unable to find run '' of project 'project_name' of publication 'publication_name'"}

This message error can be caused by:

Displayed message:

Login error: {"code": "1010","message": "Unable to find dataset file 'WMS.Ortho' of workspace 'admin' of publication 'publication_name'"}

This message error can be caused by:

  • Web services are not yet supported on HTML5.

Displayed message:

Login error: {"code": "1016","message": "Invalid file format: '..\shp_name.shp';Dataset file '..\shp_name.shp' of workspace 'admin' of publication 'publication_name' is not web compatible"}

This message error can be caused by:

  • Only vector files in Orbit formats are supported on HTML5.

Displayed message:

Login error: {"code": "1016","message": "Invalid file format: '..\database_table_name.odb';Dataset file '..\database_table_name.odb' of workspace 'admin' of publication 'publication_name' is not web compatible"}

Submit

This message error can be caused by:

  • Databse data is not yet supported on HTML5.

Submit

Hanging on Loading Data

This can be caused by:

  • No imagery is available in the run

The HTML5 cannot operate if the run doesn't contain imagery.

  • Web Sockets are not enabled

Web Sockets must be enabled on the server machine. See: Wikipediq Web Sockets

Example of error message displayed message in Google Chrome Developer Tools:

app.js?v=18.0.4:1 WebSocket connection to 'ws://localhost:1111/storageWebSocket?Service=StorageWS&StorageSpace=publisher&EMethod=0&EKey=ghKd4oF3lItFmSGiXrJK9Q==' failed: Connection closed before receiving a handshake response

Missalignement between pointcloud and imagery

The Startup Coordinates used to open a publication CRS must be in a projected CRS. Do not use WGS84 as startup coordinate CRS.
If 3DM data is WGS84, use any projected CRS for startup coordinates.
If 3DM data is in any projected CRS, the same projected CRS must be used for startup coordinates.

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