I have to interface with some dumb sensors that are mounted on a drone. The drone itself has a GPS sensor and is sending their coordinates. What the sensor providers are currently doing is sending the name of the sensor together with their
measures. This way, the service receiving the measures is able to infer the position of a sensor from the measure provided by the GPS sensor mounted on the drone whose name is equal to the one provided by each sensor. That is, the drone is acting as a platform
with GPS capabilities where some dumb sensors are mounted.
But this is not compliant with SOS, and I want to provide a standard SOS server to support this situation, which is relatively common. But I do not get to find any field in the sosInsertObservation.xsd that allows me to cross the measure
of a sensor with another sensor to get its geographical position. There is an example from 52North that registers a set of sensors with a position but it does not fit my problem, because the drone will act as a moving platform, and hence I need to update the
position for each measure.
Right now, the only solution I can think of is to use the call to registerSensor to record the set of sensors of the platform and extract the GPS sensor from them, looking for the one whose observed property has position type. This, added
to the sensor identifier reported in insertObservation, would allow the service to look for the corresponding GPS sensor, get its last measure, and use it. But this approach has a huge drawback: it is specific for my system and it will work only with my specific
procedure for selecting the proper GPS sensor. The idea for using a standard is creating interoperable components, but this solution would possibly not work with any other platform that .
Does SOS support any way for a sensor to specify that its position is provided by another one?
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free
and will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
SWE mailing list
[hidden email] http://list.52north.org/mailman/listinfo/swe http://sensorweb.forum.52north.org Please respect our mailing list guidelines: