Introduction
Introduction section.
Description
The most common use with a mobile device is field data collection. Nowadays gvSIG Mobile allows read some services like WFS, but only can read small layers. Read the heavy SML and O&M sensor data files from SOS server with gvSIG Mobile, which runs in devices with low memory isn’t very handy. This is the reason why is not recommended the use of gvSIG Mobile like a sensor data consumer .
On the other hand, the SOS protocol includes the transactional profile, with register and insert operations, adding new sensors and observations in SOS services. This profile is called SOS-T, used by sensor data producers in order to add the given measures. Next sequence diagram shows a typical sequence of operations:
Both RegisterSensor and InsertObservation requests are simple XML's, therefore upload them from gvSIG Mobile to SOS server is possible and very useful, as the mobile device can publish sensor data right away from field.
This document analyses gvSIG Mobile SOS-T project. The goal is add the capability of using gvSIG Mobile as a sensor, allowing upload sensor data directly from gvSIG Mobile to SOS services.
But this sensor data can be get from different sensors that are integrated in the device. The list of supported sensor data providers must be extensible and we are only going to provide an implementation for the GPS, that can generate waypoints every time in a configured period. This data could be sent to a SOS server, which can stores waypoints as positions or just a single data value.
The user will choose the SOS server to publish through a GUI. Then, gvSIG will register the sensor into the SOS server if it didn’t exist yet. Once configured the time interval and selected the right sensor which provides the measures, the program will begin uploading observations every time automatically.
Requisites
New plug-in (stand alone jar and/or bundle) for gvSIG Mobile which allows publish sensor data (example: GPS positions) from PDA.
Development Following OGC SOS standard in order to connect to a SOS server with transactional extension implemented (example: 52º North).
Allow register new sensor in a SOS server. (add new offering, insert sensor operation)
Also allow insert observations into a registered sensor instance. (insert observations into procedure from an offering)
The time between observations have to be configured by the user.
GPS data source have to be supported as data source from gvSIG Mobile sensor input.
Source Code compatible with gvSIG Desktop.
The system uses simple templates in order to send the requests to the server. The goal is not the creation of a complex system to edit all the possible requests.
- Simple GUI for gvSIG Mobile, allowing the user to:
- Configure period time observations and sensor to publish.
- Insert/Choose SOS server URI to insert the observations.
- Select the (procedure) sensor ID from a server to add new observation data.
- Tests.