document your team's AgriCrop Smart Data Model project #263
Labels
AgriCrop documentation
to document your team's AgriCrop Smart Data Model project
github-admin-documentation
Suggested skills: GitHub admin, documentation
document your team's AgriCrop Smart Data Model project
Your mission, should you choose to accept it, is to document your team's AgriCrop Smart Data Model project.
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
FiwareAgriCrop
repository for your team's project inside therh-impact
Github Organization here.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: AgriCrop
Open License
document generated automatically
Global description: This entity contains a harmonised description of a generic crop. This entity is primarily associated with the agricultural vertical and related IoT applications.
version: 0.0.4
List of properties
agroVocConcept
: The link with the defined concept into the AgroVoc vocabularyalternateName
: An alternative name for this itemdataProvider
: 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 itemharvestingInterval
: A list of the recommended harvesting interval date(s) for this crop. Specified using ISO8601 repeating date intervals:interval, description
Where interval is in the form of start date/end date
--MM-DD/--MM-DD
Meaning repeat each year from this start date to this end date.
hasAgriFertiliser
: Reference to the recommended types of fertiliser suitable for growing this crop.hasAgriPest
: Reference to the pests known to attack this crophasAgriSoil
: Reference to the recommended types of soil suitable for growing this crop.id
: Unique identifier of the entityname
: The name of this item.owner
: A List containing a JSON encoded sequence of characters referencing the unique Ids of the owner(s)plantingFrom
: A list of the recommended planting interval date(s) for this crop. Specified using ISO8601 repeating date intervals:interval, description
Where interval is in the form of start date/end date
--MM-DD/--MM-DD
Meaning repeat each year from this start date to this end date.
relatedSource
: List of IDs the current entity may have in external applicationsseeAlso
: 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 AgriCropRequired properties
id
name
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
AgriCrop NGSI-v2 key-values Example
Here is an example of a AgriCrop 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.AgriCrop NGSI-v2 normalized Example
Here is an example of a AgriCrop 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.
AgriCrop NGSI-LD key-values Example
Here is an example of a AgriCrop 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.AgriCrop NGSI-LD normalized Example
Here is an example of a AgriCrop 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
AgriCrop adopters
This message will not self destruct, because this project is open source.
The text was updated successfully, but these errors were encountered: