deploy a FIWARE context broker on OpenShift Local and WaterConsumptionObserved Smart Model Data apps #286
Labels
openShift-deployment-containers
Suggested skills: OpenShift infrastructure, OpenShift deployment, containers
WaterConsumptionObserved deployment
to deploy a FIWARE context broker on OpenShift Local and WaterConsumptionObserved Smart Mod...
deploy a FIWARE context broker on OpenShift Local and WaterConsumptionObserved Smart Model Data apps
Your mission, should you choose to accept it, is to deploy a FIWARE context broker on OpenShift Local and WaterConsumptionObserved 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: WaterConsumptionObserved
Open License
document generated automatically
Global description: The Smart Water Meter model captures water consumption, customer side leak alarms and associated flow rate originating from the smart water meters
List of properties
acquisitionStageFailure
: No inductive response of metering deviceaddress
: The mailing addressalarmFlowPersistence
: Alarm signifying continuous water usealarmInProgress
: Indicates that one or more alarms are in progressalarmStopsLeaks
: Alarm signifying the potential for an intermittent leakalarmTamper
: Alarm signifying the potential of mechanical tampering with the devicealarmWaterQuality
: Alarm signifying the potential of backflows occurringalternateName
: An alternative name for this itemareaServed
: The geographic area where a service or offered item is provideddataProvider
: 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 itemid
: Unique identifier of the entitylocation
: Geojson reference to the item. It can be Point, LineString, Polygon, MultiPoint, MultiLineString or MultiPolygonmaxFlow
: Maximum flow rate observed during the last weekminFlow
: Minimum flow rate observed during the last weekmoduleTampered
: Removal of module from metering devicename
: The name of this item.owner
: A List containing a JSON encoded sequence of characters referencing the unique Ids of the owner(s)persistenceFlowDuration
: The duration that persistence flow (continuous flow) is recorded by the meter. Text field showing durations in minutes (m), hours (h) or days (d).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.type
: It has to be WaterConsumptionObserved. NGSI typewaterConsumption
: The water meter reading. Note – this is total volume passed through the meter and is therefore a cumulative total at the timeRequired properties
id
type
Data Model description of properties
Sorted alphabetically (click for details)
full yaml details
Example payloads
WaterConsumptionObserved NGSI-v2 key-values Example
Here is an example of a WaterConsumptionObserved 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.WaterConsumptionObserved NGSI-v2 normalized Example
Here is an example of a WaterConsumptionObserved 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.
WaterConsumptionObserved NGSI-LD key-values Example
Here is an example of a WaterConsumptionObserved 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.WaterConsumptionObserved NGSI-LD normalized Example
Here is an example of a WaterConsumptionObserved 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
WaterConsumptionObserved adopters
This message will not self destruct, because this project is open source.
The text was updated successfully, but these errors were encountered: