Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:viewer:sdk:concepts [2020/04/01 13:37] nathalie |
dev:viewer:sdk:concepts [2022/09/28 13:10] (current) pieter |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Concepts ====== | + | ====== |
- | ==== Index ==== | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | [[concepts# | + | |
- | ---- | + | This page is a glossary describing some basic concepts of the 3DM Viewer and 3DM Viewer SDK. |
- | ===== Bookmark | + | ==== Bookmark ==== |
A Bookmark is a utility for Named Users that allows them to store a Workspace for later reference. By default, this is a private utility, available from the Bookmark sidebar of the Viewer. | A Bookmark is a utility for Named Users that allows them to store a Workspace for later reference. By default, this is a private utility, available from the Bookmark sidebar of the Viewer. | ||
Line 32: | Line 11: | ||
* Anyone else can open a Bookmark that is made public, providing the Organisation has enough Guest Users left. | * Anyone else can open a Bookmark that is made public, providing the Organisation has enough Guest Users left. | ||
- | ===== Coordinate ===== | + | ==== Coordinates |
A Coordinate represents an exact geographical location in a specific CRS. | A Coordinate represents an exact geographical location in a specific CRS. | ||
- | ===== Coverage ===== | + | By default, all data returned by the SDK is expressed in WGS84, EPSG: |
- | Coverage is an overall term to point out vector data which consists of the Footprints, the Envelope, and the Field of Views of a run. | + | ==== Coordinate Reference System ==== |
- | + | ||
- | ===== Coordinate Reference System | + | |
A CRS or Coordinate Reference System is a system used to interpret locations of features with the use of their coordinates. For more information on the use of Coordinate Reference Systems in Orbit, please visit [[dev: | A CRS or Coordinate Reference System is a system used to interpret locations of features with the use of their coordinates. For more information on the use of Coordinate Reference Systems in Orbit, please visit [[dev: | ||
Line 48: | Line 25: | ||
Spatial objects that are returned by the SDK are expressed in WGS84 (EPSG code 4326) by default. | Spatial objects that are returned by the SDK are expressed in WGS84 (EPSG code 4326) by default. | ||
- | ===== Field Of View ===== | + | ==== Coverage ==== |
+ | |||
+ | Coverage is an overall term to point out vector data which consists of the Footprints, the Envelope, and the Field of Views of a run. | ||
+ | |||
+ | ==== Field Of View ==== | ||
A Field Of View is the representation of the position, direction or bounds of a View on the Reference Map. \\ | A Field Of View is the representation of the position, direction or bounds of a View on the Reference Map. \\ | ||
- | Field-Of-Views are provided by the SDK as MapObjects. | + | Field-Of-Views are provided by the SDK as '' |
- | ===== Footprint | + | ==== Footprint ==== |
- | A Footprint is the representation of a visible Resource on the Reference Map. Footprints are useful to indicate data availability. Footprints can be Photo Positions or the Envelope. \\ | + | A Footprint is the representation of a visible Resource on the Reference Map. Footprints are useful to indicate data availability. Footprints can be Photo Positions, a Trajectory |
Footprints are provided by the SDK as '' | Footprints are provided by the SDK as '' | ||
- | ===== Globals | + | ==== Globals ==== |
Global state (focus, mouse hover). | Global state (focus, mouse hover). | ||
- | ===== Login ===== | + | ==== Login ==== |
When you launch the SDK, you need to log in to a service that will provide the data. The SDK supports both cloud-based and on-premise content. | When you launch the SDK, you need to log in to a service that will provide the data. The SDK supports both cloud-based and on-premise content. | ||
Line 77: | Line 58: | ||
Note: For security reasons, we do not allow the SDK Developer to preset a 3DM Cloud Named User Login. | Note: For security reasons, we do not allow the SDK Developer to preset a 3DM Cloud Named User Login. | ||
- | ===== MapObjects | + | ==== MapObjects ===== |
- | A MapObject is an object that defines everything needed to render it on the Reference Map: | + | Visualisation of Data |
- | * Spatial information (point, | + | |
- | * Legend information (line color, etc...) | + | |
- | Currently, there are four types of MapObjects that can be rendered | + | To represent objects to be rendered, we decided on introducing a self-describing type called a '' |
- | * Field-of-views | + | * It describes its own spatial component (point, line, area) |
- | * Measurements | + | * It describes its own legend component (line color, etc...) |
- | * Globals | + | |
- | * Footprints: Visualisation of where resources have data available. | + | |
- | ===== Measurement | + | Currently we have 4 types of MapObjects that are to be rendered in their own layer. |
+ | * Field-of-views : visualisation of view states. | ||
+ | * Measurements : Visualisation of measurements. | ||
+ | * Globals : Visualisation of global state (focus, mouse hover). | ||
+ | * Footprints : Visualisation of where resources have data available. | ||
+ | |||
+ | By using MapObjects, we move the complexity of representing Viewer data out of your code and into the Viewer SDK itself. | ||
+ | |||
+ | ==== Measurement ==== | ||
A Measurement can be a point, line or area you measure. | A Measurement can be a point, line or area you measure. | ||
Line 95: | Line 80: | ||
When making a Measurement, | When making a Measurement, | ||
- | ===== Publication | + | ==== Pan Angle ==== |
+ | |||
+ | The viewing direction of a view in the horizontal plane with 0 degrees indicating north and 90 degrees indicating the east. Pan is similar to the concept of heading in navigation. | ||
+ | |||
+ | ==== Publication | ||
A Publication is a representation of Resources in the Viewer. A publication is the end product of the [[dev: | A Publication is a representation of Resources in the Viewer. A publication is the end product of the [[dev: | ||
- | ===== Promise | + | ==== Promise ==== |
A Promise is an object instance that is a placeholder for a value that is not yet available. | A Promise is an object instance that is a placeholder for a value that is not yet available. | ||
Line 105: | Line 94: | ||
The user of a Promise can attach listeners to the Promise to be notified when the Promise either resolves or fails. | The user of a Promise can attach listeners to the Promise to be notified when the Promise either resolves or fails. | ||
- | ===== Reference Map ===== | + | ==== Reference Map ==== |
The Reference Map is the 2D map, which is part of the Viewer. It shows you where Resources and Views are situated in the form of Footprints and Field of Views. | The Reference Map is the 2D map, which is part of the Viewer. It shows you where Resources and Views are situated in the form of Footprints and Field of Views. | ||
- | ===== Resource | + | The '' |
+ | The '' | ||
+ | The '' | ||
+ | |||
+ | ==== Resource ==== | ||
A resource is a dataset that can be opened in the Viewer. A resource can be one of the following types: Mobile Mapping run, Oblique project, UAS run, vector data, point cloud, textured mesh. | A resource is a dataset that can be opened in the Viewer. A resource can be one of the following types: Mobile Mapping run, Oblique project, UAS run, vector data, point cloud, textured mesh. | ||
- | ===== Signal | + | ==== Signal ==== |
- | A Signal can be best described as an event emitter. | + | A Signal can be best described as an event emitter. |
- | Some signals also provide a payload when they dispatch an event. | + | Signals start with " |
- | By convention, signal names are CamelCase and always start with " | + | ==== Start-Up Options ===== |
- | + | ||
- | ===== Start-Up Options | + | |
A Start-Up Option is a named value that can be provided on viewer startup. | A Start-Up Option is a named value that can be provided on viewer startup. | ||
Line 127: | Line 118: | ||
One example of such an option is the " | One example of such an option is the " | ||
- | ===== User ===== | + | ==== Tilt Angle ==== |
+ | |||
+ | The viewing direction of a view in the vertical plane parallel to the viewing direction. | ||
+ | |||
+ | ==== User ==== | ||
There are 3 types of users, all automatically handled by the SDK (see Log in) | There are 3 types of users, all automatically handled by the SDK (see Log in) | ||
Line 134: | Line 129: | ||
* 3DM Publisher users | * 3DM Publisher users | ||
- | ===== View ===== | + | ==== View ==== |
A View is a single interactive component of the Viewer Workspace that visualizes the visible Resources, in some way or form. | A View is a single interactive component of the Viewer Workspace that visualizes the visible Resources, in some way or form. | ||
- | ===== Viewer | + | ==== Viewer ==== |
The Viewer is the framework in which a publication is made and resources are represented. | The Viewer is the framework in which a publication is made and resources are represented. | ||
- | ===== Workspace | + | ==== Viewer3DM |
+ | |||
+ | The central Viewer component is named '' | ||
+ | |||
+ | ==== Workspace | ||
A Workspace defines a list of Resources and how they are presented by the Viewer. | A Workspace defines a list of Resources and how they are presented by the Viewer. | ||
Publications and Bookmarks use a Workspace to store the Viewer state. | Publications and Bookmarks use a Workspace to store the Viewer state. |
Last modified:: 2020/04/01 13:37