Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SENSOR is based on the OGC standard SensorML (and device descriptions are downloadable in XML or JSON format). SENSOR also provides an API to export (and import) data programmatically. Two instances of SENSOR - one on Polarstern and one at AWI Bremerhaven-  will run simultanously throughout MOSAiC. They are synchronized on different levels throughout the day as long as network connection permits.

Data Contacts

Every group has assigned chief editors for there devices. They are your first contacts concerning SENSOR related questions. You find them here:

...

  • general (overview) information such as unique short names, serial numbers, short description etc.
  • Properties: used for quality checks
  • Contacts with different roles e.g. Editor, Owner, Principal Investigator.
  • Actions: Deployment, Recovery, ...
  • Resources: fact sheets, manuals, SOPs
  • Parameters: measurement parameters with parameter types. Parameter types follow NERC vocabulary and are now matched to PANGAEA parameter types
  • Subdevices: devices attached to the device


Note

IMPORTANT!!!

  • ONLY devices which are set to 'Public' and have the contact 'polarstern dship'  with the role 'dship connector'  are synchronized to the MCS onboard Polarstern and will be accessable via the DShip Actionlog.
  • ONLY a contact with the role ‘Data Provider’ will obtain write access in the respective directory on the MCS onboard Polarstern. Please make sure to enter the person that is actually onboard and observes the data flow is entered as editor or data provider.
  • Device operations entered in the DShip Actionlog will appear under 'Actions' in SENSOR. Still, choice of available actions types is limited in SENSOR and therefore several action types in DShip are associated with the same action type in SENSOR.

...

You will find the extensive manual here: SENSOR manual

Overview