Sensor Data Platform

Interpretation of quality assurance (QA) flags ¶

Table below displays the possible QA flags:

X = bit reserved

NOTE: When the verification bit flag is set to Verified, the time series (measurement) value cannot be overwritten.

Interpretation of quality control (QC) flags ¶

The QC flags are set at raw value level.

Table below displays the possible QC flags:

X = bit reserved

Interpretation of specific quality assurance (QAS) flags ¶

Table below displays the possible QAS flags:

X = bit reserved

Interpretation of specific quality control (QCS) flags ¶

The QCS flags are set at raw value level.

Table below displays the possible QCS flags:

X = bit reserved

Interpretation of the pipeline status flags ¶

The pipeline status flags are set at the sensor level.

Table below displays the possible pipeline flag values:

X = bit reserved

Timestamps ¶

It is possible to bind (or map) a JSON attribute representing a moment in time as a timestamp for measurement when storing the data.

If this JSON attribute is given as number of seconds since 00:00:00 UTC on 1 January 1970 (Unix Epoch), then no timestamp converter is required.

On the other hand, if the attribute is represented as a string of any given custom format (e.g. 'yyyy/MM/dd HH:mm:ss'), then the StringEpochTime converter must be used. This converter converts the string value into Unix Epoch.

In both cases a timestamp field-binder must be used if you want to use that JSON attribute as a timestamp representation. Be aware of that if this attribute binding is omitted, the system time will instead be used, which defaults to the Unix Epoch UTC.

Binding Path / Target Path JSON attributes ¶

The "binding-path" and "target-path" JSON attributes are used when a converter or a field-binder is used when defining the sensor schema.

When creating new sensor schema and specifying the components, the binding-path is the absolute JSON path to an attribute (sensor data packet) bound to a component (e.g. PM₁₀, NO₂, CO).

Similar, when using a converter (if required), the converter takes the target-path as an argument. The converter is using this path when converting an attribute (k) with value (v) located at that JSON path.

Similarly, when using a field-binder, the field-binder m is an alias for attribute k with value v located at target path p.

These attributes support JPath syntax.

Below is a table with some examples:

{ "no2" : 15.232 }

{ "no2" : { "value" : 15.232 }}

{ "gas" : { "components" : [ { "no2" : { "value" : 15.232 } }, ... , { "no2" : { "value" : 15.232 } } ] }}

{ "level1" : { "lev.el2" : { "no2" : { "value" : 15.232 } } } }

Errors ¶

All API endpoints use a standard error message format for any requests that return an HTTP status indicating an error (any 400 or 500 statuses). For example, a request entity that omits a required field may generate the following response:

HTTPS/1.1 422 Unprocessable Entity
Content-Type: application/json

{    
    "error-code": 1000,
    "error-message": "Sensor name must be defined.",
    "http-status-code": 422
}

Although it is good practice to check the status code, you may safely parse the response of the API calls and check for the presence of an error-code field to detect errors.

Some error codes are used frequently across the entire API and you will probably want to have general purpose code to handle these, whereas most other error codes will need to be handled on a per-request basis.