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.
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.
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
Now the README file of every data model includes a link to the generator of NGSI-LD payloads compliant with the data model.
As you can see in the image below there is a new section “Dynamic examples generation”
There the sentence “Link to the Generator of NGSI-LD payloads compliant with this data model. Refresh for new values”. By clicking the Generator link an example of payload appears on the web page. Refreshing (F5) generates new payloads.
Now all data models have an interactive specification. (As long as they have examples)
This is the first step to deeper interactive services for every data model contributed.
See the example for weatherForecast.
The file common-schema.json compiles those properties massively used across the different data models in the different domains.
The property userAlias has been included to store those anonymous identifiers of a user that cannot be traced back to the user.
It can be referenced in any data model just by including this code
“$ref” : “https://smart-data-models.github.io/data-models/common-schema.json#/definitions/userAlias”
This a general review of the contributions’ manual with these changes:
- Recommendation how to document a property that is an object referencing to a shared schema
- Change order in the elements (schema recommendation is the most demanded documentation and it is being placed at the beginning)
- Minor reviews, contact point, etc.
Located in the upper menu of the site.
It has been updated the database for searching properties, two main improvements:
- Performance (now it is a database query instead of the former static file)
- The reference model of the property
- The format (uri, date-time, etc) for string properties.
A new data model, FloodMonitoring, in the Environment Subject from IUDX initiative is available:
FloodMonitoring: Flood Sensor Data Model intended to represent the level of flooding w.r.t water flow/level at a certain water mass (river, lake, etc.).