deploy a FIWARE context broker on OpenShift Local and WasteWaterPlant Smart Model Data apps #282
Labels
openShift-deployment-containers
Suggested skills: OpenShift infrastructure, OpenShift deployment, containers
WasteWaterPlant deployment
to deploy a FIWARE context broker on OpenShift Local and WasteWaterPlant Smart Model Data apps
deploy a FIWARE context broker on OpenShift Local and WasteWaterPlant Smart Model Data apps
Your mission, should you choose to accept it, is to deploy a FIWARE context broker on OpenShift Local and WasteWaterPlant Smart Model Data apps.
Walk through Youtube videos related to your task
These Youtube videos have been carefully prepared to help you with this data import task:
More details about your task
orion-ld
Deployment in thefiware
namespace, I suggest adding an Environment VariableORIONLD_CORS_ALLOWED_ORIGIN
to__ALL
so that the visualization specialist's application will be able to make requests to the Context Broker using JavaScript and AJAX.The day of the operation is Thursday February 2nd, 2023
You will have 4 hours to complete your mission.
Work with Smart Data Models and the FIWARE Context broker in Europe
At the end of the day
Should you, or any of your force be taken or compromised that day, you must report back as many changes as you have made, and any knowledge of your actions, by pull request or comments on the issue on the board.
The details of your mission:
Entity: WasteWaterPlant
Open License
document generated automatically
Global description: Data model for waste water treatment plant.
List of properties
address
: The mailing addressalternateName
: An alternative name for this itemareaServed
: The geographic area where a service or offered item is providedbod
: Biological Oxygen Demand concentration measured in the waste-water treatment plant corresponding to this observation.cod
: Chemical Oxygen Demand concentration measured in the waste-water treatment plant corresponding to this observation.dataProvider
: A sequence of characters identifying the provider of the harmonised data entity.dateCreated
: Entity creation timestamp. This will usually be allocated by the storage platform.dateModified
: Timestamp of the last modification of the entity. This will usually be allocated by the storage platform.description
: A description of this itemdo
: Dissolved oxygen measured in the waste-water treatment plant corresponding to this observation.id
: Unique identifier of the entityinFlow
: In-flow amount into the treatment plant/reservoir corresponding to this observation.location
: Geojson reference to the item. It can be Point, LineString, Polygon, MultiPoint, MultiLineString or MultiPolygonmunicipalityInfo
: Municipality information corresponding to this observation.name
: The name of this item.nh4
: Ammonium concentration measured in the waste-water treatment plant corresponding to this observation.no3
: Nitrate concentration measured in waste-water treatment plant corresponding to this observation.observationDateTime
: Last reported time of observation.outFlow
: Out-flow amount into the treatment plant/reservoir corresponding to this observation.owner
: A List containing a JSON encoded sequence of characters referencing the unique Ids of the owner(s)pHTSA
: Acidity level or basicity level observed in the water. Object defining the temporal processing of the magnitude property during a period. It provides maximum, minimum, instant value and averagepo4
: Ortho-phosphate concentration measured in the waste-water treatment plant corresponding to this observation.redox
: Reduction potential or oxidation measured in waste-water treatment plant corresponding to this observation.seeAlso
: list of uri pointing to additional resources about the itemsource
: A sequence of characters giving the original source of the entity data as a URL. Recommended to be the fully qualified domain name of the source provider, or the URL to the source object.tic
: Total Inorganic Carbon concentration measured in the waste-water treatment plant corresponding to this observation.tn
: Total Nitrogen concentration measured in waste-water treatment plant corresponding to this observation.toc
: Total Organic Carbon concentration measured in the waste-water treatment plant corresponding to this observation.treatmentPlantCapacity
: Handling capacity of the waste-water treatment plant corresponding to this observation.treatmentPlantCode
: Unique code for the waste-water treatment plant corresponding to this observation.treatmentPlantId
: Unique identification number for the waste-water treatment plant corresponding to this observation.treatmentPlantName
: Name of the waste-water treatment plant corresponding to this observation.tss
: Total suspended solids concentration measured in a waste-water treatment plant corresponding to this observation.type
: NGSI entity type. It has to be WasteWaterPlantRequired properties
id
type
Data Model description of properties
Sorted alphabetically (click for details)
full yaml details
Example payloads
WasteWaterPlant NGSI-v2 key-values Example
Here is an example of a WasteWaterPlant in JSON-LD format as key-values. This is compatible with NGSI-v2 when using
options=keyValues
and returns the context data of an individual entity.WasteWaterPlant NGSI-v2 normalized Example
Here is an example of a WasteWaterPlant in JSON-LD format as normalized. This is compatible with NGSI-v2 when not using options and returns the context data of an individual entity.
WasteWaterPlant NGSI-LD key-values Example
Here is an example of a WasteWaterPlant in JSON-LD format as key-values. This is compatible with NGSI-LD when using
options=keyValues
and returns the context data of an individual entity.WasteWaterPlant NGSI-LD normalized Example
Here is an example of a WasteWaterPlant in JSON-LD format as normalized. This is compatible with NGSI-LD when not using options and returns the context data of an individual entity.
See FAQ 10 to get an answer on how to deal with magnitude units
WasteWaterPlant adopters
This message will not self destruct, because this project is open source.
The text was updated successfully, but these errors were encountered: