Archives for posts with tag: OGC Standard

The Observations&Measurements model is part of the OGC’s Sensor Web Enablement activity. Excerpt from the specification document:

Herein we describe a framework and encoding for measurements and observations. This is required specifically for the Sensor Observation Service and related components of an OGC Sensor Web Enablement capability, and also for general support for OGC compliant systems dealing in technical measurements in science and engineering.

The aim is to define a number of terms used for measurements, and the relationships between them. […] The scope covers observations and measurements whose results may be quantities, categories, temporal and geometry values, coverages, and composites and arrays of any of these.

But how does this relate to sos4R?

Well, as mentioned above, the SOS requires some kind of schema to communicate the markup/encoding of the observations and measurements it stores. So I have to deal with O&M (the common shorthand for the specification) two times: First, when I feed my SOS instance through the transactional profile. An example of a measurement is as follows: Read the rest of this entry »

It’s time now to introduce the second basic element (the first being R) of the sos4R project: the OGC Sensor Observation Service. Instead of going deeply into the specification, I just like to cite some paragraphs from the specification document and elaborate myself more about what I use and the utilized implementation.

What is the SOS?

A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today.

What can it do? Read the rest of this entry »