Data Services SOS - glos/Documentation GitHub Wiki

SOS is an OGC standard used for interoperable management of sensor data. This web service interface provides a means for querying data and metadata, registering and removing sensors, and adding new sensor observations (OGC, 2015).

GLOS has implemented the IOOS customized build of the 52◦ North SOS, which has been extended with IOOS-specific encoding formats and test data as described in the IOOS 52N reference. The IOOS enhancements to 52N include extra metadata in the GetCapabilities response and extensions of SensorML to include extra metadata and incorporate the concept of hierarchies for networks, stations, and sensors. The GLOS SOS implementation complies with the IOOS SWE Milestone 1.0 templates and requires datasets to be in any of the CF 1.6 Discrete Sampling Geometries.

The GLOS 52 North instance for serving the in-situ observation data runs through Tomcat 7 and uses PostgreSQL 9.2 / PostGIS 2.0. The GLOS SOS data includes air pressure, air temperature, dew point, humidity, significant wave height, wave period, water level, water temperature, wind speed and directional data from the GLOS network of sensors. Observation data are harvested every 12 minutes using Sensor Web Harvester from submitted XML and injected into 52N.

SOS is physically isolated from other JEE applications by taking a multiple instances approach with Tomcat: a crash of other applications and JVMs sharing the same Tomcat binary will not affect the SOS. The SOS Tomcat instance only listens on local ports and takes Apache web server as its proxy. The backend PostgreSQL 9.2 is installed on a separate database server.

In addition to the 44 buoys and stations in GLOS 52N SOS, GLOS applications consume SOS services from: • Center for Operational Oceanographic Products and Services (COOPS) SOS – 53 stations • National Data Buoy Center (NDBC) – 24 buoys and stations • Lake Simcoe Resource Conservation Authority (LSCRA) – 2 stations