These files reflect changes made to the MVCO profile after version 1.0 (deliverables) was reviewed and after the changes made in harmonizing approaches after discussions about the CTD/DO model.
1. SOS implementation
Table View from SensorML Description
1.1 GetCapabilities - Returns service metadata and information about the Offerings provided.
1.2 GetObservation - returns the observation data. Currently, 6 offerings are provided:
- ADCP_DATA - Latest measurement of all Wave data parameters, including QC flags
- ADCP_DATA with individual observedProperties - Latest measurement of several Wave parameters, including aggregateVelocityFlag, waveHeight, wavePeriod, swell, and swellPeriod
- ADCP_DATA - Archived Time Series of all Wave data parameters, including QC flags
- ADCP_DATA_QC- Only wave data which has passed the Velocity Quality Control test
- PRESSURE_ALL- All wave data derived from pressure measurement, including QC flags
- PRESSURE_QC - Pressure-derived parameters that have passed Pressure QC tests
- VELOCITY_ALL - All wave data derived from the ADCP 2HZ velocity measurements
- VELOCITY_QC - Velocity-derived parameters that have passed beamIntensity Test, Correlation Coeff test, Qartod Velocity QC tests
1.3 DescribeSensor - return info about the sensor, provenance, and qc processes Here is a sample request for the ProcessChain that generates the ADCP_DATA offering:
ADCP_System is the overall system description for the MVCO ADCP Waves Offerings.
A good way to see describeSensor returns (as a human instead of a machine) is to copy and paste the above link into the PrettyView service. When available we will offer a link to component, as well as a link to the describeSensor in PrettyView. For example, the describeSensor for the ADCP_System can be viewed in PrettyView.
The remainder of the SensorML documents for the instrument and various QC Processes are detailed in Sections 2 & 3.
2. Sensor Description Files, v 2.2
The SensorML Description document for the Martha's Vineyard Coastal Observatory shows the main platforms/components that comprise the Observing system:
MVCO_ObservingSystem.xml - System overview for Martha's Vineyard Coastal Observatory (MVCO). (PrettyView)
Also, shown here is a diagram of the MVCO.
There are two main SensorML documents that describe the ADCP, one of the components of the 12m node at the MVCO. They are:
RDI_Workhorse_1200.xml - A general SensorML description of the RDI instrument: the 1200 Workhorse. This is called the Original Equipment Manufacturer (OEM) file and fully describes the model attributes, capabilities, parameters and characteristics. (PrettyView)
MVCO_Workhorse_1200.xml - SensorML description entailing specific details about the MVCO setup and deployment of an RDI Workhorse. (ConDep file) (PrettyView)
These two were encapsulated in a single document (MVCO_Workhorse) in the 1.0 version. It is better to split them up like this, so that any Data Provider using the RDI could reuse the general SensorML description, and they need only fill in details about their particular installation in a separate SensorML doc.
Work is still ongoing on the SensorML description for the RDI_Workhorse_1200. This work is being done with the assistance of Teledyne RDI to ensure accuracy.
3. Process Files
A number of different files comprise the process chain for the ADCP.
3.2 ProcessChain Modules
Each chain encapsulates one or more <components> which may be either another ProcessChain or a generic Test. The ProcessChain describes a flow of data via <inputs>, <outputs>, and <parameters>. A series of <connections> serves to describe the linkage between components.
- ADCP_System - The main SensorML System description. This is Fig 2 in Janet's Chapter 4 in the user guides. (PrettyView)
- Pressure_QC_Chain - General ProcessChain for Pressure time series QC (PrettyView)
- Velocity_QC_Chain - General ProcessChain for Velocity time series QC (PrettyView)
- Pressure_QC_Chain_Values - ProcessChain for Pressure time series data with parameters configured for MVCO setup (Obsolete -- but left in for demonstration purposes. See PARAMS service below.)) (PrettyView)
- Pressure_Obs_Process - Chain that generates a number of observable properties from the cleaned, interpolated time series that is output from Pressure_QC_Chain. (PrettyView)
- Velocity_Obs_Process - Chain that generates a number of observable properties from the cleaned, interpolated time series that is output from Velocity_QC_Chain. (PrettyView)
- PUV_Analysis - Using pressure and horizontal velocity (PUV), compute the wave direction parameters.(See the MVCO Process Diagram') (PrettyView)
- TimeSeriesChain - ProcessChain composed of several individual processes that perform time-related QC checks on the Pressure and Velocity Series data. (PrettyView)
3.3 Parameter values for tests
For several of the tests/processes above, certain parameters can be included inline, or declared externally and coupled to the appropriate process by SensorML-aware software. Examples of this include minimum and maximum wave height for a wave height range check, or the number of Standard Deviations to be used for a SpikeTest. The MVCO SOS serves these parameters as another SOS offering, so that the parameter values used for any time in the archive can be retrieved at a later date:
Link to PARAMS service.
4. MVCO Registered Vocabularies
- observableProperty - the sensed observable properties of a system
- process - qc tests and processing descriptions
- properties - the output (processed) oceanographic or meteorological observed properties
- mvco QC flag
- platform - descriptions
5. SensorML Tools - A couple of development tools are in the works for viewing and editing SensorML Tools. These can be found at the VAST team website:
SensorML Tools
These are described briefly below.
5.1 PrettyView
A basic web application provides an aid for displaying SensorML files in a tabular form for human consumption. The tool allows the display of remote files via a URL, or files on the user's local system. It can be found here:
SensorML PrettyView
It is actually not all that pretty yet, but we are working on adding bells and whistles. More elaborate SensorML display and editing tools are also being developed.
5.2 SensorML Editor - The Editor is a stand-alone application which must be downloaded to the user'slocal machine to run. Details and downloads are available at the SensorML Tools page at UAH:
SensorML Editor