Sensor Web Client Architecture

TODO Describe ...
  • ... Server architecture
  • ... Server Interfaces (RESTful, RPC)
  • ... Tooling Interfaces (e.g. SosMetadataHandler)
  • ... Event based architecture
  • ... Data Model


The Sensor Web Client application is divided into two parts:
User Interface
A browser frontend (UI) which will be compiled into HTML/!JavaScript by the GWT compiler. During development the UI can be implemented and debugged as Java code (see here how to setup the project for development). The user interface is mainly for interaction purposes and delegates any processing to the server component. This increases performance when working with (mostly large) timeseries.
Server Engine
The server component aggregates different data sources, generates reports, is responsible for session management and graph rendering, etc. The server component acts like a facade to each configured SOS instance. This server builds and sends OGC conform requests, parses the service responses and shares a common data model with the client. It is possible to perform pre-processing, e.g. compression of large timeseries to increase performance.

The server component is built upon the 52n°North Ox-Framework oxf-integration.png


Topic revision: r1 - 16 Apr 2013, HenningBredel
Legal Notice | Privacy Statement

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback