Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:viewer:sdk:scope [2020/03/31 12:30]
nathalie
+++ dev:viewer:sdk:scope [2020/05/13 05:55] (current)
jeroen
@@ Line 1: / Line 1: @@
-====== Scope ======
+====== Scope & Possibilities ======
-The Orbit’s free SDK gives you the tools to build a plugin that connects a 3rd party application with the Orbit 3D Mapping Viewer. The connection is a two-way communication set up with WebSockets technology which enables synchronizing, augmenting, enriching and integrating datasets at both sides. \\
+Discover the 3DM Viewer SDK.
-**Synchronize views**\\
+The Orbit 3DM Viewer SDK provides the tools to build a plugin to connect a 3rd party host application and the Orbit 3DM Viewer. It is a two-way connection enabling synchronize, augment, enrich and integrate the 3DM Viewer and host application.
-Focus the Viewer to a location the user picked in the 3rd party application. This is also possible the other way around. \\
-**Augment the data in your 3rd party application**\\
+===== Key Features =====
-Overlay vector data representing the 3D data in the 3rd party application. These vector data are the photo positions of a run, the bounding box of the run, the location and orientation of the images that are opened, and even the current measurement in the Viewer. \\
-**Enrich existing external datasets**\\
+=== Synchronize views ===
-Next to visualizing measurements from the Viewer inside the 3rd party application, it’s also possible to save these as features in an external dataset opened in the application. \\
-**Integrate external data in the Viewer**\\
+Focus the Viewer to a location the user picked in the 3rd party application. This is also possible the other way around.
-Data features opened in the 3rd party application can be added to the Viewer as a separate resource, using the SDK. \\
+=== Augment the data in your 3rd party application ===
-Links to
+Overlay vector data representing the 3D data in the 3rd party application. These vector data are the photo positions of a run, the bounding box of the run, the location and orientation of the images that are opened, and even the current measurement of the Viewer.
-  * documentation on viewer
-  * plugin documentation
+=== Enrich existing external datasets ===
-  * test with try-it-nows
+Next to visualizing measurements from the Viewer inside the 3rd party application, it’s also possible to save these as features in an external dataset opened in the 3rd party application.
+=== Integrate external data in the Viewer ===
+Data features opened in the 3rd party application can be added to the Viewer as a separate resource, using the SDK.
+=== Easy to run environment ===
+The Viewer is opened in a tab in the user's browser. Apart from an up-to-date browser and the conditions to run the 3rd party application, there's no need for special requirements to use a plugin made with the SDK.
+There is one SDK reference that can be implemented on multiple platforms. Different implementations are available. At the moment we have an SDK for JavaScript, .NET, and Python.
+===== What's in the API =====
+The API has everything you need to :
+  * Visualize resource footprints (where is data available?)
+  * Visualize field-of-views (where are the views?)
+  * Visualize measurements
+  * Use measurements (add them to your own layers for example)
+  * Integrate with Viewer zoom-to-extent
+  * Integrate with Viewer position picking
+  * Open a View at a location
+  * Focus all Views on a location
+  * Add your own objects to the Viewer

Last modified:: 2020/03/31 12:30