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
dev:server:publishers:viewer_data_preparation [2019/05/24 09:49]
nathalie.moerman@orbitgt.com 		dev:server:publishers:viewer_data_preparation [2023/01/31 19:09]
jeroen removed
Line 1: Line 1:
 ====== Data Preparation and Organization for Orbit 3DM Publisher Viewer ====== ====== Data Preparation and Organization for Orbit 3DM Publisher Viewer ======
-This page describes the best recommended practices in data preparation and organization to achieve consistently reliable high performance when Publishing big amount of data.+This page describes the best-recommended practices in data preparation and organization to achieve consistently reliable high performance when Publishing a big amount of data.
  
 ===== Concepts ===== ===== Concepts =====
-Orbit 3DM Publisher Viewer processes most requests on the end-user side, not on the Publishing server. Unlike previous generation of Orbit Viewer: Flash Viewer, HTML5 Viewer relies on data being optimized for streaming which means:+Orbit 3DM Publisher Viewer processes most requests on the end-user side, not on the Publishing server. Unlike the previous generation of Orbit Viewer: Flash Viewer, HTML5 Viewer relies on data being optimized for streaming which means:
   * All data, except for 3D Mesh (see below), should be in native Orbit formats.   * All data, except for 3D Mesh (see below), should be in native Orbit formats.
-  * The performance is affected drastically by amount of resources, not their size - recommended maximum number of Runs in one Publication is not more than 20. +  * The performance is affected drastically by the amount of resources, not their size - the recommended maximum number of Runs in one Publication is not more than 20. 
-  * WM(T)S should be accessed with special Orbit Tile Map (otm) driver. +  * WM(T)S should be accessed with a special Orbit Tile Map (.otm) driver. 
-  * If a Publication contains at least one Resource not complaint with mandatory requirements, it will not open.+  * If a Publication contains at least one Resource not compliant with mandatory requirements, it will not open.
  
 ===== Mobile Mapping\UAS\Oblique data ===== ===== Mobile Mapping\UAS\Oblique data =====
  
 ==== Mandatory ==== ==== Mandatory ====
-To publish mobile mapping resources, data must be imported as Runs and organized into Projects. \\ +To publish mobile mapping resources, data must be imported as Runs. \\ 
-It is possible to use Orbit 3DM Publisher Catalog on server to Import Runs. However it is highly recommended to have a dedicated Content Manager license and run data processing (Import and Merging Runs) on a separate machine with all resources being processed locally. All Mapping Runs\Oblique Projects included in a Publication have to be HTML5-ready, see [[dev:desktop_ext:catalog|]] > Cloud & HTML5. \\+It is possible to use Orbit 3DM Publisher Catalog on the server to Import Runs. However, it is highly recommended to have a dedicated Content Manager license and run data processing (Import and Merging Runs) on a separate machine with all resources being processed locally. All Mapping Runs\Oblique Projects included in a Publication have to be HTML5-ready, see [[dev:desktop_ext:catalog|]] > Cloud & HTML5. \\
  
 **Workflow:** **Workflow:**
   - Import and process your data into mobile mapping runs using the "Import Run" procedure, see [[dev:desktop_ext:mapping:manage:runs|]].   - Import and process your data into mobile mapping runs using the "Import Run" procedure, see [[dev:desktop_ext:mapping:manage:runs|]].
   - [[dev:desktop_ext:mapping:manage:imagery|]].   - [[dev:desktop_ext:mapping:manage:imagery|]].
-  - Organize Runs into Projects using 3DM Orbit Publisher Catalog, see [[dev:desktop_ext:mapping:manage:projects|]]. +  - Manage the runs in the 3DM console, see [[dev:server:publisher_console:resources|]].
-  - Manage projects in EOS console, see [[dev:server:console:extensions|]].+
  
 ==== Recommended ==== ==== Recommended ====
Line 35: Line 34:
   * All vector layers should be converted to Orbit native formats. Use [[dev:desktop:tools:convert_data|]] or [[dev:desktop:tools:optimize_data|]] tools to convert supported vector formats into *.ovf or *.ovt.   * All vector layers should be converted to Orbit native formats. Use [[dev:desktop:tools:convert_data|]] or [[dev:desktop:tools:optimize_data|]] tools to convert supported vector formats into *.ovf or *.ovt.
   * Every vector layer must have [[dev:technology:supported_formats:other:olg|]] (*.olg) and [[dev:technology:supported_formats:other:ord|]] (*.ord) files accompanying it.   * Every vector layer must have [[dev:technology:supported_formats:other:olg|]] (*.olg) and [[dev:technology:supported_formats:other:ord|]] (*.ord) files accompanying it.
-  * Vector layers of Point type must have [[dev:desktop:dataset:legend:parameters:symbol_library]] (*.osl) file accompanying it. The easiest way to create *.osl file is: +  * Vector layers of Point type must have [[dev:desktop:dataset:legend:parameters:symbol_library]] (*.osl) file accompanying it. The easiest way to create *.osl file is to open the file in Orbit, go to the legend editor and press save. \\ Following the below steps will also allow you to retreive the .osl file. 
-    - Copy the .osl file corresponding to the legend specified in *.olg file (can be checked in Legend editor) from ..\server\program\symbols.+    - Open .olg file and search for the parameter 'Symbol.Library'. 
 +    - Copy the .osl file corresponding to the value of that parameter from ..\server\program\symbols in the installation folder.
     - Paste it next to the .ovf file.     - Paste it next to the .ovf file.
     - Rename it to the same name as the vector file.     - Rename it to the same name as the vector file.
Line 42: Line 42:
 **Workflow:** **Workflow:**
   - Import and convert the vector files in an Orbit desktop product.   - Import and convert the vector files in an Orbit desktop product.
-  - Manage vector files in EOS console, see [[dev:server:console:resources:datasets|]].+  - Manage vector files in the 3DM console, see [[dev:server:publisher_console:resources|]].
  
 ==== Recommended ==== ==== Recommended ====
-  * Remove all unnecessary attributes from vector files.+  * Remove all unnecessary attributes and labels from vector files.
  
-<note>WFS services are currently not supported directly in the Viewer. However  it is possible to overlay features available through WFS by accessing the Orbit Publication with one of the available plugins , [[dev:products:3dm_plugin_qgis|]] for example.</note>+<note>WFS services are currently not supported directly in the Viewer. However  it is possible to overlay features available through WFS by accessing the Orbit Publication with one of the available plugins, [[dev:products:3dm_plugin_qgis|]] for example.</note>
  
 ===== Point Cloud ===== ===== Point Cloud =====
-A point cloud which is not part of a run/project can be added separately to a publication. This is possible via the <publication_name>.xml file. See below.+A point cloud which is not part of a run/project can be added separately to a publication.  
 +  * Import and convert the point cloud files in an Orbit desktop product. 
 +  * Manage pointcloud files in the 3DM console, see [[dev:server:publisher_console:resources|]].
  
 ===== Basemaps ===== ===== Basemaps =====
Line 56: Line 58:
 **WM(T)S services** \\ **WM(T)S services** \\
   * WM(T)S services are supported as local resources in [[dev:technology:supported_formats:image:otm|]] (*.otm)  format.   * WM(T)S services are supported as local resources in [[dev:technology:supported_formats:image:otm|]] (*.otm)  format.
-  * Manage .otm files in the Resources tab of the EOS console.+  * Manage basemap files in the 3DM console, see [[dev:server:publisher_console:resources|]].
  
 **Georeferenced images** \\ **Georeferenced images** \\
   * Georeferenced [[dev:technology:supported_formats:image:omi|]] (*.omi) with accompanying *.ord file is also supported as basemap layer.\\   * Georeferenced [[dev:technology:supported_formats:image:omi|]] (*.omi) with accompanying *.ord file is also supported as basemap layer.\\
-  * Manage and add georeferenced images as basemaps to a publication via the <publication_name>.xml file. See below.+  * Manage basemap files in the 3DM console, see [[dev:server:publisher_console:resources|]].
  
 ===== Mesh ===== ===== Mesh =====
-Mesh datasets can be added to a publication via the <publication_name>.xml file. See below. \\+Mesh datasets can be added to a publication as a separate resource.\\
 Supported type of mesh datasets: Supported type of mesh datasets:
-  * Cesium b3dm using gltf storage type. *.3dtiles, *.ord and *.ini files have to be available for Orbit to understand how to read cesium 3D tiles. *.3dtiles is an empty text file, *.ini file can also be empty or contain translation and scale of the mesh. +  * Cesium b3dm using gltf storage type.  
- +  * *.3dtiles, *.ord and *.ini files have to be available for Orbit to understand how to read cesium 3D tiles.  
-===== <publication_name>.xml ===== +    * *.3dtiles is an empty text file 
- +    * *.ini file can be empty or contain translation and scale of the mesh.
-  - Create folder 'publication_resources' in <installation folder>\server\program\services\publisher +
-  - The <publication_name>.xml file should be added in 'publication_resources' folder. This file allows to add non-EOS resources into the publication with the name exactly the same as the one from the publication. +
- +
-<publication_name>.xml example: +
- +
-<code> +
-<resources> +
- <resource> +
- <id>1001</id> +
- <name>Mesh City Model</name> +
- <file>D:/test/20180829_cesium/test_TILES_cESIUM.3dtiles</file> +
- <basemap>false</basemap> +
- <dem>false</dem> +
- </resource> +
- <resource> +
- <id>1002</id> +
- <name>SRTM Orthometric</name> +
- <file>O:/Nasa/Shuttle Radar Topography Mission (SRTM)/png_orthometric/srtm.omi</file> +
- <basemap>false</basemap> +
- <dem>true</dem> +
- </resource> +
- <resource> +
- <id>1003</id> +
- <name>Ghent South PointCloud</name> +
- <file>D:/BE_Ghent_South/BE_Ghent_South_PointCloud.opc</file> +
- <basemap>false</basemap> +
- <dem>false</dem> +
- </resource> +
-</resources> +
-</code> +