Category: Smart Water Domain

No comments

New service: Generate a NGSI-LD payload keyvalues format compliant with a Smart Data Model

  By , , , , , , , , , ,

There is a new service for users, which is the ability to generate an example payload compliant with a specific data model in key values format. Previously it was available the normalized format.

Options are located in the main menu (Generate NGSI examples)

No comments

Update of the contribution manual. Process image

  By , , , , , , , , , ,

We have drafted the publication process for new data models and for updates.

It’s the first page of the contribution manual and every box (not in this image) has links to the tools/resources to be used.

Hopefully, it will be more straightforward to be understood.

Comments welcomed

No comments

Updated data models of subject Social media

  By ,

The 5 data models of social media subject have been updated to ensure compatibility with other data models.

  • SMAnalysis. This entity contains a harmonized description of a generic SMAnalysis made for the Social Media domain. This entity is primarily associated with the process of analysis of Social Media applications’ posts.
  • SMCollection. This entity contains a harmonized description of a generic SMCollection made for the Social Media domain. This entity is primarily associated with the process of collection of Social Media posts (primarily Twitter).
  • SMPost. This entity contains a harmonized description of a generic SMPost made for the Social Media domain.
  • SMRefLocation. This entity contains a harmonized description of a generic SM Reference Location (SMRefLocation) made for the Social Media domain.
  • SMUser. This entity contains a harmonized description of a generic SMUser made for the Social Media domain. This entity is primarily associated with the description of a user of Social Media applications.
No comments

New widget for searching data models

  By , , , , , , , , , , ,

In the right column of the front page, there is a new feature for look for data models

Initial

once type ‘light’ it looks like in the right

 Filtered

Every entry is an hyperlink

 

No comments

Shortcut to go or search your data model

  By , , , , , , , , , , ,

The list of data models has been completely changed.

Step 1: write part of the name of data model or repository

Step 2: The table filter the options

Step 3: Click on the name and it takes you directly to the github location you need.

No comments

MediaEvent in the Multimedia Subject

  By ,

The multimedia subject, belonging to the cross-sector domain, has been created with this data model:

MediaEvent. Base for all events raised by elements in the media server.

This model works with the components media server and kurento. Kurento Generic Enabler enables real-time processing of media streams supporting the transformation of video cameras into sensors as well as the incorporation of advanced application functions (integrated audiovisual communications, augmented reality, flexible media playing and recording, etc)

No comments

4 new data models for WasteWater

  By ,

4 new data models for datamodel.wasteWater Subject

  • Blower. This entity contains a harmonized description of a Blower made for the Wastewater treatment domain. The entity represents a Blower that is used for aeration purposes in the wastewater treatment process. Important parameters are measured to regulate and measure the amount of airflow is being provided to the aeration tank in the bioreactor. The energy consumption of a blower is also important information for real-time control and optimization of the wastewater treatment plant.
  • OffGasStack. This entity contains a harmonized description of a generic Off-gas Stack made for the Wastewater treatment domain. This entity represents stacks that are present in some wastewater treatment plants where the emissions, greenhouse gases included, are emitted.
  • WasteWaterJunction. This entity contains a harmonized description of a generic Junction made for the Wastewater treatment domain. Junctions could be in place in certain sections of the treatment plant. For wastewater treatment purposes, the junction is most useful if it is a location of a sensor that measures a specific variable.
  • WasteWaterTank. This entity contains a harmonized description of a generic Tank made for the Wastewater treatment domain. For a given type of tank, all possible variables that can be measured are listed as properties. In the description property, the type of tank (anaerobic, pre-dinitrification, nitrification, etc.)can be defined.
No comments

Don’t to these section in the contribution manual

  By , , , , , , , , , ,

In order to reduce the work for the contributors of the new data models, there is a new section on the contribution manual title ‘don’t do these’ with recommendations for the most common poor practices in the contribution process.

Although all contributions are welcomed it will save everybody’s time by reading this section once.

Additionally, the section can be improved so you can submit your recommendations/lessons learned here.

No comments

Updated all the data models (11) in subject WaterDistributionManagement EPANET

  By

The data models of the subject WaterDistributionManagement EPANET have been updated with flow properties and other improvements. New properties are already available for search in the database.

Additionally, there is an alpha version of the German translation of the specification.

  • Curve. This entity contains a harmonized description of a generic curve made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Junction. This entity contains a harmonized description of a generic junction made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • WaterNetwork. This entity contains a harmonized description of a generic network made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Pattern. This entity contains a harmonized description of a generic pattern made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Pipe. This entity contains a harmonized description of a generic pipe made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Pump. This entity contains a harmonized description of a generic pump made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Reservoir. This entity contains a harmonized description of a generic Reservoir made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • SimulationResult. This entity contains a harmonized description of a generic simulation result made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • SimulationScenario. This entity contains a harmonized description of a generic simulation scenario made for the Water Network Management domain. This entity is primarily associated with the water network management vertical and related IoT applications.
  • Tank. This entity contains a harmonized description of a generic tank made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.
  • Valve. This entity contains a harmonized description of a generic Valve made for the Water Network Management domain. This entity is primarily associated with the water management vertical and related IoT applications.

You can answer our survey in order to know what more useful for you.

    Q1: What elements of a smart data model are useful for you?

    Examples of the options:
    1.-Json Schema
    2.-Examples
    3.-Specification
    Mark those relevant for you

    Optional. Other element useful. (Available or desired)

    Q2: What services do you use?

    1.- Search data models
    2.- Validation of payload
    3.-Validate schema before contribution
    4.-Generate a NGSI-LD payload out of a schema
    Search data modelsValidation of payloadValidate of json schema before contributionGenerate a NGSI-LD payload out of a schema
    Optional. Other services missing. (Available or desired)

    Membership

    Member of FIWARE FoundationMember of TMForumMember of IUDXNo membership

    No comments

    Contribution checklist

      By , , , , , , , , , ,

    There is a new option in the main menu Data Models -> Contribution Checklist

    It is strongly recommended to pass every element before submitting your new data model.

    See below the checklist

      schema.json

      1.-
      2.-

      3.-

      4.-

      Examples

      5.-
      6.-

      Optional documents

      7.-
      8.-
      9.-
      10.-

      Contribution

      11.-

      Comments




      By using this form you agree with the storage and handling of your data by this website.