Spatial Observation support for SOS clients

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Spatial Observation support for SOS clients

jdf1307
This post was updated on .
Hi there,

I wanted to ask if the future version of the 52°North JS client will support the Spatial Observation as mentioned in [0].

If I insert such observations in the SOS and use GetObservation in the SOS instance everything works fine.
However if I use the JS client to visualize the data, there are no markers added to the map.
At least I can see the observation values as timeseries data in diagram mode.

I also checked out the SensorWebClient [2].
However if I deploy the client in Tomcat, there are only three stations shown, which are not associated with my sensor station, they are called "PEGELONLINE", "Wupperverband", and "Air Quality Belgium".
Furthermore the map loads infinitely, the other buttons are not responding, when I click on them.
After a timeout of about 5 minutes the client stops loading.

With the QGIS client I achieved similar not satisfactory results.

I do not have the possibility to check this in ArcGIS SOS Plugin, due to lacking ArcGIS myself. Does anybody have experience in that matter?

So are there solutions for visualizing mobile sensor data using current SOS clients?
I would like to implement this feature for the JS thin client myself, however I do not know where to start in [1]. I would be glad if hints regarding establishing visualization for mobile sensors can be provided.


Due to the need of visualizing such mobile sensor data I implemented a prototype JS client, which also is based on leaflet.

In this a simple routine is implemented, the client periodically executes GetObservation request addressing my currently running SOS instance. After receiving the POX response is processed, required values are saved in variables. Using leaflet a map is generated and markers are added, containing observation values and time. The position of the markers are based on the om:parameter position value.
Observable properties can be switched on and off using layer control.
However this approach is not feasible in the long run, it would be better to augment the current 52°North JS client.
I attached a screenshot of this client in the end of the post.
You can visit the client on (sometimes the server could be down): http://gpslog.ddns.net:8080/sosClient



Best regards,

Jack

-----------------------------------------------------------------------
[0] http://schemas.opengis.net/om/2.0/examples/spatial_observation1.xml
[1] https://github.com/52North/js-sensorweb-client
[2] http://52north.org/downloads/download/14-clients/400-52n-sensorwebclient-310-release
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

Henning Bredel-2
Hey jdf1307,

find my comments inline.

Am 04.07.2016 um 20:52 schrieb jdf1307:

> Hi there,
>
> I wanted to ask if the future version of the 52°North JS client will support
> the Spatial Observation as mentioned in [0].
>
> If I insert such observations in the SOS and use GetObservation in the SOS
> instance everything works fine.
> However if I use the JS client to visualize the data, there are no markers
> added to the map.
> At least I can see the observation values as timeseries data in diagram
> mode.


The JS client connects to a lightweight layer to access sensor data
stored in an SOS. That is, there is an additional layer in between the
SOS and the JS Client. This is due to both performance reasons and to
provide a more natural developer experience within JavaScript.


> I also checked out the SensorWebClient [2].
> However if I deploy the client in Tomcat, there are only three stations
> shown, which are not associated with my sensor station, they are called
> "PEGELONLINE", "Wupperverband", and "Air Quality Belgium".
> Furthermore the map loads infinitely, the other buttons are not responding,
> when I click on them.
> After a timeout of about 5 minutes the client stops loading.

That project is GWT based and does not benefit much from our developing
resources at the moment. It probably does not compile JavaScript for
current browsers. However, similar to the above comment, it depends also
on connector implementations which are able to communicate with specific
SOS dialects (here I include mobile data) .. at least the default SOS
connector would have to be improved to parse mobile data. This is on our
roadmap, once we have finished conceptualization and implementation of
our series-rest-api. The SOS proxy provides a simple backend
implementation for that API.


> With the QGIS client I achieved similar not satisfactory results.

I doubt that QGIS has implemented mobile SOS data at the moment, but I
don't know, to be honest.


>
> I do not have the possibility to check this in ArcGIS SOS Plugin, due to
> lacking ArcGIS myself. Does anybody have experience in that matter?

Same here. Mobile data is not supported by this plugin.


>
> So are there solutions for visualizing mobile sensor data using current SOS
> clients?

The way I would go is the


> I would like to implement this feature for the JS thin client myself,
> however I do not know where to start in [1]. I would be glad if hints
> regarding establishing visualization for mobile sensors can be provided.

Which project on github do you mean exactly by saying 'JS thin client'?


>
>
> Due to the need of visualizing such mobile sensor data I implemented a
> prototype JS client, which also is based on leaflet.
>
> In this a simple routine is implemented, the client periodically executes
> GetObservation request addressing my currently running SOS instance. After
> receiving the POX response is processed, required values are saved in
> variables. Using leaflet a map is generated and markers are added,
> containing observation values and time. The position of the markers are
> based on the om:parameter position value.
> However this approach is not feasible in the long run, it would be better to
> augment the current 52°North JS client.
> I attached a screenshot of this client in the end of the post.
> You can visit the client on (sometimes the server could be down):
> http://gpslog.ddns.net:8080/sosClient
>

Interesting, did you code it from scratch? (currently the instance is
down :).


_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

Simon Jirka-2
In reply to this post by jdf1307
Hi Jack,

Your question has an excellent timing. There are currently three
projects in which we extend the JavaScript SOS Client (Helgoland) as
well as the REST-API (as part of the SOS server) to support the
visualisation of mobile sensors. My colleague Jan Schulte will be able
to provide you more information about this.

Best regards
Simon

2016-07-04 20:52 GMT+02:00 jdf1307 <[hidden email]>:

> Hi there,
>
> I wanted to ask if the future version of the 52°North JS client will support
> the Spatial Observation as mentioned in [0].
>
> If I insert such observations in the SOS and use GetObservation in the SOS
> instance everything works fine.
> However if I use the JS client to visualize the data, there are no markers
> added to the map.
> At least I can see the observation values as timeseries data in diagram
> mode.
>
> I also checked out the SensorWebClient [2].
> However if I deploy the client in Tomcat, there are only three stations
> shown, which are not associated with my sensor station, they are called
> "PEGELONLINE", "Wupperverband", and "Air Quality Belgium".
> Furthermore the map loads infinitely, the other buttons are not responding,
> when I click on them.
> After a timeout of about 5 minutes the client stops loading.
>
> With the QGIS client I achieved similar not satisfactory results.
>
> I do not have the possibility to check this in ArcGIS SOS Plugin, due to
> lacking ArcGIS myself. Does anybody have experience in that matter?
>
> So are there solutions for visualizing mobile sensor data using current SOS
> clients?
> I would like to implement this feature for the JS thin client myself,
> however I do not know where to start in [1]. I would be glad if hints
> regarding establishing visualization for mobile sensors can be provided.
>
>
> Due to the need of visualizing such mobile sensor data I implemented a
> prototype JS client, which also is based on leaflet.
>
> In this a simple routine is implemented, the client periodically executes
> GetObservation request addressing my currently running SOS instance. After
> receiving the POX response is processed, required values are saved in
> variables. Using leaflet a map is generated and markers are added,
> containing observation values and time. The position of the markers are
> based on the om:parameter position value.
> However this approach is not feasible in the long run, it would be better to
> augment the current 52°North JS client.
> I attached a screenshot of this client in the end of the post.
> You can visit the client on (sometimes the server could be down):
> http://gpslog.ddns.net:8080/sosClient
>
> <http://sensorweb.forum.52north.org/file/n4028563/mobileSensorJSClient.jpg>
>
> Best regards,
>
> Jack
>
> -----------------------------------------------------------------------
> [0] http://schemas.opengis.net/om/2.0/examples/spatial_observation1.xml
> [1] https://github.com/52North/js-sensorweb-client
> [2]
> http://52north.org/downloads/download/14-clients/400-52n-sensorwebclient-310-release
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/Spatial-Observation-support-for-SOS-clients-tp4028563.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

jansch
Hi Jack,

so first of all what Henning says to the SensorWebClient applies also to
the js-sensorweb-client. There are no big developments in thies
repository. I will add a hint in the readme.md.

The current client developments are focused on the previously mentioned
client called Helgoland [1]. In the branch
feature/map-diagram-combination is a visualization to see a mobile
trajectory which combines a map where you can see the trajectory as
geometry and a diagram where you see the measurement to the regarding
trajectory points. These developments are in an early stage, so I can
not guarantee that it works properly. There exists also a snapshot [2]
which leads you to a bundled application (SOS + Rest API + Helgoland
(map-diagram-branch). Sadly there are no sample data available and I can
not explain how to get mobile Data in the SOS. Maybe Carsten or Henning
can give you a hint?

Best regards,
Jan



[1] https://github.com/52North/helgoland
[2]
https://52north.org/delivery/SensorWeb/SOS/52n-sensorweb-sos-bundle-4.4.0-Extended-REST-API-Helgoland.zip

On 06.07.2016 09:19, Simon Jirka wrote:

> Hi Jack,
>
> Your question has an excellent timing. There are currently three
> projects in which we extend the JavaScript SOS Client (Helgoland) as
> well as the REST-API (as part of the SOS server) to support the
> visualisation of mobile sensors. My colleague Jan Schulte will be able
> to provide you more information about this.
>
> Best regards
> Simon
>
> 2016-07-04 20:52 GMT+02:00 jdf1307 <[hidden email]>:
>> Hi there,
>>
>> I wanted to ask if the future version of the 52°North JS client will support
>> the Spatial Observation as mentioned in [0].
>>
>> If I insert such observations in the SOS and use GetObservation in the SOS
>> instance everything works fine.
>> However if I use the JS client to visualize the data, there are no markers
>> added to the map.
>> At least I can see the observation values as timeseries data in diagram
>> mode.
>>
>> I also checked out the SensorWebClient [2].
>> However if I deploy the client in Tomcat, there are only three stations
>> shown, which are not associated with my sensor station, they are called
>> "PEGELONLINE", "Wupperverband", and "Air Quality Belgium".
>> Furthermore the map loads infinitely, the other buttons are not responding,
>> when I click on them.
>> After a timeout of about 5 minutes the client stops loading.
>>
>> With the QGIS client I achieved similar not satisfactory results.
>>
>> I do not have the possibility to check this in ArcGIS SOS Plugin, due to
>> lacking ArcGIS myself. Does anybody have experience in that matter?
>>
>> So are there solutions for visualizing mobile sensor data using current SOS
>> clients?
>> I would like to implement this feature for the JS thin client myself,
>> however I do not know where to start in [1]. I would be glad if hints
>> regarding establishing visualization for mobile sensors can be provided.
>>
>>
>> Due to the need of visualizing such mobile sensor data I implemented a
>> prototype JS client, which also is based on leaflet.
>>
>> In this a simple routine is implemented, the client periodically executes
>> GetObservation request addressing my currently running SOS instance. After
>> receiving the POX response is processed, required values are saved in
>> variables. Using leaflet a map is generated and markers are added,
>> containing observation values and time. The position of the markers are
>> based on the om:parameter position value.
>> However this approach is not feasible in the long run, it would be better to
>> augment the current 52°North JS client.
>> I attached a screenshot of this client in the end of the post.
>> You can visit the client on (sometimes the server could be down):
>> http://gpslog.ddns.net:8080/sosClient
>>
>> <http://sensorweb.forum.52north.org/file/n4028563/mobileSensorJSClient.jpg>
>>
>> Best regards,
>>
>> Jack
>>
>> -----------------------------------------------------------------------
>> [0] http://schemas.opengis.net/om/2.0/examples/spatial_observation1.xml
>> [1] https://github.com/52North/js-sensorweb-client
>> [2]
>> http://52north.org/downloads/download/14-clients/400-52n-sensorwebclient-310-release
>>
>>
>>
>> --
>> View this message in context: http://sensorweb.forum.52north.org/Spatial-Observation-support-for-SOS-clients-tp4028563.html
>> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
>> _______________________________________________
>> SWE mailing list
>> [hidden email]
>> http://list.52north.org/mailman/listinfo/swe
>> http://sensorweb.forum.52north.org
>> Please respect our mailing list guidelines:
>> http://52north.org/resources/mailing-lists-and-forums/guidelines
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines

--
Jan Schulte
52°North GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
Fon: +49 251 396371 - 37
Fax: +49 251 396371 - 11
Web: http://52north.org

General Managers:
Albert Remke, Andreas Wytzisk
Local Court Münster HRB 10849

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

Jacky Fu

Hi Jan,

thank you for your answer I will look into the bundled version and try to submit sample data. Looking onto the map diagram visualization in your repository, I think it is really interesting! So the map markers of the stations there are they based on the observation sampling geometries? Or do they still depend on the feature of interest sampling geometries? 


Kind regards,

Jack


On Thu, Jul 7, 2016 at 9:41, Jan Schulte
Hi Jack,

so first of all what Henning says to the SensorWebClient applies also to
the js-sensorweb-client. There are no big developments in thies
repository. I will add a hint in the readme.md.

The current client developments are focused on the previously mentioned
client called Helgoland [1]. In the branch
feature/map-diagram-combination is a visualization to see a mobile
trajectory which combines a map where you can see the trajectory as
geometry and a diagram where you see the measurement to the regarding
trajectory points. These developments are in an early stage, so I can
not guarantee that it works properly. There exists also a snapshot [2]
which leads you to a bundled application (SOS + Rest API + Helgoland
(map-diagram-branch). Sadly there are no sample data available and I can
not explain how to get mobile Data in the SOS. Maybe Carsten or Henning
can give you a hint?

Best regards,
Jan



[1] https://github.com/52North/helgoland
[2]
https://52north.org/delivery/SensorWeb/SOS/52n-sensorweb-sos-bundle-4.4.0-Extended-REST-API-Helgoland.zip

On 06.07.2016 09:19, Simon Jirka wrote:

> Hi Jack,
>
> Your question has an excellent timing. There are currently three
> projects in which we extend the JavaScript SOS Client (Helgoland) as
> well as the REST-API (as part of the SOS server) to support the
> visualisation of mobile sensors. My colleague Jan Schulte will be able
> to provide you more information about this.
>
> Best regards
> Simon
>
> 2016-07-04 20:52 GMT+02:00 jdf1307 <<a shape="rect" ymailto="mailto:jacky.fu@mytum.de" href="javascript:return">jacky.fu@...>:
>> Hi there,
>>
>> I wanted to ask if the future version of the 52°North JS client will support
>> the Spatial Observation as mentioned in [0].
>>
>> If I insert such observations in the SOS and use GetObservation in the SOS
>> instance everything works fine.
>> However if I use the JS client to visualize the data, there are no markers
>> added to the map.
>> At least I can see the observation values as timeseries data in diagram
>> mode.
>>
>> I also checked out the SensorWebClient [2].
>> However if I deploy the client in Tomcat, there are only three stations
>> shown, which are not associated with my sensor station, they are called
>> "PEGELONLINE", "Wupperverband", and "Air Quality Belgium".
>> Furthermore the map loads infinitely, the other buttons are not responding,
>> when I click on them.
>> After a timeout of about 5 minutes the client stops loading.
>>
>> With the QGIS client I achieved similar not satisfactory results.
>>
>> I do not have the possibility to check this in ArcGIS SOS Plugin, due to
>> lacking ArcGIS myself. Does anybody have experience in that matter?
>>
>> So are there solutions for visualizing mobile sensor data using current SOS
>> clients?
>> I would like to implement this feature for the JS thin client myself,
>> however I do not know where to start in [1]. I would be glad if hints
>> regarding establishing visualization for mobile sensors can be provided.
>>
>>
>> Due to the need of visualizing such mobile sensor data I implemented a
>> prototype JS client, which also is based on leaflet.
>>
>> In this a simple routine is implemented, the client periodically executes
>> GetObservation request addressing my currently running SOS instance. After
>> receiving the POX response is processed, required values are saved in
>> variables. Using leaflet a map is generated and markers are added,
>> containing observation values and time. The position of the markers are
>> based on the om:parameter position value.
>> However this approach is not feasible in the long run, it would be better to
>> augment the current 52°North JS client.
>> I attached a screenshot of this client in the end of the post.
>> You can visit the client on (sometimes the server could be down):
>> http://gpslog.ddns.net:8080/sosClient
>>
>> <http://sensorweb.forum.52north.org/file/n4028563/mobileSensorJSClient.jpg>
>>
>> Best regards,
>>
>> Jack
>>
>> -----------------------------------------------------------------------
>> [0] http://schemas.opengis.net/om/2.0/examples/spatial_observation1.xml
>> [1] https://github.com/52North/js-sensorweb-client
>> [2]
>> http://52north.org/downloads/download/14-clients/400-52n-sensorwebclient-310-release
>>
>>
>>
>> --
>> View this message in context: http://sensorweb.forum.52north.org/Spatial-Observation-support-for-SOS-clients-tp4028563.html
>> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
>> _______________________________________________
>> SWE mailing list
>> <a shape="rect" ymailto="mailto:SWE@52north.org" href="javascript:return">SWE@...
>> http://list.52north.org/mailman/listinfo/swe
>> http://sensorweb.forum.52north.org
>> Please respect our mailing list guidelines:
>> http://52north.org/resources/mailing-lists-and-forums/guidelines
> _______________________________________________
> SWE mailing list
> <a shape="rect" ymailto="mailto:SWE@52north.org" href="javascript:return">SWE@...
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines

--
Jan Schulte
52°North GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
Fon: +49 251 396371 - 37
Fax: +49 251 396371 - 11
Web: http://52north.org

General Managers:
Albert Remke, Andreas Wytzisk
Local Court Münster HRB 10849


_______________________________________________
SWE mailing list
<a shape="rect" ymailto="mailto:SWE@52north.org" href="javascript:return">SWE@...
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

jdf1307
In reply to this post by jdf1307
Hi there,

I deployed the Helgoland client in my own SOS instance which has still the version 4.3.6 due to the fact that the bundled version of the SOS 4.4.0 seems to have no transactional extensiom, i. e.  I cannot use Insert operations.
In the Helgoland client there is a additional menu next to 'Diagramm' and 'Map' which is called Trajectory when connected with my SOS instance version 4.3.6. That menu was not available when I used the client in conjunction with the SOS 4.4.0 bundled version.
After I clicked on it I expected to see my spatial observations as a trajectory like you mentioned earlier.
However the client replied there are no trajectories on the SOS instance, so I suppose a trajectory is not made of multiple spatial observations from a sensor .
Also the position of the marker on the map is displayed as the featuresOfInterest sampling geometry and not as the observation's sampling geometry using om:parameter-Element.
So how is the trajectory mechanism implemented, does this automatically happen in the bundled SOS 4.4.0 version or is it theoretically possible in the stable 4.3.6 version?

Best regards,


Jack
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

Carsten Hollmann
Hi Jack,

> I deployed the Helgoland client in my own SOS instance which has still the
> version 4.3.6 due to the fact that the bundled version of the SOS 4.4.0
> seems to have no transactional extensiom, i. e.  I cannot use Insert
> operations.

The transactional operations are supported. Have you enabled the
operations in the admin interfance and disable or configured the
transactional security?

Trajectories are only supported from version 4.4.0 of the SOS and from
version 2.0 of the Sensor Web REST-API which is included in the SOS
4.4.0 SNAPSHOT bundle.
With previous versions of the SOS and Sensor Web REST-API trajectories
are not supported because some adjustments to the SOS database model
were necessary.

Best,
Carsten


_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

jdf1307
Hi Carsten,


Carsten Hollmann wrote
Hi Jack,

> I deployed the Helgoland client in my own SOS instance which has still the
> version 4.3.6 due to the fact that the bundled version of the SOS 4.4.0
> seems to have no transactional extensiom, i. e.  I cannot use Insert
> operations.

The transactional operations are supported. Have you enabled the
operations in the admin interfance and disable or configured the
transactional security?

Trajectories are only supported from version 4.4.0 of the SOS and from
version 2.0 of the Sensor Web REST-API which is included in the SOS
4.4.0 SNAPSHOT bundle.
With previous versions of the SOS and Sensor Web REST-API trajectories
are not supported because some adjustments to the SOS database model
were necessary.

Best,
Carsten


_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines

thank you for your hints! The transactional profile is activated on default, when no settings are changed during the initial SOS configuration. However it is neccessary to switch on the transactional operations, i. e. in the admin operations section http://localhost:8080/52n-sos-webapp/admin/operations.
I activated the operations and afterwards I tested the SOS using Insertions of sensor and observations. For that I used provided example operations of the SOS:

1. [POX] InsertSensor - with SensorML 2.0 description (SOS 2.0.0)
2. [POX] InsertObservation - Measurement/Spatial Filtering Profile (SOS 2.0.0) (3x times)

The only thing I changed in those examples are the position of the spatial observation (om:parameter)
and the position of the feature of interest.
Afterwards I could see in the map section that my sensor is positioned according to the values in the sampling geometry of the feature of interest. Succeeding changes of the sampling geometry of the feature of interest (same identifier) did not change the position of the sensor in the map section.
In comparison in the trajectory section I could see three dot-shaped markers which are positioned in the trajectory map according to the sampling geometry of my observation. I also could see the interesting map diagram visualization, which was mentioned by Jan.

So I assume
- The position of the sensor in the map section is deduced from the sampling geometry of the feature of interest
- The position of the observation in the trajectory map is deduced from the sampling geometry of the observation, i. e. from the value of om:parameter
 
Can this be confirmed? Is this the anticipated pathway for the SOS 4.4.0?

When looking at the InsertSensor request (that which I mentioned before in my test) in the CapabilitiesList there are SensorML elements provided which states whether the sensor is in-situ or remote and whether the sensor is mobile or stationary.
Are they solely supposed to provide metadata information or is that data used in conjunction with specific functionality?


Thanks in advance and best regards,

Jack
Reply | Threaded
Open this post in threaded view
|

Re: Spatial Observation support for SOS clients

Carsten Hollmann
Hi Jack,

> So I assume
> - The position of the sensor in the map section is deduced from the sampling
> geometry of the feature of interest
> - The position of the observation in the trajectory map is deduced from the
> sampling geometry of the observation, i. e. from the value of om:parameter
>
> Can this be confirmed? Is this the anticipated pathway for the SOS 4.4.0?

Yes, the location of a stationary sensor is deduced from the geometry of
the featureOfInterest and the trajectory positions are deduced from the
samolingGeometry of the observation.

For mobile sensors the featureOfInterest geometry should not be set.

> When looking at the InsertSensor request (that which I mentioned before in
> my test) in the CapabilitiesList there are SensorML elements provided which
> states whether the sensor is in-situ or remote and whether the sensor is
> mobile or stationary.
> Are they solely supposed to provide metadata information or is that data
> used in conjunction with specific functionality?

This information are stored in the procedure table and is used by the
REST-API to identify the "platform" type. In you case "in-situ" and
"mobile" should be "true".

Best,
Carsten
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines