Official list of unitcodes

Whenever there is measurement it could be necessary to use the unitCode for setting the units for the value.

Now the guidelines for the data model’s creation include the place to find out these unit codes. See section units.

The list of UN/CEFACT Common Code (3 characters) can be download from this page. Or the list directly from here.

Automatic creation of examples

In order to reduce the amount of work in the contribution of data models, we have a script that generates the key-values format of a normalized NGSI LD payload.
It has been operated on 46 data models currently in the repository.

In a close future instead of submitting 4 examples, it will be only necessary to include 2 examples, the normalized payloads for NGSI v2 and NGSI LD (the other two would be generated automatically).

Making examples more consistent

All the repositories have been normalized in the naming of the core examples. So:

  • Key values in NGSI v2 is named example.json
  • Key values in NGSI LD is named example.jsonld
  • Normalized (default) in NGSI v2 is named example-normalized.json
  • Normalized (default) in NGSI LD is named example-normalized.jsonld

It is possible to have more examples in the directory. And in the same directory of every data model, there are other exports (csv) for the use of the data model users.
The goal is that this 4 examples were present in every data model

Automated README for Subjects

As promised the at Subject level explaining the different data models is automated, and therefore there is no need to be contributed by the contributors. See an example here for the weather subject

Thus, the is based on the data models and their descriptions, linking to the current contributors

Soon the for the domain will be also automated.



Now in the root of every subject, you can find only the file CONTRIBUTORS.yaml with the current contributors to the data model of the subject.

The old file is being removed.

CONTRIBUTORS.yaml is a structured format that allows automatic treatment globally across the initiative. It compiles the full name of the contributor, his/her organization, and their project and comments if necessary.

If you keep seeing it is because you are not looking at the master branch but in a specific commit (like it happens in the submodules). We update the branches in submodules daily, so tomorrow it will not appear unless you want it to go to former commits.

See one example.


Automated for data models

Currently, the at data models level (inside every directory in a Subject) explaining the contents of the data models is automated, and therefore there is no need to be contributed by the contributors. See an example here for the weather forecast.

Thus, the is based on the examples provided, the specification and the model.yaml.

Soon the for the Subject will be also automated.

Incubated data models

if you are browsing the repository you can realise that now there are several data models ended with the term ‘_incubated’.
This suffix denotes that there will be ‘soon’ a new data model.
The readme in the folder points to the repository where this data model is being created.

Once finished (all the docs, examples, etc) the _incubated suffix will be removed and the data model will be fully included into the data models.
some examples:


BuildingType_incubated(published 30-11-21)

PhreaticObserved_incubated (published 31-5-2021)

RainFallRadarObserved_incubated (published 10-5-2021)


Survey to the users of smart data models

This is the first survey to the USERS of the Smart Data Models. We want to know what is more important to you and try to prioritize our efforts. This is an agile initiative, therefore we will take into very consideration your comments. Your survey is anonymous although if you wish you can include your email in comments and we will contact you regarding your comments.

You can answer it here.

    Are you, or your organization, a user of FIWARE platform (any enabler)

    YesNoDo not know

    What elements of the data models are useful for you:

    The json schema. See an example

    Very usefulSomehow usefulNot useful

    The examples of payloads. See an example

    Very usefulSomehow usefulNot useful

    The specification. See an example

    Very usefulSomehow usefulNot useful

    Other elements. Specify Which one/s

    Very usefulSomehow usefulNot useful

    Are you interested on the smart data models?

    YesNoDo not knowOther
    Explain other

    Why don't you use FIWARE platform?

    I do not need itIt is complicatedNot yetOther
    Explain other

    Please choose the more likely (Yes / No)

    Other recommendations or comments about your answers

    How do you describe yourself

    A developerAn end userA project managerA manager

    Soon there will be another survey for the CONTRIBUTORS.

    New data models for Photovoltaic Device

    In the harmonization repository, there is a new model name photovoltaic Device. To be completed previously to be incorporated. You can submit an issue on it if interested.

    The Data Model is intended to describe the mechanical, electrical and thermal characteristics of photo-voltaic panels according to : – STC – Standard Test Condition – Sunshine 1000 Wm² / Radiation 1.5 AM / Temp 25° Celsius / Air Masse 0 m/s. – NOCT – Normal Operating Cell Temperature
    – Sunshine 800 Wm² / Radiation 1.5 AM / Temp 20° Celsius / Air Masse 1 m/s.

    The measures performed for STC and NOCT are – [Pmax] Maximum Nominal Power measured in WTT represents Watt.. – [Umpp] Optimal operating voltage measured in VLT represents Volt. – [Impp] Optimal Operating Current measured in AMP represents Ampere. – [Uoc] Open Circuit Voltage measured in VLT represents Volt. – [Isc] Short Circuit Current measured in AMP represents Ampere.

    Additional Information about Data Model: This Data Model can be used directly as the main entity to describe the device [PHOTOVOLTAIC] or as a sub-entity of the Data Model [DEVICE] using a reference by the refDevice attribute.