You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each schema must be a valid HTTP(S) URLs to an existing YAML files compliant to fiboa Schema.
39
+
The schema for this specification (see above) is required to be provided.
40
+
41
+
Each `collection` must have a single set of applicable schemas.
42
+
43
+
The schema URI listed above is required to be present in the `schemas` array.
44
+
45
+
### id
27
46
28
-
A Collection is a group of one or more features with a unique identifier (see property `collection`).
47
+
It must be unique per collection, i.e. `collection` and `id` form a unique identifier.
29
48
30
-
Each collection must have a single set of applicable schemas.
49
+
###collection
31
50
32
-
Any property that consists of the same value across all features can be de-duplicated to the collection-level
33
-
if more than two features are available for the collection.
51
+
A collection is a group of one or more features with a unique identifier, stored in the `collection` property.
52
+
53
+
The collection identifier is usually only needed for merged datasets and it is **required** in this case.
54
+
Implementations may create collection identifiers if datasets that don't provide a collection identifer are getting merged.
55
+
A validatior can't know whether the `collection` property is required, the data providers or tooling must handle this,
56
+
i.e. if data from two different sources is merged, a `collection` property with distinct values must be provided.
57
+
This ensures unique IDs through the combination of the properties `id` and `collection`.
58
+
59
+
Encodings may support to store properties that consists of the same value across all features at the collection-level.
60
+
This de-duplicates data for more efficient resource usage, but only applies if more than two features are available for the collection.
34
61
The specific location and behaviour of collection-level data is specified in the encoding-specific specifications.
35
62
36
-
Example:
63
+
**Example:**
37
64
38
65
You have two different field boundary datasets named `abc` (CC-0 licensed) and `xyz` (CC-BY-4.0 licensed).
39
66
If you store the datasets separately, you can store the license in the collection-level data
@@ -42,23 +69,9 @@ Once you merged the two datasets, you must ensure that a unique identifier for t
42
69
(here: `abc` and `xyz`) so that IDs are unique.
43
70
Additionally, you have to add the license property on the feature-level as the licenses are now twofold.
44
71
45
-
## General Properties
46
-
47
-
| Property Name | Data Type | Description |
48
-
| ------------- | -------------- | ----------- |
49
-
| schemas | array\<string> |**REQUIRED.** A list of URLs to schemas the collection implements. |
50
-
| id | string |**REQUIRED.** A unique identifier for the field. It must be unique per collection, i.e. `collection` and `id` form a unique identifier. |
51
-
| collection | string | The identifier of the parent collection. |
52
-
| category | array\<string> | A set of categories the field boundary belongs to. |
72
+
### category
53
73
54
-
**schemas:** The schemas the collection implements. Must be URLs to the schema YAML files.
55
-
The schema for this specification (see above) is required to be provided.
56
-
57
-
**collection:** The collection identifier is usually only needed for merged datasets and it is **required** in this case.
58
-
A validatior can't check whether the `collection` property is required, the data providers or tooling must ensure that if data from two different sources are merged that a `collection` property with distinct values is provided.
59
-
Otherwise, IDs may conflict or extension requirements might not be fulfilled and validation could fail.
60
-
61
-
**category:** Choose any (unique) combination of the following values:
74
+
Choose any (unique) combination of the following values:
62
75
63
76
-`conceptual`: This boundary represents how the grower thinks of a field, and what they would share with service
64
77
providers to allocate information at the highest level of the field concept within their operation.
@@ -81,29 +94,36 @@ The categories are based on the [definitions of the AgGateway initiative](https:
81
94
| area | float | Area of the field, in hectares. Must be > 0 and <= 100,000. |
82
95
| perimeter | float | Perimeter of the field, in meters. Must be > 0 and <= 125,000. |
83
96
84
-
**area/perimeter:** These are derived attributes from the geometry itself,
97
+
### area / perimeter
98
+
99
+
These are derived attributes from the geometry itself,
85
100
and must match the geometry's area/perimeter. If they do not match then the
86
101
geometry should be considered canonical.
87
102
Validators may flag the value as invalid if it exceeds a certain threshold.
0 commit comments