From 075ae78f760193df04a753c2686d37741195dfe6 Mon Sep 17 00:00:00 2001 From: Jenkins Date: Mon, 17 May 2021 23:41:46 +0000 Subject: [PATCH] Jenkins Commit --- .../ObservationUnits/README.md | 41 ++++++++++--------- 1 file changed, 22 insertions(+), 19 deletions(-) diff --git a/Specification/BrAPI-Phenotyping/ObservationUnits/README.md b/Specification/BrAPI-Phenotyping/ObservationUnits/README.md index bcc3d00b..275d4aef 100644 --- a/Specification/BrAPI-Phenotyping/ObservationUnits/README.md +++ b/Specification/BrAPI-Phenotyping/ObservationUnits/README.md @@ -1,7 +1,8 @@ # Group Observation Units -API to retrieve and submit data (phenotypes, environment variables) from studies. While the study calls focus on one study, calls in this section are for cross-study phenotypic data retrieval and submission. +API to retrieve and submit data regarding Observation Units. An Observation Unit is anything that is being observed. Typically, this is a Plot or a Plant, but it could include things like Fields or Samples. The Observation Level defines the type of Observation Unit. For more information on Observation Levels, please review the Observation Levels documentation. + @@ -14,6 +15,8 @@ Call to retrieve the list of supported observation levels. Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level, `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). The values are used to supply the `observationLevel` parameter in the observation unit details call. + +For more information on Observation Levels, please review the Observation Levels documentation. @@ -141,11 +144,11 @@ Get a filtered set of Observation Units |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -400,11 +403,11 @@ Add new Observation Units |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -445,11 +448,11 @@ Add new Observation Units |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -782,11 +785,11 @@ Note - In strictly typed languages, this structure can be represented as a Map o |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -1432,11 +1435,11 @@ Get the details of a specific Observation Unit |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -1673,11 +1676,11 @@ Update an existing Observation Units |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -1717,11 +1720,11 @@ Update an existing Observation Units |geoCoordinates|object|One geometry as defined by GeoJSON (RFC 7946). All coordinates are decimal values on the WGS84 geographic coordinate reference system. Copied from RFC 7946 Section 3.1.1 A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element.| |geometry|object|A geometry as defined by GeoJSON (RFC 7946). In this context, only Point or Polygon geometry are allowed.| |type|string|The literal string "Feature"| -|observationLevel|object|The exact level and level code of an observation unit. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| +|observationLevel|object|The exact level and level code of an observation unit. For more information on Observation Levels, please review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -2077,11 +2080,11 @@ Review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| @@ -2456,11 +2459,11 @@ Review the Observation Levels documentation. MIAPPE V1.1 DM-71 Observation unit type "Type of observation unit in textual form, usually one of the following: study, block, sub-block, plot, sub-plot, pot, plant. Use of other observation unit types is possible but not recommended. The observation unit type can not be used to indicate sub-plant levels. However, observations can still be made on the sub-plant level, as long as the details are indicated in the associated observed variable (see observed variables). Alternatively, it is possible to use samples for more detailed tracing of sub-plant units, attaching the observations to them instead."| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).| -|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| +|observationLevelRelationships|array[object]|Observation levels indicate the granularity level at which the measurements are taken. For more information on Observation Levels, please review the Observation Levels documentation. `levelName` defines the level `levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`s lower numbers are at the top of the hierarchy (ie field > 0) and higher numbers are at the bottom of the hierarchy (ie plant > 6). `levelCode` is an ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelCode|string|An ID code for this level tag. Identify this observation unit by each level of the hierarchy where it exists| |levelName|string|A name for this level| |levelOrder|integer|`levelOrder` defines where that level exists in the hierarchy of levels. `levelOrder`'s lower numbers are at the top of the hierarchy (ie field -> 1) and higher numbers are at the bottom of the hierarchy (ie plant -> 9).|