Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:server:publishers:viewer_data_preparation [2019/09/02 06:10] paulien [Vector data] |
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 |
===== 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 |
* 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 | + | * If a Publication contains at least one Resource not compliant |
===== 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, | + | 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, |
**Workflow: | **Workflow: | ||
- Import and process your data into mobile mapping runs using the " | - Import and process your data into mobile mapping runs using the " | ||
- [[dev: | - [[dev: | ||
- | | + | - Manage |
- | | + | |
==== Recommended ==== | ==== Recommended ==== | ||
Line 35: | Line 34: | ||
* All vector layers should be converted to Orbit native formats. Use [[dev: | * All vector layers should be converted to Orbit native formats. Use [[dev: | ||
* Every vector layer must have [[dev: | * Every vector layer must have [[dev: | ||
- | * Vector layers of Point type must have [[dev: | + | * Vector layers of Point type must have [[dev: |
- Open .olg file and search for the parameter ' | - Open .olg file and search for the parameter ' | ||
- Copy the .osl file corresponding to the value of that parameter from ..\server\program\symbols in the installation folder. | - Copy the .osl file corresponding to the value of that parameter from ..\server\program\symbols in the installation folder. | ||
Line 43: | 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: | + | - Manage vector files in the 3DM console, see [[dev: |
==== Recommended ==== | ==== Recommended ==== | ||
- | * Remove all unnecessary attributes from vector files. | + | * Remove all unnecessary attributes |
- | < | + | < |
===== Point Cloud ===== | ===== Point Cloud ===== | ||
- | A point cloud which is not part of a run/project can be added separately to a publication. | + | A point cloud which is not part of a run/project can be added separately to a publication. |
+ | * Import and convert | ||
+ | * Manage pointcloud files in the 3DM console, see [[dev: | ||
===== Basemaps ===== | ===== Basemaps ===== | ||
Line 57: | Line 58: | ||
**WM(T)S services** \\ | **WM(T)S services** \\ | ||
* WM(T)S services are supported as local resources in [[dev: | * WM(T)S services are supported as local resources in [[dev: | ||
- | * Manage | + | * Manage |
**Georeferenced images** \\ | **Georeferenced images** \\ | ||
* Georeferenced [[dev: | * Georeferenced [[dev: | ||
- | * Manage | + | * Manage |
===== Mesh ===== | ===== Mesh ===== | ||
- | Mesh datasets can be added to a publication | + | Mesh datasets can be added to a publication |
Supported type of mesh datasets: | Supported type of mesh datasets: | ||
* Cesium b3dm using gltf storage type. | * Cesium b3dm using gltf storage type. | ||
Line 70: | Line 71: | ||
* *.3dtiles is an empty text file | * *.3dtiles is an empty text file | ||
* *.ini file can be empty or contain translation and scale of the mesh. | * *.ini file can be empty or contain translation and scale of the mesh. | ||
- | |||
- | ===== < | ||
- | |||
- | - Create folder ' | ||
- | - The < | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | </ | ||
- | </ |