|
1 | | -# Pilot 3 air quality & semantics |
2 | | - |
3 | | -## Semantic uplift |
4 | | - |
5 | | -The following files are semantically uplifted and published in the |
6 | | -[OGC RAINBOW hosted instance](https://defs-dev.opengis.net/vocprez-hosted): |
7 | | - |
8 | | -* `generic/properties.yml`: AD4GD properties |
9 | | -* `generic/procedures.yml`: AD4GD procedures |
10 | | -* `generic/sensors.yml`: AD4GD sensors |
11 | | -* `generic/sensor-manufacturers.yml`: AD4GD sensor anufacturers) |
12 | | - |
13 | | -New uplift entries can be configured inside `.ogc/catalog.ttl` |
14 | | -(see [Documentation and tutorials](#documentation-and-tutorials) below). |
15 | | - |
16 | | -Please bear in mind that any `.ttl` files that you may find in this repository (apart from `.ogc/catalog.ttl`) |
17 | | -are most certainly going to be auto-generated, and thus you should not edit them directly because your changes |
18 | | -will be lost. The repository is set up to work with YAML/JSON files and JSON-LD uplift definitions (`*-uplift.yml` |
19 | | -files), and to generate (and publish) their RDF representations automatically. |
20 | | - |
21 | | -### Documentation and tutorials |
22 | | - |
23 | | -* [Example domain definition (like `.ogc/catalog.ttl`)](https://opengeospatial.github.io/ogc-na-tools/examples/#sample-domain-configuration) |
24 | | -* [How to create a JSON-LD uplift context definition](https://opengeospatial.github.io/ogc-na-tools/tutorials/#how-to-create-a-json-ld-uplift-context-definition) |
25 | | - |
26 | | -## The data model |
27 | | - |
28 | | -A simplified version of the pilot data model employed is shown below. |
29 | | - |
30 | | - |
31 | | - |
32 | | -Further discussion on the rationale for some of the modeling decisions (such as how to link units of |
33 | | -measure and procedures to sensor definitions) can be found in |
34 | | -[this document](https://docs.google.com/document/d/1fzEKymhmAB4dVEEgJE3XXf4DTzPS60oj3wYzJQrZcrE/edit?usp=sharing). |
35 | | - |
36 | | -### Working with observations |
37 | | - |
38 | | -An example of a sensor type defined according to the model above could be (some properties omitted for clarity): |
39 | | - |
40 | | -```turtle |
41 | | -<https://w3id.org/ad4gd/sensors/Nova-Fitness/SDS011> a skos:Concept, owl:Class ; |
42 | | - rdfs:subClassOf sosa:Sensor ; |
43 | | - sosa:observes [ |
44 | | - qudt:hasUnit unit:MicroGM-PER-M3 ; |
45 | | - skos:broader ad4gd-prop:pm10 ; |
46 | | - ssn:implements [ qb:order 1 ; skos:broader ad5gd-procedure:pm-humidity-correction ] ; |
47 | | - ] |
48 | | -. |
49 | | -``` |
50 | | - |
51 | | -This would represent a sensor that observes PM10 concentration (`ad4gd-prop:pm10`) using μg/m³ (`unit:MicroGM-PER-M3`), |
52 | | -and implementing a humidity correction procedure (`ad5gd-procedure:pm-humidity-correction`). |
53 | | - |
54 | | -Apart from their numeric value, it is expected that observations will only include a reference to the |
55 | | -sensor type and a reference to the generalized observable property that has been measured. So, for example, we would |
56 | | -have: |
57 | | - |
58 | | -```turtle |
59 | | -_:obs75134 a sosa:Observation ; |
60 | | - sosa:madeBySensor [ |
61 | | - a <https://w3id.org/ad4gd/sensors/Nova-Fitness/SDS011> ; |
62 | | - dct:identifier "SN/2313Q432" |
63 | | - ] ; |
64 | | - sosa:observedProperty ad4gd-prop:pm10 ; |
65 | | - sosa:hasSimpleResult 0.323 ; |
66 | | -. |
67 | | -``` |
68 | | - |
69 | | -The above observation was made by a sensor of type SDS011 with serial number "SN/2313Q432", its observed property is |
70 | | -PM10, and it has a result of 0.323. If a consumer encounters this observation, it can retrieve the information about the |
71 | | -sensor type and match the observed property to the one declared inside its `sosa:observes`, making it possible to infer |
72 | | -new metadata, resulting in the following full description for the observation: |
73 | | - |
74 | | -```turtle |
75 | | -_:obs75134 a sosa:Observation ; |
76 | | - sosa:madeBySensor [ |
77 | | - a <https://w3id.org/ad4gd/sensors/Nova-Fitness/SDS011> ; |
78 | | - dct:identifier "SN/2313Q432" |
79 | | - ] ; |
80 | | - sosa:observedProperty ad4gd-prop:pm10 ; |
81 | | - sosa:hasSimpleResult 0.323 ; |
82 | | - sosa:hasResult [ |
83 | | - qudt:numericValue 0.323 ; |
84 | | - qudt:unit unit:MicroGM-PER-M3 ; |
85 | | - ] ; |
86 | | - sosa:usedProcedure [ qb:order 1 ; skos:broader ad5gd-procedure:pm-humidity-correction ] ; |
87 | | -. |
88 | | -``` |
89 | | - |
90 | | -### The SOSA model |
91 | | - |
92 | | -For reference, the observation perspective of the [SOSA/SSN ontology](https://www.w3.org/TR/vocab-ssn/) model follows. |
93 | | - |
94 | | - |
95 | | - |
96 | | -## Acknowledgements |
97 | | - |
98 | | -The work has been co-funded by the European Union and the United Kingdom under the |
99 | | -Horizon Europe [AD4GD Project](https://www.ogc.org/initiatives/ad4gd/). |
| 1 | +# AD4GD Pilot 3: Air Quality |
0 commit comments