Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
dev:cloud:concepts:resources [2022/05/13 09:38] jeroen removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== 3DM Cloud - Resources ====== | ||
- | Will we be able to designate a staging area for uploads? (i.e, user’s upload data from district, data is staged, division user applies template and performs qa/qc before moving to production) | ||
- | Users with the role " | ||
- | Users with the Role of " | ||
- | A flexible tagging system provides users with role " | ||
- | |||
- | |||
- | |||
- | What integration is available with OrbitGT via API or otherwise? | ||
- | Orbit 3DM Viewer comes with .net, JavaScript, and Phyton API for integrating the 3DM Viewer into the host application. | ||
- | For each API POC plugins are available, free to download both source documentation as the read-to-use plugin | ||
- | https:// | ||
- | |||
- | What is the procedure for files where a template is not available? | ||
- | Templates are required for Mapping systems that include geotagged images. | ||
- | For single data type resources like single point cloud, single textured mesh, ... no template is required. | ||
- | If a template is missing we provide generic import templates or can customize an import template based on a well-documented sample dataset. |