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] |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== 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. | ||
- | ===== 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: | ||
- | * 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. | ||
- | * WM(T)S should be accessed with special Orbit Tile Map (otm) driver. | ||
- | * If a Publication contains at least one Resource not complaint with mandatory requirements, | ||
- | |||
- | ===== Mobile Mapping\UAS\Oblique data ===== | ||
- | |||
- | ==== Mandatory ==== | ||
- | To publish mobile mapping resources, data must be imported as Runs and organized into Projects. \\ | ||
- | 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, | ||
- | |||
- | **Workflow: | ||
- | - Import and process your data into mobile mapping runs using the " | ||
- | - [[dev: | ||
- | - Organize Runs into Projects using 3DM Orbit Publisher Catalog, see [[dev: | ||
- | - Manage projects in EOS console, see [[dev: | ||
- | |||
- | ==== Recommended ==== | ||
- | * All ' | ||
- | * Only necessary attributes should be included in the photo positions locations.ovt files: Orbit system attributes and only those attributes which are of interest for end user if any. To strip photo positions of unnecessary attributes: | ||
- | - Back up locations.ovt. | ||
- | - Convert locations.ovt to *.ovf. | ||
- | - Remove attributes through [[dev: | ||
- | - Convert *.ovf to locations.ovt and replace original file. | ||
- | * Runs belonging to one logical group should be physically merged into one Run (contrary creating Project containing multiple Runs) with [[dev: | ||
- | |||
- | ===== Vector data ===== | ||
- | |||
- | ==== Mandatory ==== | ||
- | * All vector layers should be converted to Orbit native formats. Use [[dev: | ||
- | * Every vector layer must have [[dev: | ||
- | * Vector layers of Point type must have [[dev: | ||
- | - 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. | ||
- | - Paste it next to the .ovf 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 EOS console, see [[dev: | ||
- | |||
- | ==== Recommended ==== | ||
- | * Remove all unnecessary attributes from vector files. | ||
- | |||
- | < | ||
- | |||
- | ===== 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 < | ||
- | |||
- | ===== Basemaps ===== | ||
- | |||
- | **WM(T)S services** \\ | ||
- | * WM(T)S services are supported as local resources in [[dev: | ||
- | * Manage .otm files in the Resources tab of the EOS console. | ||
- | |||
- | **Georeferenced images** \\ | ||
- | * Georeferenced [[dev: | ||
- | * Manage and add georeferenced images as basemaps to a publication via the < | ||
- | |||
- | ===== Mesh ===== | ||
- | Mesh datasets can be added to a publication via the < | ||
- | 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 be empty or contain translation and scale of the mesh. | ||
- | |||
- | ===== < | ||
- | |||
- | - Create folder ' | ||
- | - The < | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | < | ||
- | </ | ||
- | </ | ||
- | </ |
Last modified:: 2019/09/02 06:10