You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ A quick way to send sensor data to an OGC Sensor Observation Service - Transacti
11
11
1.[What is SOS-T](#what-is)
12
12
1.[How SOS-T Works](#brief-sos)
13
13
1.[How to Send Sensor Data](#how-to)
14
+
1.[How to Get Sensor Data](#how-to-receive)
14
15
15
16
<h2id="quick-start">Quick Start</h2>
16
17
@@ -120,3 +121,8 @@ When you are finally done communicating with the server, clean up the server con
120
121
```java
121
122
sosService.shutdown();
122
123
```
124
+
125
+
<h2id="how-to-receive">How to Get Sensor Data</h2>
126
+
127
+
Although outside of the original scope of this library, you can also use swe-android to pull data from an **SOS 2.0** compatible server. swe-library will retrieve a list of sensors and will allow you to get the latest sensor data for a particular sensor to include automatically polling the server to regularly get sensor data. To see how this is implemented, check out the PullExampleActivity in the Example app.<br/>
128
+
swe-android will also except a limited number of **SOS-T** commands to allow one app running swe-android to share OGS SOS data with another app running swe-android. This is mostly a temporary work around to provide interim connectivity while more robust solutions like **Open Sensor Hub** become fully integrated.
0 commit comments