deploy a FIWARE context broker on OpenShift Local and AgriGreenhouse Smart Model Data apps #270
Labels
AgriGreenhouse deployment
to deploy a FIWARE context broker on OpenShift Local and AgriGreenhouse Smart Model Data apps
openShift-deployment-containers
Suggested skills: OpenShift infrastructure, OpenShift deployment, containers
deploy a FIWARE context broker on OpenShift Local and AgriGreenhouse Smart Model Data apps
Your mission, should you choose to accept it, is to deploy a FIWARE context broker on OpenShift Local and AgriGreenhouse 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: AgriGreenhouse
Open License
document generated automatically
Global description: This entity contains a harmonised description of the conditions recorded within a generic greenhouse, a type of AgriParcel.
version: 0.0.2
List of properties
alternateName
: An alternative name for this itembelongsTo
: Entity the Greenhouse belongs toco2
: The measured interior C02 concentration nominally in mg/LdailyLight
: Daily Accumulated light measured in kW per square metredataProvider
: 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 itemdrainFlow
: The observed drain flow rate in litres per secondhasAgriParcelChildren
: Related sub AgriParcel records to which this entity relateshasAgriParcelParent
: Reference to the AgriParcel entity to which this entity relateshasDevice
: Reference to the IoT devices associated with this greenhouse i.e. sensors, controls.hasWaterQualityObserved
: Reference to one or more water quality observation records current for this entityhasWeatherObserved
: Reference to the weather observation record current for this entityid
: Unique identifier of the entityleafTemperature
: The inside relative humidity expressed as a number between 0 and 1 representing the range 0% to 100 (%).0 <= relativeHumidity <= 1
name
: The name of this item.ownedBy
: Owner (Person or Organization) of the AgriGreenhouseowner
: A List containing a JSON encoded sequence of characters referencing the unique Ids of the owner(s)relatedSource
: List of IDs the current entity may have in external applicationsrelativeHumidity
: The average greenhouse air temperature nominally in degrees centigrade.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
: NGSI Entity Type. It has to be AgriGreenhouseRequired properties
hasAgriParcelParent
id
type
This entity is primarily associated with the agricultural vertical and related IoT applications.
Data Model description of properties
Sorted alphabetically (click for details)
full yaml details
Example payloads
AgriGreenhouse NGSI-v2 key-values Example
Here is an example of a AgriGreenhouse 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.AgriGreenhouse NGSI-v2 normalized Example
Here is an example of a AgriGreenhouse 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.
AgriGreenhouse NGSI-LD key-values Example
Here is an example of a AgriGreenhouse 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.AgriGreenhouse NGSI-LD normalized Example
Here is an example of a AgriGreenhouse 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
AgriGreenhouse adopters
This message will not self destruct, because this project is open source.
The text was updated successfully, but these errors were encountered: