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/03/25 11:36] 127.0.0.1 external edit |
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 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 dedicated Content Manager license and run data processing (Import and Merging Runs) on a separate machine with all resources being processed locally. \\ | + | 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: | ||
- Import and process your data into mobile mapping runs using the " | - Import and process your data into mobile mapping runs using the " | ||
- | - [[dev: | + | - [[dev: |
- | - Organize Runs into Projects using 3DM Orbit Publisher Catalog, see [[dev:desktop_ext:mapping:manage: | + | - Manage the runs in the 3DM console, see [[dev:server:publisher_console:resources|]]. |
- | + | ||
- | All Mapping Runs\Oblique Projects included in a Publication have to be HTML5-ready, | + | |
==== 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: |
- | - Copy the .osl file corresponding to the legend specified in *.olg file (can be checked in Legend editor) | + | - Open .olg file and search for the parameter ' |
+ | - Copy the .osl file corresponding to the value of that parameter | ||
- 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. | ||
+ | |||
+ | **Workflow: | ||
+ | - Import and convert the vector files in an Orbit desktop product. | ||
+ | - Manage vector files in the 3DM console, see [[dev: | ||
==== Recommended ==== | ==== Recommended ==== | ||
- | * Remove all unnecessary attributes from vector files. | + | * Remove all unnecessary attributes |
- | < | + | < |
+ | |||
+ | ===== Point Cloud ===== | ||
+ | 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: | ||
===== Basemaps ===== | ===== Basemaps ===== | ||
+ | |||
+ | **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 basemap files in the 3DM console, see [[dev: | ||
+ | |||
+ | **Georeferenced images** \\ | ||
* Georeferenced [[dev: | * Georeferenced [[dev: | ||
+ | * Manage basemap files in the 3DM console, see [[dev: | ||
===== Mesh ===== | ===== Mesh ===== | ||
- | Currently cesium b3dm using gltf storage type is supported.\\ | + | Mesh datasets can be added to a publication as a separate resource.\\ |
- | + | Supported type of mesh datasets: | |
- | To add mesh to a Publication: | + | |
- | | + | * *.3dtiles, *.ord and *.ini files have to be available for Orbit to understand how to read cesium 3D tiles. |
- | - Folder ' | + | * *.3dtiles is an empty text file |
- | - The publilcation_name.xml file should be added in ' | + | * *.ini file can be empty or contain translation and scale of the mesh. |
- | + | ||
- | publilcation_name.xml example: | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | </ | + | |
- | </ | + |