diff --git a/workshop/content/docs/api-deep-dive/sensorthings.md b/workshop/content/docs/api-deep-dive/sensorthings.md
index 1829d3e..b41d7e0 100644
--- a/workshop/content/docs/api-deep-dive/sensorthings.md
+++ b/workshop/content/docs/api-deep-dive/sensorthings.md
@@ -398,12 +398,15 @@ only the result and phenomenonTime properties listed.
## Demo
-- [Demo From SensorUp](http://developers.sensorup.com/docs/)
-- Link:
-- Behaves like a GetCapabilities.
-- Provides URLs to interrogate further the service
+On this section, we explore different ways to access a [SensorThings API server](http://developers.sensorup.com/docs/) on:
-### Return Base Resource Path
+
+
+### Web Client
+
+We start exploring the different endpoints available in the server using a web browser. In alternative you could also use [postman](https://www.postman.com/) or [curl](https://curl.se/).
+
+#### Return Base Resource Path
@@ -426,32 +429,27 @@ only the result and phenomenonTime properties listed.
"name": "Datastreams",
"url": "http://pm25-march.singapore2017.sensorup.com/v1.0/Datastreams"
},
+ {
+ "name": "Sensors",
+ "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/Sensors"
+ },
+ {
+ "name": "Observations",
+ "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/Observations"
+ },
+ {
+ "name": "ObservedProperties",
+ "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/ObservedProperties"
+ },
+ {
+ "name": "FeaturesOfInterest",
+ "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/FeaturesOfInterest"
+ }
+ ]
+ }
```
-### Return Base Resource Path (Cont)
-
-``` properties
-{
- "name": "Sensors",
- "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/Sensors"
-},
-{
- "name": "Observations",
- "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/Observations"
-},
-{
- "name": "ObservedProperties",
- "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/ObservedProperties"
-},
-{
- "name": "FeaturesOfInterest",
- "url": "http://pm25-march.singapore2017.sensorup.com/v1.0/FeaturesOfInterest"
-}
-]
-}
-```
-
-### Which *Things* are available in the server?
+#### Which *Things* are available in the server?
@@ -473,7 +471,7 @@ only the result and phenomenonTime properties listed.
> ...
> ```
-### Getting a *Datastream* for a thing
+#### Getting a *Datastream* for a thing
@@ -511,7 +509,7 @@ only the result and phenomenonTime properties listed.
> },
> ```
-### Getting the *Observations* related to a stream
+#### Getting the *Observations* related to a stream
@@ -535,7 +533,7 @@ only the result and phenomenonTime properties listed.
},
```
-### Complex Query
+#### Complex Query
- Expands Datastreams and observations in one query
- Feature of Interest = 7000:Ft. York / Capreol Crt.
@@ -554,7 +552,7 @@ only the result and phenomenonTime properties listed.
> Datastreams/Observations/phenomenonTime le 2017-03-01T11:30:00.000Z
> ```
-### Complex Query Response
+#### Complex Query Response
> ``` properties
> {
@@ -583,11 +581,6 @@ only the result and phenomenonTime properties listed.
> "name": "dock count",
> "definition": "http://unitsofmeasure.org/ucum.html#para-50"
> },
-> ```
-
-### Complex Query Response (cont)
-
-> ``` properties
> "Observations@iot.nextLink":
> ".../v1.0/Datastreams(9)/Observations?$top=100&$skip=100",
> "Observations":[
@@ -605,6 +598,14 @@ only the result and phenomenonTime properties listed.
> "description": " ...
> ```
+### Python Client
+
+The [Sensorthings API Python Client](https://pypi.org/project/frost-sta-client/) is a python package for developing applications with SensorThings API.
+
+### QGIS Plugin
+
+The [SensorThings API plugin](https://plugins.qgis.org/plugins/SensorThingsAPI/) enables QGIS software to access dynamic data from sensors, using SensorThings API protocol.
+
## References
[ITU-T, Overview of the Internet of
diff --git a/workshop/content/docs/assets/images/bridges.png b/workshop/content/docs/assets/images/bridges.png
new file mode 100644
index 0000000..66b93ca
Binary files /dev/null and b/workshop/content/docs/assets/images/bridges.png differ
diff --git a/workshop/content/docs/getting-involved.md b/workshop/content/docs/getting-involved.md
index dbdb818..038dfac 100644
--- a/workshop/content/docs/getting-involved.md
+++ b/workshop/content/docs/getting-involved.md
@@ -10,7 +10,7 @@ There are numerous ways to get involved with the development of OGC APIs. If you
Most of the OGC API development takes place on public [GitHub repositories](https://github.com/orgs/opengeospatial/repositories?q=ogcapi&type=all&language=&sort=). This means anyone can follow the development of the standards, from their early stages and even contribute through the usual mechanisms (e.g.: issue tracker, pull requests)
-{width="100.0%"}
+{width="100.0%"}
## OGC Code sprints
diff --git a/workshop/content/docs/transition-and-migration.md b/workshop/content/docs/transition-and-migration.md
index e0e2017..7efc2b8 100644
--- a/workshop/content/docs/transition-and-migration.md
+++ b/workshop/content/docs/transition-and-migration.md
@@ -10,4 +10,8 @@ This could be the case of many [OWS standards](https://developer.ogc.org/ows.htm
As with deprecated Standards, Legacy Standards are no longer supported, but they remain on the OGC website with a notification that the capabilities of the Standard have been replaced in whole or part by new Standard(s). The notification will clearly indicate that the Legacy Standard is not invalid, but that new implementations of the capabilities of the Standard are better served by the identified new Standard(s).
-In the Diving into pygeoapi Workshop, we include a section about the use of bridges to facilitate the migration from OWS to OGC API. TODO: add link
\ No newline at end of file
+In the [Diving into pygeoapi Workshop](https://dive.pygeoapi.io), you can find
+a section about the [use of bridges to facilitate the migration from OWS to OGC
+API](https://dive.pygeoapi.io/advanced/bridges/).
+
+{width="80.0%"}
\ No newline at end of file