agile 2015 a-geo-label-for-the-sensor-web
TRANSCRIPT
A GEO label for the Sensor Web
Daniel Nüst, 52°North Initiative for Geospatial Open Source GmbH, [email protected]
Victoria Lush, Aston University, [email protected]
AGILE 2015, Lisbon
Motivation & ApproachImprove sensor data discovery for increasing amount of data in the sensor web
smart citiesbig datametadata is not sexy, but necessary, and an image says
more then a thousand words…
Adapt GEO label to sensor web1. Support sensor web datasources for labels2. Integrating the label with sensor web metadata
GEO LABELWhat is the GeoViQua …
Motivation
GEOSS has millions of datasets
GEO Science and Technology Committee proposed to establish a GEO label – a label “related to the scientific relevance, quality, acceptance and societal needs for activities in support of GEOSS”
https://www.earthobservations.org/documents/geo_xi/5_3_GEOSS_Highlights_Massacand_Desconnets.pdf
What is the GEO label?
http://geolabel.info and http://geolabel.net
GEO label facets
producer profileproducer commentslineage informationstandards compliancequality informationuser feedbackexpert reviewcitations information
GEO label API
Web service interface for label generation (SOA)
XML APIsvg (and png)
Portals Data services
POST or ref
Transformation Transformation Transformation
Transformation descriptions
Sensor data discovery• Dynamic• Duality of instances and services• Interoperability standards rather complex > Profiles
SensorML Profile for Discovery (Jirka et al.)identification, classification, temporal validity, capabilities, contact, location, interfaces, inputs and outputs of a stationary sensor and its components
A GEO LABEL FOR THE SENSOR WEBThe Sensor Web Label – „SWL“
Requirements / Use case
Scenario: stationary in-situ sensors
• OGC Sensor Web Enablement Standards– SensorML– Sensor Observation Service– XML
• Dynamic integration on client-side• Dynamic integration on the server side• Static integration in sensor and service metadata
Mappings
Mappings
Mappings
Labels within metadata documents
• adding sensor labels in-line so that the whole label information is available in a form of SVG encoded as XML
• as a reference to an online resource, such as a call to the GEO label API
Schematron rules for defining valid integrationsChallenge: denoting link/SVG as label
Prototype
Integrated in open source projectGEO-label-java
https://github.com/52North/GEO-label-java/
Summary
• Information for labels is available in SWE standards,but not all dynamic aspects of SWE are in the label
• Going beyond GEO label: Integration• Requirements fulfilled completely for second generation standards
(inline vs. ref)• Inline integration pros/cons: size, SOA, string matching (non-
semantic)• Need pratical experience and users for consensus of suggested
markups• Transformation file concept works!• Usefulness depends on portals > labels will increase portals‘
usability
Future Work
Extending the SWL• New facets because discovery profile could not be
mapped: standards compliance wrt APIs, license, valid time
Extending data sources for SWL• SSN ontology and semantic web technology• IoT standards• SensorML 2.0 (typeOf), document hierarchies
