Smart water and Smart Environment: Updated WaterQualityObserved in water quality repository

The data model WaterQualityObserved has been expanded to include 3 new properties:

  • BOD: Biochemical oxygen demand (BOD) is the amount of dissolved oxygen (DO) needed (i.e. demanded) by aerobic biological organisms to break down organic material present in a given water sample at certain temperature over a specific time period
  • COD: Chemical oxygen demand (COD) is an indicative measure of the amount of oxygen that can be consumed by reactions in a measured solution
  • PO4: Concentration of phosphates

Additionally, the data model of WaterQualityObserved has been moved from the dataModel.Environment repo to the dataModel.WaterQuality subject.

In order to preserve the relationship with the SmartEnvironment domain the subject dataModel.WaterQuality has been linked to it.


Improved the database of properties

The database for the searching on data models, properties and their descriptions has been expanded to allow filtering also by :

  • NGSI type (one of Property, Relationship or Geoproperty)
  • data type (string, number, boolean, array, object, etc)

Additionally, it has been updated containing more than 11.000 items

Accessible from the front page in this widget (Structured check)

You can export the results

New data models for Environment. ElectroMagneticObserved and IndoorEnvironmentObserved

There are two new data models ElectroMagneticObserved and IndoorEnvironmentObserved

ElectroMagneticObserved. The Data Model is intended to measure excessive electric and magnetic fields (EMFs), or radiation in a work or public environment according to the level of exposure to electromagnetic fields on the air. The frequency of the Hertzian waves is conventionally lower than 300 GHz, propagating in space without artificial guide. They are between 9 kHz and 300 GHz.
IndoorEnvironmentObserved. Observation of air and climate conditions for indoor environments.

Located in the Subject Environment

New data model for Environment. Phreatic Observed

There is a new data model PhreaticObserved is intended to measure, observe and control the level and quality of groundwater at a given time (T), by a fixed or mobile monitoring system. Depending on the device used, it is also possible to measure the quality of water such as its electrical conductivity, its salt content, its temperature, etc. In this case, the values measured are processed by the Data Model `WaterObserved` and `WaterQualityObserved`. Additional Information about Attributes: For attributes dedicated to water, a MetaData attribute can also be used. it contains the `TimeStamp` in seconds, the `qualification` and control `status` of the measurement”.

Located in the Environment Subject

Specifications in languages in the readme of the data models

Now you can see the links to the specification in two languages, Spanish y French in the of every data models. German and Japanese are in the queue.

See here an example


All specifications updated

All the specifications (the text descriptions of the data model located in the /doc directory of each daat model) for the different domains and languages (currently French and Spanish besides English) have been updated to the new format. See an example in Spanish and French.

All of them are generated automatically from the json schema (which is the unique source of truth for the data model)

The contribution manual explains further details.

Raise an issue for any point you find in the new format.



Check a schema validates a payload

If you want to check if a schema validates a payload  through this API call


Parameters: (Mandatories)

  • payloadUrl: The url of the payload in RAW version
  • schemaUrl: The link to the RAW version of the json schema (see example)


Output: A json payload with these properties

  • result: Boolean. if the schema validates the payload.
  • time: time stamp in ISO 8601 (CET) of the validation
  • payloadUrl: The url of the payload in RAW version submitted
  • schemaUrl: The link to the RAW version of the json schema submitted

on error

  • cause: The description of the cause for the rejection to the validation