Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
INTRODUCTION TO OGC’S SENSORML AND O&M:
EXAMPLE OF A POSSIBLE SOLUTION
Alessandro Oggioni & Holger Dettki
A future for a common bio-logging language? BLS 6, 27 September 2017, Konstanz, Germany
OPEN GEOSPATIAL CONSORTIUM (OGC)
Standards organization, originated in 1994. In the OGC, more than 500 commercial, governmental, nonprofit and research institutions worldwide collaborate in a consensus process encouraging development and implementation of open standards for geospatial content and web services.
OPEN GEOSPATIAL CONSORTIUM (OGC)
principal OGC web services
• WebMapService WMSastandardforexposingspatial dataasaimagesontheweb
• WebCoverageService WCSastandardforexposingrasterdatawiththeir informativecontentontheweb
• WebFeatureService WFSastandardforexposing vectordatawiththeirinformativecontent ontheweb
• SensorWebEnablement SOSastandardforexposingobservations andsensors information collectedbyin-situ sensors ontheweb
• WebProcessingService WPSastandardforexposingprocess requests(input) andresponses (output)fromdifferentdatasources
• WebCatalogService CSWastandardforexposingacatalogueofgeospatialrecordsontheweb
0
50
100
150
200
250
300
350
9-apr 29-apr 19-mag 8-giu 28-giu 18-lug
Q sim
Q mis
OPEN GEOSPATIAL CONSORTIUM (OGC)
▸ open geospatial consortium (OGC) and W3C standard
▸ capacity of systematic acquisition in-situ measurements/observations
▸ on-line accessibility to data (O&M) and sensor metadata (SensorML)
▸ implementation of SWE services within Spatial Data Infrastructures (SDI)
STANDARDISED SENSOR METADATA - to automatically ingest/import/exchange DATA
SWE = O&M + SensorML
SENSOR WEB ENABLEMENT (SWE)
SENSOR METADATA LANGUAGE - SENSORML
▸ OGC XML schema for describe instruments:
General Info
Histories
STATIC CONTENT
DYNAMIC CONTENT
Parameter
OBSERVATIONS & MEASUREMENTS (O&M)
defines a conceptual schema encoding for observations. While the O&M standard was developed in the context of geographic information systems, the model is derived from generic patterns proposed by Fowler and Odell (1997) and is not
limited to spatial information.
INTEROPERABILITY: STANDARDS + THESAURUS
O&MTHESAURUS
SENSORML
what is measured?
who measures?
what is measured?
• Lookup info for bio-logging terms
• Web based
• Info about provider, type, setting and data formats for each sensor
• Refers to Thesaurus file
• Contains the actual sensor data
• Refers to sensor definition SensorML file
OBSERVATIONS & MEASUREMENTS (O&M)
derived from: Katharina Schleidt image within Draft Guidelines for the use of Observations & Measurements and Sensor Web Enablement-related standards in INSPIRE Annex II and III data specification development. 2013
Feature Property
Observation
Process Values
AirTemperature
Expertjudgement
FeatureOfInterest
observedProperty
result procedure
SensorMLsensorprofile
h3ps://edmapache1.umweltbundesamt.at/envThes/USLterCV_81
43.1212.45
2010-03-01,12.052010-04-15,15.34
INTEROPERABILITY: STANDARS + THESAURUS
General Info
STATIC CONTENT
SensorML
INTEROPERABILITY: STANDARS + THESAURUS
SensorML
DYNAMIC CONTENT
Historieslink to other SensorML file
INTEROPERABILITY: STANDARS + THESAURUS
SensorML
DYNAMIC CONTENT
Parameter
INTEROPERABILITY: STANDARS + THESAURUS
O&M
link to SensorML file
INTEROPERABILITY: STANDARS + THESAURUS
O&M
INTEROPERABILITY: STANDARS + THESAURUS
O&M and SensorML
Thesaurus.xml
OM_PAS01_20151013T180340Z.xml
OM_PAS01_20151013T180336Z.xml
OM_PAS02_20151013T180345Z.xml
OM_PAS02_20151013T180350Z.xml
SML_Provider_A_Sensor_01_20151001T100112Z.xml
SML_Provider_A_Sensor_02_20151001T100112Z.xml
Thesaurus sensorML Observation & Measurements (O&M)
• Info about provider, type, setting and data formats for each sensor
• Refers to Thesaurus file • The file name must be unique to avoid
overwriting & reflect setting changes
• Contains the actual sensor data • Refers to sensor definition sensorML file • The file name must be unique (ID!) to avoid
overwriting
• Lookup info forbio-‐logging terms
• Web based
Example of GPS data
SensorID;DateTime_UTC;ECEF_X;ECEF_Y;ECEF_Z;Lon;Lat;Alt;DOP;FixType;Bat_Main;Bat_Bkup;Temp
P1S01;2015-‐10-‐13T18:00:43Z;3399215;1004816;5284760;16.4678;56.327081;46.91211;1.8;1;3.28;3.44;16
P1S01;2015-‐10-‐13T17:30:13Z;3399217;1004816;5284754;16.46779;56.32704;42.98222;2.6;1;3.28;3.44;15
P1S01;2015-‐10-‐13T17:00:12Z;3399209;1004848;5284758;16.46833;56.32704;47.08708;1.6;1;3.36;3.44;14
P1S01;2015-‐10-‐13T16:30:13Z;3399075;1004862;5284842;16.46916;56.32839;47.94707;2.0;1;3.36;3.52;14
P1S01;2015-‐10-‐13T16:00:42Z;3399077;1004862;5284840;16.46915;56.32837;47.34598;1.6;1;3.28;3.44;14
P1S01;2015-‐10-‐13T15:30:12Z;3399115;1004822;5284824;16.46836;56.32810;47.94738;2.8;1;3.28;3.36;15
P1S01;2015-‐10-‐13T15:00:13Z;3399139;1004992;5284778;16.47088;56.32734;49.14776;3.0;1;3.28;3.44;15
P1S01;2015-‐10-‐13T14:30:13Z;3399175;1004984;5284754;16.47059;56.32698;47.05807;1.4;1;3.28;3.44;15
File P1S01_20151013T180336Z.csv
O&M file: Headers<om:OM_Observation xmlns:sos="http://www.opengis.net/sos/2.0"
xmlns:swes="http://www.opengis.net/swes/2.0" xmlns:swe="http://www.opengis.net/swe/2.0"
xmlns:sml="http://www.opengis.net/sensorML/1.0.1" xmlns:gml="http://www.opengis.net/gml/3.2"
xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:om="http://www.opengis.net/om/2.0"
xmlns:sams="http://www.opengis.net/samplingSpatial/2.0"
xmlns:sf="http://www.opengis.net/sampling/2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-‐instance"
xsi:schemaLocation="http://www.opengis.net/sos/2.0 http://schemas.opengis.net/sos/2.0/sos.xsd http://www.opengis.net/samplingSpatial/2.0 http://schemas.opengis.net/samplingSpatial/2.0/spatialSamplingFeature.xsd"
gml:id="O35235">
<gml:name>GPS Data</gml:name>
<om:type xlink:href="http://www.opengis.net/def/observationType/OGC-‐OM/2.0/OM_SWEObservation"/>
<om:phenomenonTime>
<!-‐-‐ scts is the time stamp the information was transmitted by email, GSM or Iridium -‐-‐>
<gml:TimeInstant gml:id="sctsTime_20151013180336">
<gml:timePosition>2015-‐10-‐13T18:03:40.000-‐00:00</gml:timePosition>
</gml:TimeInstant>
</om:phenomenonTime>
O&M file: Data <om:observedProperty xlink:href="http://rdfdata.get-‐it.it/BiologgingSensorML/Provider1/Sensor01/SML_P1S01_20170602T100400Z.xml"/>
<om:result>
<swe:DataArray>
<swe:encoding>
<swe:TextEncoding decimalSeparator="." tokenSeparator=";" blockSeparator="\n"/>
</swe:encoding> <swe:values>
P1S01;2015-‐10-‐13T18:00:43Z;3399215;1004816;5284760;16.4678;56.327081;46.91211;1.8;1;3.28;3.44;16
P1S01;2015-‐10-‐13T17:30:13Z;3399217;1004816;5284754;16.46779;56.32704;42.98222;2.6;1;3.28;3.44;15
P1S01;2015-‐10-‐13T17:00:12Z;3399209;1004848;5284758;16.46833;56.32704;47.08708;1.6;1;3.36;3.44;14
P1S01;2015-‐10-‐13T16:30:13Z;3399075;1004862;5284842;16.46916;56.32839;47.94707;2.0;1;3.36;3.52;14
P1S01;2015-‐10-‐13T16:00:42Z;3399077;1004862;5284840;16.46915;56.32837;47.34598;1.6;1;3.28;3.44;14
P1S01;2015-‐10-‐13T15:30:12Z;3399115;1004822;5284824;16.46836;56.32810;47.94738;2.8;1;3.28;3.36;15
P1S01;2015-‐10-‐13T15:00:13Z;3399139;1004992;5284778;16.47088;56.32734;49.14776;3.0;1;3.28;3.44;15
P1S01;2015-‐10-‐13T14:30:13Z;3399175;1004984;5284754;16.47059;56.32698;47.05807;1.4;1;3.28;3.44;15
</swe:values>
</swe:DataArray>
</om:result>
sensorML file: DefinitionsFile: SML_P1S01_20170602T100400Z.xml
Thesaurus at jpl.nasa.govhttps://sweet.jpl.nasa.gov/2.0/spaceCoordinates.owl#Latitude
sensorML file: Bio-‐logging DefinitionsFile: SML_P1S01_20170602T100400Z.xml
Bio-‐logging-‐Thesaurus at rdfdata.get-‐it.ithttp://rdfdata.get-‐it.it/BiologgingThesaurus/collarTemperature