1 of 12

WebUI Review

Release 4.3

Sprint 4.3.3

July 6th

​

​

2 of 12

Overview Release 4.3 (1)

Main achievement:

  • Extend existing GE implementation to serve wider range of applications
  • Improve existing APIs and provide new features that make application development easier:

​

  • 2D-UI:
    • Added new touch events for both Android and iOS devices

​

  • POI Data Provider:
    • Orion Context Broker Integration
    • New demo that includes new functionality
    • Cross chapter POI discussion led to sketches of a new architecture and interface

​

3 of 12

Overview Release 4.3 (2)

  • GIS Data Provider
    • Added support for Octet stream dataset format
    • Now uses XML3D Asset instancing feature for better and more efficient assembly of 3D landscape models
    • Demo and more features presented in this meeting

​

  • Interface designer
    • New methods of scene manipulation
    • Saving functionality to persist created scene
    • Demo later in this meeting

​

4 of 12

Overview Release 4.3 (3)

  • 3D-UI-XML3D
    • Asset hierarchy instancing for easier composition of complex scenes
    • Load events for complex geometry
    • Internet Explorer 11 support
    • Fast progress towards new version 5.0 with optimized interfaces

​

  • Synchronization
    • New implementation FiVES complements the 3D-UI-WebTundra oriented reference implementation with a 3D-UI-XML3D optimized server
    • SceneAPI complies Synchronization GE specification -> Cross compatibility
    • Final Release planned within Release 4
      • Binaries for Windows and Linux, Recipes in FIWARE Lab
      • Documentation and E-Learning Material

​

5 of 12

WebUI Highlights - Sprint 4.3.3 (1)

3D-UI-XML3D:

  • New version 4.3.2 published to Lab
    • Internet Explorer 11 Support
    • External Xflow operators
      • Reference externally defined operators directly from within the scene
      • No need to provide operators as JavaScript file together with the application anymore

​

  • XML3D Bundle:
    • Still several issues with FIWARE Lab accounts. Reported to help desk and most of them were solved until end of the Release
    • Bundle Testing will need more work in Sprint 4.4.1

​

6 of 12

WebUI Highlights - Sprint 4.3.3 (2)

  • Alternative Synchronization GE implementation: FiVES
    • Officially started in Release 4.3.2
      • Lightweight, modular synchronization server with generic data model
      • Complements the set of WebUI software by synchronization that is optimized towards XML3D
    • Documentation ready to be published
    • Aligned API and Real Time Synchronization protocol with the Specification

​

  • Next Steps:
    • Provide REST API with respect to Synchronization GE
    • Publish documentation and E-Learning material
    • Publish software to the LAB

​

7 of 12

WebUI Highlights - Sprint 4.3.3 (3)

  • GIS GE
    • Multiple new features released:
      • Additional datasets
      • Asset instancing
      • Octet-stream visualization and
      • Octet-stream Resolution
    • GIS GE client demos for all the above features: http://gis.testbed.fiware.org:8080/gis_test_client/
    • Additional datasets major addition, now it is possible to use DEM images as for source to elevation. Example client of using DEM images and creating 3D terrain here: http://gis.testbed.fiware.org:8080/gis_test_client/GIS_Client_DEM/index.xhtml
      • Web client receives terrain elevation data from the DEM file in octet-stream format and generates terrain block based on this information. Client divides whole layer to 5x5 grid, each block is queried and created when camera lands to the empty area.

DEM image

GIS GE example client:

XML3D Scene created based on DEM file information

Elevation data in octet-stream format

8 of 12

WebUI Highlights - Sprint 4.3.3 (4)

  • Interface Designer
    • Saving / loading a scene
    • Javascript API and extendability of the interface designer
    • Live demo of all the functionality (never been done before)
  • Next Steps:
    • Multi-object manipulation

​

9 of 12

WebUI Highlights - Sprint 4.3.3 (5)

  • Points of Interest Data Provider (POI DP)
    • Dynamic data
      • A POI can have a dynamic data descriptor component fw_dynamic to define where from and how data items are fetched.
      • Almost any data item of any component may be dynamic.
      • Data can be fetched from different kinds of already available REST web services providing HTML pages, JSON data, XML data, etc.
      • Powerful pattern matching mechanism to find the wanted data item from external data.
      • Data from several different kind of services can be combined to one POI.
      • Fetched data is cached to the POI server until explicit expiration time.
      • Remote data source identities, credentials, and patterns are protected in a hidden configuration file.
    • Sensor data
      • Generic sensor data component fw_sensor for measurement values
      • Versatile and easy-to-use with dynamic data component

10 of 12

WebUI Highlights - Sprint 4.3.3 (6)

POI DP demonstration at http://dev.cie.fi/FI-WARE/demos/dyn_poi/

  • Select Categories -> Sensor
  • Look Finland (road weather stations as such) or Santander (sensors via Orion CB)
  • Click to a POI pin to look sensor values

11 of 12

WebUI - Next Steps (1)

  • Bundles:
    • Keep testing.
    • XML3D-Geo-Visualization:
      • Reduce number of used VM’s to make deployment easier (needs many resources at the moment)
      • Use of Docker would help, once the infrastructure for that has been set up

​

  • 3D-UI-XML3D:
    • Release 5.0 planned for end of August / early September
      • Improved, easier to use API
      • More efficient implementation of core feature sets
      • Consolidation of DOM nodes to a smaller, easier to use set

​

12 of 12

WebUI - Next Steps (2)

  • Synchronization:
    • Provide recipes and example installations of FiVES GEi
    • Implement closer integration with existing dynamic POI concepts
    • Investigate integration of Synchronization GE with GE from other chapters, e.g. ContextBroker, or for Authentication

​