Document Actions
General Overview
The sensor project contains different components that can be studied independently. This components provides their own interface that can be used by the consumer. One of these components can be classified as libraries, others as a extensions and finally as user interfaces.
org.gvsig.mobile.remoteclient.sos will be used by a implementation of org.gvsig.mobile.sensor.lib.api.
Libraries
- org.gvsig.mobile.sensor.lib: Standalone sensor library.
- org.gvsig.mobile.sensor.lib.api: Application programing interface that is used by other component to select a sensor provider and start to upload data. It has methods to retrieve all the registered sensor data providers, to retrieve all the previous used SOS servers, and to create a Service that is the responsible to upload data to the server.
- org.gvsig.mobile.sensor.lib.spi: Programing interface to add sensor data providers. It has methods to register providers and methods to retrieve the list of registered providers. It defines the sensor data provider API.
- org.gvsig.mobile.remoteclient.sos: The SOS protocol manager. It contains utilities to create a SOS request as using templates. created for every configured sensor and to parse the SOS replies (ID Sensor returned). The GPS provider uses it to connect to the server, send sensor data and retrieve server responses.
- org.gvsig.mobile.sensor.prov: Providers implementations using org.gvsig.mobile.sensor.lib.spi.
- org.gvsig.mobile.sensor.prov.gps: GPS sensor provider implementation of org.gvsig.mobile.sensor.lib.spi methods adding gps registering, GPS offering, procedure and insert new positions as observations.
Extension
- org.gvsig.mobile.extension.sensor: This component let the user select the server, register the sensor on it and start to upload data every time configured.
UI Components
- org.gvsig.mobile.sensor.ui: User Interface components.
- org.gvsig.mobile.sensor.ui.api: New methods to add the graphics components to show sensor configuration.
