visualize FIWARE WaterObserved Smart Model Data using tools of your choice #257
Labels
ux-ui-containers
Suggested skills: UX, UI, containers
WaterObserved visualization
to visualize FIWARE WaterObserved Smart Model Data using tools of your choice
visualize FIWARE WaterObserved Smart Model Data using tools of your choice
Your mission, should you choose to accept it, is to visualize FIWARE WaterObserved Smart Model Data using tools of your choice.
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
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: WaterObserved
Open License
document generated automatically
Global description: ** Water observation data model is intended to represent the parameters of flow, level and volume of water observed, as well as the swell information, over a fixed or variable area. This observation also includes the masses of floating objects on this area. The data collected is provided by Sensors, Cameras,Water stations positioned at specific or sensitive locations for rivers, streams, torrent, lakes, seas, etc.**
List of properties
address
: The mailing addressalternateName
: 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.dateObserved
: Date and time of this observation represented by an ISO8601 UTC format.dateObservedFrom
: Observation period : Start date and time in an ISO8601 UTC format.dateObservedTo
: Observation period : End date and time in an ISO8601 UTC format.description
: A description of this itemflow
: Water Flow observed. The unit code (text) of measurement given using the UN/CEFACATheight
: Water height - Level reach on alert coasts.id
: Unique identifier of the entitylocation
: Geojson reference to the item. It can be Point, LineString, Polygon, MultiPoint, MultiLineString or MultiPolygonmeasuredArea
: Reference of the surface measured. The unit code (text) of measurement given using the UN/CEFACT Common Codes (max. 3 characters). For instance,MTK
represents M².name
: The name of this item.objectArea
: Percentage occupied by floating object in the area. The unit code (text) of measurement given using the UN/CEFACT Common Codes (max. 3 characters). For instance,P1
represents Percentage.objectHeightAverage
: Average height raised. The unit code (text) of measurement given using the UN/CEFACT Common Codes (max. 3 characters). For instance,MTR
represents Meter.objectHeightMax
: Maximum height raised. The unit code (text) of measurement given using the UN/CEFACT Common Codes (max. 3 characters). For instance,MTR
represents Meter.objectVolume
: Estimated volume raised. The unit code (text) of measurement given using the UN/CEFACT Common Codes (max. 3 characters). For instance,MTQ
represents Cubic Metersowner
: A List containing a JSON encoded sequence of characters referencing the unique Ids of the owner(s)refDevice
: A reference to a point of interest associated 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.swellDirection
: Swells Direction observed.swellHeight
: Swell height observed.swellPeriod
: Swells period observed.type
: NGSI Entity type. It has to be WaterObservedwaveLength
: Wave Length observed.Required properties
dateObserved
id
location
type
Water observation data model is intended to represent the parameters of flow, level and volume of water observed, as well as the swell information, over a fixed or variable area. This observation also includes the masses of floating objects on this area. The data collected is provided by [Sensors], [Cameras], [Water stations] positioned at specific or sensitive locations for rivers, streams, torrent, lakes, seas, etc.
Data Model description of properties
Sorted alphabetically (click for details)
full yaml details
Example payloads
WaterObserved NGSI-v2 key-values Example
Here is an example of a WaterObserved 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.WaterObserved NGSI-v2 normalized Example
Here is an example of a WaterObserved 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.
WaterObserved NGSI-LD key-values Example
Here is an example of a WaterObserved 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.WaterObserved NGSI-LD normalized Example
Here is an example of a WaterObserved 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
WaterObserved adopters
This message will not self destruct, because this project is open source.
The text was updated successfully, but these errors were encountered: