2. SensorML
Common SensorML profiles
“In order to achieve interoperability within and between various sensor communities, implementation of SensorML will require the definition of community specific semantics (within online dictionaries or ontologies) that can be utilized within the framework” [1].
Task 3.21 deals with the implementation of these profiles, by dealing with the following issues in SensorML:
-
The coding standard itself
-
The list of terms each section includes
-
The list of values each term can accept
-
The controlled vocabularies for the terms and values.
The current report is in sync with the SWE Marine profiles group, which is formulating the common SensorML profiles across the world. The following profiles will form the basis for the SWE Marine group work as they include the decisions taken from the group’s meetings as well.
SWE Marine Profiles Group
To avoid interoperability issues in OGC SWE implementations by different organizations and users, an agreement was needed on how to apply SWE concepts and how to use vocabularies in a common way that would be shared by different projects, implementations, and users.
SWE Marine Profiles group, was created as a solution to the above mentioned need, by partners from several projects and initiatives (AODN, BRIDGES, ENVRI+, EUROFLEETS /EUROFLEETS2, FixO3, FRAM, IOOS, Jerico/Jerico-Next, NeXOS, ODIP/ODIP II, RITMARE, SeaDataNet, SenseOcean, X-DOMES) who joined forces to develop common marine profiles of OGC SWE standards that can be used in multiple projects and organizations. [2]
SWE Marine Profile members interact and communicate through the use of a mailing list and a wiki website. The wiki helps to collect and discuss different approaches to how OGC Sensor Web Enablement (SWE) standards (Sensor Observation Service (SOS), Observations and Measurements (O&M) and SensorML are used in different projects and systems. It is currently structured in the following subsections, which can be edited by its members after logging in:
• SweExamples: Examples of SensorML, O&M and SOS usage
• SweVocabularies: Vocabularies for the Marine SWE Profiles
• SweProfile: Structure and proposed content of the Marine SWE Profiles
• SosInventory: Inventory of SOS Servers
A while ago the group published several vocabularies that cover six SensorML sections, namely the History, Capabilities, Characteristics, Classification, Identification and Contacts [3].
Overview
This document describes platforms and sensors and distinguished them in models and instances. A model is an intangible entity that specifies some characteristics of a group of similar, usually mass-produced products, in the sense of a prototype. An instance is a particular serial number of a model. Through extension and inheritance, we need to only provide minimal instance-specific information about a particular deployed sensor/platform, while retaining a link back to a much more robust manufacturer’s description. The information that is common to all sensors of this model is found by following the link in the typeOf element.
PLATFORM MODELS
IDENTIFIERS
Code style
<sml:identification>
< sml:IdentifierList>
< sml:identifier>
< sml:Term definition=”http://vocab.nerc.ac.uk/collection/W07/current/IDEN0012/”>
< sml:label>Manufacturer</label>
< sml:value>http://vocab.nerc.ac.uk/collection/L35/current/MAN0007/</ sml:value>
</Term>
</ sml:identifier>
< /sml:IdentifierList>
< /sml:identification>
Vocabularies
| List of terms: | Minimum terms: | Status: | |—————–|—————-|———–| | W07 | Model name | Mandatory | | | Model number | | | | Manufacturer | | | | UUID | | | | Unique ID| |
CLASSIFICATION
Code style
<sml:classification>
<sml:ClassifierList>
<sml:classifier>
<sml:Term definition=”http://vocab.nerc.ac.uk/collection/W06/current/CLSS0002/”>
<sml:label>Instrument Type</ sml:label> <sml:value>http://vocab.nerc.ac.uk/collection/L05/current/351/</sml:value>
</sml:Term>
</sml:classifier>
</sml:ClassifierList>
</sml:classification>
Vocabularies
| List of terms: | Minimum terms: | Status: | |—————–|—————-|———–| | W06| Platform type | Mandatory | | | Application Domain | |
CAPABILITIES
Code style
<?xml version=”1.0”?>
<sml:capabilities name=”MeasurementCapapbilities”>
<sml:CapabilityList>
<sml:capability name=”Operating depth”>
<sml:QuantityRange definition=” http://vocab.nerc.ac.uk/collection/W04/current/CAPB0012/”>
<sml:label> Operating depth</label>
<sml:uom href=” http://vocab.nerc.ac.uk/collection/P06/current/ULAA/”/>
<sml:value>10 1000</value>
</sml:QuantityRange>
</sml:capability>
<sml:capability name=”SurvivalDepth”>
<sml:Quantity definition=” http://vocab.nerc.ac.uk/collection/W04/current/CAPB0013/”>
<sml:label>Survival Depth</label>
<sml:uom href=” http://vocab.nerc.ac.uk/collection/P06/current/ULAA/”/>
<sml:value>1000</value>
</sml:Quantity>
</sml:capability>
</sml:CapabilityList>
</sml:capabilities>
Vocabularies
| List of terms: | Minimum terms: | Status: | |—————–|—————-|———–| | W04|Operating Depth| | | Survival Depth | | | | Resolution | | | |Sampling Rate | |
CHARACTERISTICS
Code style
<sml:characteristics name=”PhysicalCharacteristics”>
<sml:CharacteristicList>
<sml:characteristic name=”Weight”>
<sml:Quantity definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0001/”>
<sml:label>Weight</ sml:label>
<sml:uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UGKG/”/>
<sml:value>160</value>
</sml:Quantity>
</sml:characteristic>
<sml:characteristic name=”Length”>
<sml:QuantityRange definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0002/”>
<sml:label>Length</ sml:label>
<sml:uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UXMM/”/>
<sml:value>193 273</value>
</sml:QuantityRange>
</sml:characteristic>
</sml:CharacteristicList>
</sml:characteristics>
Vocabularies
| List of terms: | Minimum terms: | Status: |
|---|---|---|
| W05 | Width | Optional |
| Height | ||
| Weight | ||
| Length | ||
| Material | ||
| Data Storage |
Contacts
Code style
<sml:contacts>
<sml:ContactList>
< sml:contact arcrole=”http://vocab.nerc.ac.uk/collection/G04/current/001/”>
<gmd:CI_ResponsibleParty>
< gmd:contactInfo>
< gmd::CI_Contact>
< gmd:phone>
< gmd:CI_Telephone>
< gmd:voice>
<gco:CharacterString>+449898989</gco:CharacterString>
</ gmd:voice>
</ gmd:CI_Telephone>
</ gmd:phone>
< gmd:address>
< gmd:CI_Address>
< gmd:deliveryPoint>
<gco:CharacterString>xx YYYYYY street</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gmd:CharacterString>UKPT0811</gmd:CharacterString>
</gmd:city>
<gmd:postalCode>
<gco:CharacterString>L3 2BD</gco:CharacterString>
</gmd:postalCode>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role gco:nilReason=”inapplicable”/>
</CI_ResponsibleParty>
</contact>
<sml:contact
xlink:arcrole=” http://vocab.nerc.ac.uk/collection/G04/current/010/”
xlink:href=”http://www.myCompany.com/contact/company.xml”/>
</sml:ContactList>
</sml:contacts>
Vocabularies
| List of terms for roles from G04: | Status: |
|---|---|
| G04 | Optional |
Documentation
Code style
<?xml version=”1.0”?>
<documentation>
<DocumentList>
<document arcrole=”http://sensorml.com/ont/swe/property/OperationsManual”>
<CI_OnlineResource>
<linkage>
<URL>http://www.aanderaa.com/media/pdfs/oxygen-optode-4531.pdf</URL>
</linkage>
<name> <CharacterString>Aanderaa 4531 oxygen optode OperationsManual</CharacterString></name>
<description><CharacterString>Aanderaa 4531 oxygen optode OperationsManual</CharacterString></description>
</CI_OnlineResource>
</document>
</DocumentList>
</documentation>
| Status: |
|---|
| Optional |
PLATFORM INSTANCES
IDENTIFIERS
Code style
<identification>
<IdentifierList>
<identifier>
<Term definition=”http://vocab.nerc.ac.uk/collection/current/IDEN0009/”>
<label>WMO platform number</label>
<value>XXXXXXX</value>
</Term>
</identifier>
<IdentifierList>
<identification>
Vocabularies
| List of terms: | Minimum terms: | Status: | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| W07 | ICES CODE | Mandatory | ||||||||
| CALLSIGN | ||||||||||
| WMO | ||||||||||
| UniqueID | ||||||||||
| Serialnumber | LongName | ShortName | ||||||||
| UUID |
KEYWORDS
Code style
<keywords>
<KeywordList>
<keyword>SenseOcean</keyword>
<keyword>BODC</keyword>
<keyword>NOC</keyword>
</KeywordList>
</keywords>
CAPABILITIES (if additional from the model add here. if different add them in the output)
Code style
<?xml version=”1.0”?>
<capabilities name=”MeasurementCapapbilityTEMPPR01”>
<CapabilityList>
<capability name=”Latency”>
<QuantityRange definition=”http://vocab.nerc.ac.uk/collection/W04/current/CAPB0004/”>
<label>Latency</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UTBB/”/>
<value>0 1</value>
</QuantityRange>
</capability>
<capability name=”Frequency”>
<Quantity definition=”http://vocab.nerc.ac.uk/collection/W04/current/CAPB0003/”>
<label>Frequency</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UTHZ/”/>
<value>1</value>
</Quantity>
</capability>
</CapabilityList>
</capabilities>
| List of terms: | Status: |
|---|---|
| W04 | Optional |
CHARACTERISTICS (Additional characteristics diff from model)
Code style
<characteristics name=”PhysicalCharacteristics”>
<CharacteristicList>
<characteristic name=”Weight”>
<Quantity definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0001/”>
<label>Weight</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UGKG/”/>
<value>160</value>
</Quantity>
</characteristic>
<characteristic name=”Length”>
<QuantityRange definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0002/”>
<label>Length</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UXMM/”/>
<value>193 273</value>
</QuantityRange>
</characteristic>
</CharacteristicList>
</characteristics>
Vocabularies
| List of terms: | Status: |
|---|---|
| W05 | Optional |
CONTACTS (Contacts specific to the instance)
Code style
<sml:contacts>
<sml:ContactList>
< sml:contact arcrole=”http://vocab.nerc.ac.uk/collection/G04/current/CONT0001/”>
<gmd:CI_ResponsibleParty>
< gmd:contactInfo>
< gmd::CI_Contact>
< gmd:phone>
< gmd:CI_Telephone>
< gmd:voice>
<gco:CharacterString>+449898989</gco:CharacterString>
</ gmd:voice>
</ gmd:CI_Telephone>
</ gmd:phone>
< gmd:address>
< gmd:CI_Address>
< gmd:deliveryPoint>
<gco:CharacterString>17 STANDISH STREET</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gmd:CharacterString>UKPT0811</gmd:CharacterString>
</gmd:city>
<gmd:postalCode>
<gco:CharacterString>L3 2BD</gco:CharacterString>
</gmd:postalCode>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role gco:nilReason=”inapplicable”/>
</CI_ResponsibleParty>
</contact>
<sml:contact
xlink:arcrole=” http://vocab.nerc.ac.uk/collection/W08/current/CONT0001/”
xlink:href=”http://www.myCompany.com/contact/company.xml”/>
</sml:ContactList>
</sml:contacts>
Vocabularies
| List of terms | Status: |
|---|---|
| G04 | Mandatory |
COMPONENTS (These are the attached sensors)
Code style
<?xml version=”1.0”?>
<components>
<ComponentList>
<component href=”http://linkedsystems.uk/system/instance/TOOL0969_1234/”/>
<component href=”http://linkedsystems.uk/system/instance/TOOLYSI_89325698/”/>
<component href=”http://linkedsystems.uk/system/instance/TOOLYSI_1234/”/>
<component href=”http://linkedsystems.uk/system/instance/TOOL0969_55555/”/>
<component href=”http://linkedsystems.uk/system/instance/TOOL0969_9898989/”/>
<component href=”http://linkedsystems.uk/system/instance/TOOLYSI_789-654-123/”/>
</ComponentList>
</components>
Status: Optional
POSITION
Code style
By location:
A static location can also be provided using a swe:Vector
<position>
<Vector referenceFrame=”http://www.opengis.net/def/crs/EPSG/6.7/4326”
<coordinate name=”latitude”>
<Quantity definition=”http://vocab.nerc.ac.uk/collection/P07/current/CFSN0600/” axisID=”latitude”>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UAAA/”/>
<value>2.3</value>
</Quantity>
</coordinate>
<coordinate name=”longitude”>
<Quantity definition=”http://vocab.nerc.ac.uk/collection/P07/current/CFSN0554/” axisID=”longitude”>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UAAA/”/>
<value>47.8</value>
</Quantity>
</coordinate>
</Vector>
</position>
By point:
Position by point supports a static location using the gml:Point element. It is not appropriate if the orientation of the component is relevant or the component is has a dynamic location.
<sml:position>
<!– EPSG 4326 is for latitude-longitude, in that order –>
<gml:Point gml:id=”stationLocation” srsName=”http://www.opengis.net/def/crs/EPSG/0/4326”>
<gml:coordinates>47.8 88.56</gml:coordinates>
</gml:Point>
</sml:position>
Trajectory
Status: Mandatory (but depends if you model position or outputs)
-
Suggestions are: to refer to the data to get the position
-
To add a bounding box (To be added soon)
-
To list the values of the trajectory vs time (for fast moving ones, this can get very long)
<sml:position>
<swe:DataArray definition=”Suggestion to create a new vocabulary for geographical spatial co-ordinate category”>
<swe:elementCount>
<swe:Count>
<swe:value>10</swe:value>
</swe:Count>
</swe:elementCount>
<swe:elementType name=”trajectory”>
<swe:DataRecord definition=”Suggestion to create a new vocabulary for geographical spatial co-ordinate category”>
<swe:field name=”samplingTime”>
<swe:Time definition=”To be added in the “>
<swe:label>Sampling Time</swe:label>
<swe:uom xlink:href=”http://www.opengis.net/def/uom/ISO-8601/0/Gregorian”/>
</swe:Time>
</swe:field>
<swe:field name=”location”>
<swe:Vector definition=”http://sensorml.com/ont/swe/property/location” referenceFrame=”http://www.opengis.net/def/crs/EPSG/6.7/4326”
localFrame=”#SENSOR_CRS”>
<swe:label>Platform Location</swe:label>
<swe:coordinate name=”Lat”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/ALATZZ01/”
axisID=”Lat”>
<swe:uom code=”deg”/>
</swe:Quantity>
</swe:coordinate>
<swe:coordinate name=”Lon”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/ALONZZ01/”
axisID=”Long”>
<swe:uom code=”deg”/>
</swe:Quantity>
</swe:coordinate>
</swe:Vector>
</swe:field>
</swe:DataRecord>
</swe:elementType>
<swe:encoding>
<swe:TextEncoding blockSeparator=” “ tokenSeparator=”,”/>
</swe:encoding>
<swe:values>
2011-03-01T04:20:00Z,25.72,-61.75
2011-03-14T13:10:00Z,25.49,-61.70
2011-03-21T18:43:00Z,25.35,-61.63
2011-03-30T05:13:00Z,24.87,-61.43
2011-04-08T01:45:00Z,24.86,-61.42
2011-04-12T08:34:00Z,24.32,-61.67
2011-04-15T09:12:00Z,24.54,-61.53
2011-04-21T03:21:00Z,24.53,-61.68
2011-04-27T04:34:00Z,24.32,-61.76
2011-05-01T12:01:00Z,24.28,-61.56
</swe:values>
</swe:DataArray>
</sml:position>
TYPEOF
Code style
<sml:typeOf xlink:title=”National_Oceanography_Centre_waveglider_General_platform_category” xlink:href=”http://linkedsystems.uk/system/prototype/PL898/”/>
HISTORY
Code style
<sml:history>
<sml:EventList>
<sml:event href=”http://vocab.nerc.ac.uk/collection/W03/current/W030002/”>
<sml:Event>
<swe:label>Deployment</swe:label>
<swe:description>A deployment </swe:description>
<sml:time>
<gml:TimeInstant id=”D07072016”>
<gml :timePosition>2016-07-07T00:00:00Z</gml :timePosition>
</gml :TimeInstant>
</sml:time>
</sml:Event>
</sml:event>
<sml:event href=”http://vocab.nerc.ac.uk/collection/W03/current/W030012/”>
<sml :Event>
<swe:label>Decommissioning</swe :label>
<swe:description>A decommissioning </swe:description>
<sml:documentation>
<sml:DocumentList>
<sml:document>
<gmd:CI_OnlineResource>
<gmd:linkage>
<gmd:URL>http://document819path</gmd:URL>
</gmd:linkage>
</gmd:CI_OnlineResource>
</ sml:document>
</ sml:DocumentList>
</sml:documentation>
<sml:time>
< gml:TimeInstant id=”D02082016”>
< gml:timePosition>2016-08-02T00:00:00Z</ gml:timePosition>
</gml:TimeInstant>
</sml:time>
</sml:Event>
</ sml:event>
< /sml:EventList>
</sml:history>
| List of terms: | Status: |
|---|---|
| http://vocab.nerc.ac.uk/collection/W03/current/ | Mandatory |
SENSOR MODELS
IDENTIFIERS
Code style
<sml:identification>
< sml:IdentifierList>
< sml:identifier>
< sml:Term definition=”http://vocab.nerc.ac.uk/collection/W07/current/IDEN0012/”>
< sml:label>Manufacturer</label>
< sml:value>http://vocab.nerc.ac.uk/collection/L35/current/MAN0007/</ sml:value>
</Term>
</ sml:identifier>
< /sml:IdentifierList>
< /sml:identification>
Vocabularies
Vocabularies
| List of terms: | Minimum terms: | Status: | |—————–|—————-|———–| | W07 | Model name | Mandatory | | | Model number | | | | Manufacturer | | | | UUID | | | | Unique ID| |
CLASSIFICATION
Code style
<sml:classification>
<sml:ClassifierList>
<sml:classifier>
<sml:Term definition=”http://vocab.nerc.ac.uk/collection/W06/current/CLSS0002/”>
<sml:label>Instrument Type</ sml:label>
<sml:value>http://vocab.nerc.ac.uk/collection/L05/current/351/</sml:value>
</sml:Term>
</sml:classifier>
</sml:ClassifierList>
</sml:classification>
Vocabularies
Vocabularies
| List of terms: | Minimum terms: | Status: | |—————–|—————-|———–| | W06|Instrument type| | |Application Domain | |
CAPABILITIES
Code style
<?xml version=”1.0”?>
<sml:capabilities name=”MeasurementCapapbilities”>
<sml:CapabilityList>
<sml:capability name=”Operating depth”>
<sml:QuantityRange definition=” http://vocab.nerc.ac.uk/collection/W04/current/CAPB0012/”>
<sml:label> Operating depth</label>
<sml:uom href=” http://vocab.nerc.ac.uk/collection/P06/current/ULAA/”/>
<sml:value>10 1000</value>
</sml:QuantityRange>
</sml:capability>
<sml:capability name=”SurvivalDepth”>
<sml:Quantity definition=” http://vocab.nerc.ac.uk/collection/W04/current/CAPB0013/”>
<sml:label>Survival Depth</label>
<sml:uom href=” http://vocab.nerc.ac.uk/collection/P06/current/ULAA/”/>
<sml:value>1000</value>
</sml:Quantity>
</sml:capability>
</sml:CapabilityList>
</sml:capabilities>
Vocabularies
| List of terms: | Minimum terms: | Status: |
|---|---|---|
| W04 | Resolution | |
| Selectivity | ||
| Sensitivity | ||
| Accuracy | ||
| Frequency | ||
| Latency | ||
| Sampling Rate |
CHARACTERISTICS
Code style
<sml:characteristics name=”PhysicalCharacteristics”>
<sml:CharacteristicList>
<sml:characteristic name=”Weight”>
<sml:Quantity definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0001/”>
<sml:label>Weight</ sml:label>
<sml:uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UGKG/”/>
<sml:value>160</value>
</sml:Quantity>
</sml:characteristic>
<sml:characteristic name=”Length”>
<sml:QuantityRange definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0002/”>
<sml:label>Length</ sml:label>
<sml:uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UXMM/”/>
<sml:value>193 273</value>
</sml:QuantityRange>
</sml:characteristic>
</sml:CharacteristicList>
</sml:characteristics>
Vocabularies
| List of terms: | Possible terms: | Status: | |
|---|---|---|---|
| W05 | Optional | ||
| Width | |||
| Height | |||
| Weight | |||
| Lenght | |||
| Data Storage | |||
| Material |
Contacts
Code style
<sml:contacts>
<sml:ContactList>
< sml:contact arcrole=”http://vocab.nerc.ac.uk/collection/G04/current/001/”>
<gmd:CI_ResponsibleParty>
< gmd:contactInfo>
< gmd::CI_Contact>
< gmd:phone>
< gmd:CI_Telephone>
< gmd:voice>
<gco:CharacterString>+449898989</gco:CharacterString>
</ gmd:voice>
</ gmd:CI_Telephone>
</ gmd:phone>
< gmd:address>
< gmd:CI_Address>
< gmd:deliveryPoint>
<gco:CharacterString>17 STANDISH STREET</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gmd:CharacterString>UKPT0811</gmd:CharacterString>
</gmd:city>
<gmd:postalCode>
<gco:CharacterString>L3 2BD</gco:CharacterString>
</gmd:postalCode>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role gco:nilReason=”inapplicable”/>
</CI_ResponsibleParty>
</contact>
<sml:contact
xlink:arcrole=” http://vocab.nerc.ac.uk/collection/G04/current/010/”
xlink:href=”http://www.myCompany.com/contact/company.xml”/>
</sml:ContactList>
</sml:contacts>
Vocabularies
| List of terms from G04 for roles: | Status: |
|---|---|
| G04 | Optional |
Documentation
Code style
<?xml version=”1.0”?>
<documentation>
<DocumentList>
<document arcrole=”http://sensorml.com/ont/swe/property/OperationsManual”>
<CI_OnlineResource>
<linkage>
<URL>http://www.aanderaa.com/media/pdfs/oxygen-optode-4531.pdf</URL>
</linkage>
<name> <CharacterString>Aanderaa 4531 oxygen optode OperationsManual</CharacterString></name>
<description><CharacterString>Aanderaa 4531 oxygen optode OperationsManual</CharacterString></description>
</CI_OnlineResource>
</document>
</DocumentList>
</documentation>
| Status: |
|---|
| Optional |
OUTPUTS (Outputs in the model, are inherited to the instance)
Code style
<sml:outputs>
<sml:OutputList>
<sml:output name=”O2Sat_2”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/OXYSZZ02/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UPCT”/>
</swe:Quantity>
</sml:output>
<sml:output name=”Latency”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/W04/current/CAPB0004/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UTBB”/>
<swe:value>1</swe:value>
</swe:Quantity>
</sml:output>
<sml:output name=”Sample volume”>
<swe:QuantityRange definition=”N/A”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/”/>
</swe:QuantityRange>
</sml:output>
<sml:output name=”Temp”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/TEMPPR01/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UPAA”/>
</swe:Quantity>
</sml:output>
<sml:output name=”WC_dissO2_uncalib_2”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/DOXYUZ02/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UPOX”/>
</swe:Quantity>
</sml:output>
</sml:OutputList>
</sml:outputs>
SENSOR INSTANCES
IDENTIFIERS
Code style
<identification>
<IdentifierList>
<identifier>
<Term definition=”http://vocab.nerc.ac.uk/collection/W07/current/IDEN0009/”>
<label>UUID</label>
<value>XXXXXXX</value>
</Term>
</identifier>
<IdentifierList>
<identification>
Vocabularies
| List of terms: | Minimum terms: | Status: | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| W07 | ICES CODE | Mandatory | ||||||||
| UniqueID | ||||||||||
| Serialnumber | LongName | ShortName | ||||||||
| UUID | ||||||||||
KEYWORDS (Keywords can include the sensor outputs from P01)
Code style
<keywords>
<KeywordList>
<keyword> http://vocab.nerc.ac.uk/collection/P01/current/TEMPPR01/”></keyword>
<keyword> http://vocab.nerc.ac.uk/collection/P01/current/OXYSZZ02/”>“></keyword>
<keyword> http://vocab.nerc.ac.uk/collection/P01/current/TEMPPR01/”></keyword>
</KeywordList>
</keywords>
CAPABILITIES (if additional from the model add here. if different add them in the output)
Code style
<?xml version=”1.0”?>
<capabilities name=”MeasurementCapapbilityTEMPPR01”>
<CapabilityList>
<capability name=”Latency”>
<QuantityRange definition=”http://vocab.nerc.ac.uk/collection/W04/current/CAPB0004/”>
<label>Latency</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UTBB/”/>
<value>0 1</value>
</QuantityRange>
</capability>
<capability name=”Frequency”>
<Quantity definition=”http://vocab.nerc.ac.uk/collection/W04/current/CAPB0003/”>
<label>Frequency</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UTHZ/”/>
<value>1</value>
</Quantity>
</capability>
</CapabilityList>
</capabilities>
Vocabularies
| List of terms: | Status: |
|---|---|
| W06 | Optional |
CHARACTERISTICS (Additional characteristics diff from model)
Code style
<characteristics name=”PhysicalCharacteristics”>
<CharacteristicList>
<characteristic name=”Weight”>
<Quantity definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0001/”>
<label>Weight</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UGKG/”/>
<value>160</value>
</Quantity>
</characteristic>
<characteristic name=”Length”>
<QuantityRange definition=”http://vocab.nerc.ac.uk/collection/W05/current/CHAR0002/”>
<label>Length</label>
<uom href=”http://vocab.nerc.ac.uk/collection/P06/current/UXMM/”/>
<value>193 273</value>
</QuantityRange>
</characteristic>
</CharacteristicList>
</characteristics>
| List of terms: | Status: |
|---|---|
| W05 | Optional |
CONTACTS (Additional contacts specific to the instance)
Code style
<sml:contacts>
<sml:ContactList>
< sml:contact arcrole=”http://vocab.nerc.ac.uk/collection/G04/current/CONT0001/”>
<gmd:CI_ResponsibleParty>
< gmd:contactInfo>
< gmd::CI_Contact>
< gmd:phone>
< gmd:CI_Telephone>
< gmd:voice>
<gco:CharacterString>+449898989</gco:CharacterString>
</ gmd:voice>
</ gmd:CI_Telephone>
</ gmd:phone>
< gmd:address>
< gmd:CI_Address>
< gmd:deliveryPoint>
<gco:CharacterString>17 BlUMERG STREET</gco:CharacterString>
</gmd:deliveryPoint>
<gmd:city>
<gmd:CharacterString>UKPT0811</gmd:CharacterString>
</gmd:city>
<gmd:postalCode>
<gco:CharacterString>XXXXX</gco:CharacterString>
</gmd:postalCode>
</gmd:CI_Address>
</gmd:address>
</gmd:CI_Contact>
</gmd:contactInfo>
<gmd:role gco:nilReason=”inapplicable”/>
</CI_ResponsibleParty>
</contact>
<sml:contact
xlink:arcrole=” http://vocab.nerc.ac.uk/collection/W08/current/CONT0001/”
xlink:href=”http://www.myCompany.com/contact/company.xml”/>
</sml:ContactList>
</sml:contacts>
| List of terms for the role: | Status: |
|---|---|
| G08 | Mandatory |
POSITION (only relative position to the platform)
Code style
<sml:position>
<swe:Vector referenceFrame=”EPSG::4326”>
<swe:coordinate name=”easting”>
<swe:Quantity axisID=”x”>
<swe:uom code=”degree”/>
<swe:value>00.0000000</swe:value>
</swe:Quantity>
</swe:coordinate>
<swe:coordinate name=”northing”>
<swe:Quantity axisID=”y”>
<swe:uom code=”degree”/>
<swe:value>00.00000</swe:value>
</swe:Quantity>
</swe:coordinate>
<swe:coordinate name=”altitude”>
<swe:Quantity axisID=”z”>
<swe:uom code=”m”/>
<swe:value>0</swe:value>
</swe:Quantity>
</swe:coordinate>
</swe:Vector>
</sml:position>
Vocabularies
| List of terms for the position: | Status: |
|---|---|
| New vocabulary | Optional |
TYPEOF
Code style
<sml:typeOf xlink:title=”AanderaaOxygenOptode” xlink:href=”http://linkedsystems.uk/system/prototype/TOOL0969/%22/>
ATTACHEDTO
Code style
<sml:attachedTo xlink:title=”platform name” xlink:href=”URI of the platform”/>
HISTORY
Code style
<sml:outputs>
<sml:OutputList>
<sml:output name=”O2Sat_2”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/OXYSZZ02/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UPCT”/>
</swe:Quantity>
</sml:output>
<sml:output name=”Latency”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/W04/current/CAPB0004/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UTBB”/>
<swe:value>1</swe:value>
</swe:Quantity>
</sml:output>
<sml:output name=”Sample volume”>
<swe:QuantityRange definition=”N/A”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/”/>
</swe:QuantityRange>
</sml:output>
<sml:output name=”Temp”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/TEMPPR01/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UPAA”/>
</swe:Quantity>
</sml:output>
<sml:output name=”WC_dissO2_uncalib_2”>
<swe:Quantity definition=”http://vocab.nerc.ac.uk/collection/P01/current/DOXYUZ02/”>
<swe:uom code=”UCUMCODE” xlink:href=”http://vocab.nerc.ac.uk/collection/P06/current/UPOX”/>
</swe:Quantity>
</sml:output>
</sml:OutputList>
</sml:outputs>
| List of terms: | Status: |
|---|---|
| W03 | Mandatory |
REFERENCES
-
Portal.opengeospatial.org, 2016. [Online]. Available:http://portal.opengeospatial.org/files/?artifact_id=21273. [Accessed: 31-Jul- 2016]
-
S. Jirka, “Marine Profiles for OGC Sensor Web Enablement Standard”, in EGU General Assembly, Vienna, 2016, p. 14690
-
Kokkinaki, Alexandra et al. “Semantically enhancing SensorML with Controlled Vocabularies in the Marine Domain.” (2016).